But burn rates are exactly that. Burning cash. Losing money. Emphasis on the losing.
I’m really happy that I’m not alone in thinking this way. At some point you have to build a real business, generate real profits, sustain the company without the largess of investor’s capital, and start producing value the old fashioned way. We have a number of companies in our portfolio that do that. And I love them for it. I wish we had more.
Thank you. More please.
You could say that writing iOS and Mac apps is like living in a town where one company provides most of the jobs. (Sure, you could work at the diner, but all your customers work at this one company.)
And writing web apps is like living in New York City, where choice and contrast is everywhere, and sometimes A and B (and C and D) are all equally cool but different.
The web is the cosmopolitan environment.
The most common trap here is the early iOS app which gets some buzz. All of a sudden, the founders hear “When are you building for Android?” The natural, enthusiastic response to sincere requests of the Android chorus is to go ahead and build for Android and seek more downloads, more growth, more revenue. I have a different view though. The proper response is: “No. Buy an iPhone.”
I know that Semil is targeting early mobile companies here. And intuitively, go with one OS where the problems are easier and you can focus on the product seems the right thing to do. However, the product market fit that Semil is talking about is something everyone should consider.
By definition, product market fit requires you to give your app a best shot from two perspectives - the product and the market. Artificially limiting yourselves to one OS also seems just as intuitively wrong. It is important to not treat anything, yes, even what Semil says as gospel.
I am providing a few counterpoints to Semil’s reasons to go Android first.
- Early-stage startup teams cannot afford to handle the hardware fragmentation that plagues Android.
The world typically points me to the compasses not working the same in every Android phone as an example of this. Yes, not everything works exactly the same. However, hardware features being exactly the same has never happened in computing.
In fact, the very tenet of Android is that hardware diversity is a requirement to target the right hardware for the right person. As a developer, you are mostly focused on the system and OS level APIs to target the variety of devices. If that weren’t the case, Windows wouldn’t have the apps that it needed to succeed.
For anyone bringing up OS fragmentation, I urge you to look at the numbers -
So, targeting KitKat+ only devices is a strategy and something that can work very well for you.
- Study after study demonstrates iOS users are not only growing in key geographies, but are more valuable customers.
I am not going to address this. Your goal is to reach people for whom your product/service is of value and they share a certain price for that value. But any generalization here seems moot. Product market fit also means trying different business models and the argument becomes moot when it comes to engaged users. That’s purely a function of your product and service, not the amount of money a customer is willing to part with.
- iPhone 5c and future low cost models will likely steal share from Android relative to yesterday.
Yup! As much as cheaper Android phones or better Android phones are stealing market share from the iOS userbase.
I respect Semil and his advice is certainly well intended and founded. However, my advice, treat nothing as gospel. Do what’s right for you.