Quote:
Originally Posted by Redcap's Corner
Guys, the likely reason Android is taking a backseat is that iOS has the benefit of consistency. When you design for iPad, you're just designing for iPad. When you design for Android there are dozens and dozens of different platforms and it's a ton of extra work to make sure your app is presentable on all of them. I was bummed too when I first heard that iPad was getting special treatment first, but then I thought about it more, sucked it up, and saved up for an iPad (just in time too... only bought it a few weeks ago).
|
We know WHY it took a back seat. And it always comes down to money and risk on investment. How much money and how much risk Rob would take is up to him. And KickStarter is a great way to know how many peope really would commit. Saying you have an Android tablet is one thing, enough people comitting to pre-paying for it to hire more developers is another.
And I know Rob has expanded is dev base already for Realmworks and other endevors and know there is a limit one can/should expand. And I would understand/accept a "for now, we have our hands full regardless of money". I simply asked if it has been considered.
Funny thing is, for all the "iPad is consistent" talk, it already doesn't support the oldest iPad. And they still have to code for the iPad Mini screen size. I'd argue there are less differences in coding for Android tablet OS (4.x) than the iOS's out now.
And for Android, I disagree (doing some Android developement myself), that tablet market is much different thant the phone market (not nearly the number of different hardware/screensize) and there are steps to handle DPI differences. In fact, using fragments, you could design for phones and tablets at same time. But that's another discussion.
Bottom line, there are those who would put money where are mouth is! :-D