Hmm, I think a lot of people are missing the whole point in this article. I do around 60% Ruby on Rails, 35% iOS and 5% Android dev. The idea around a "lean" startup being, that an MVP, or each new feature, or even testing a change to a previous feature is usually done in quick succession. This being testing with current users over a period of say, a week, and then from the results, changes can be made and the team have learned from the testing.<p>So really, Android allows for this quick succession of testing features and iterating as quick as possible, with even to a few hours turnaround. Also, that it would cost a lot in development time to get something "just right" for the App Store for it to be accepted, whereas with Android you can keep on iterating and pushing changes without having to spent a huge amount of time making everything look perfect, and be absolute minimal in terms of bugs.<p>I love iOS development, and yes, I agree with most people on here about the revenue from iOS, the people paying for apps, Apple's process of helping keep out most malware etc. etc., but for the sake of a "lean" startup, spending extra weeks testing apps making sure it's completely bug free and "looking good enough" for iOS, as well as the wait for Apple to accept the application (and then for users to download the update, in the case of iOS 7, this has been solved), Android is a much better dev option for these changes.<p>Of course, when the team knows that the app is something that people care for, and they have a decent knowledge of what users want, what features they use, and the kind of value that the mobile app brings to them, then they can go ahead and make the best possible iOS app.<p>TL;DR<p>Saving time, money and quick iterations, learning from customers and getting quick data for problem validation, is much easier and faster on Android, than the process on iOS. Think Lean Startup.