Linked by Thom Holwerda on Thu 7th Jun 2012 16:40 UTC
Thread beginning with comment 521223
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
If you would be developing apps for a living you would be developing for both. Because there is a ridiculously small chance of you making it big in either ecosystem and custom development comes with the requirement of targeting for both iOS and Android.
That is, all substantial orders for custom mobile application development have requirements to be on both platforms at once. And without custom app development you will not get through the time it takes to start making enough in either of the stores.
Also, VC will not invest into any new mobile app anymore. It's not 2009. It's essentially useless pitching any(well... most) mobile app ideas.




Member since:
2005-07-06
I don't know how many devs would go Android first. I know that when it comes up to try to do something on mobile, I only do Android (and mostly ndk at that). Why? It's good (from a dev point of view - well, at least my dev point of view
), mixing native and java (latter mostly for the ui) is relatively easy (I mean c++ through jni), it's affordable (good emulator, affordable devices to test on, no developer fees). Of course, there could be a chance I would change my mind if I were to develop mobile apps for a living, which I don't, since in that case my choice would be strictly the given OS's market share on the specific market I'd target.