3 ms·
I also agree with this idea. If you are going to be charging for your app and want to make a revenue stream off the start before expanding, I think iOS is the b
by wapz 10y ago
I also agree with this idea. If you are going to be charging for your app and want to make a revenue stream off the start before expanding, I think iOS is the better choice. If it's going to be free and you are looking for a big user base then Android will be a better start. The other factor is Android is quite a bit easier for most to get into (but with fragmentation it is a pain to make quality apps) -- Java and any OS compared to obj-c/swift and a Mac.
- m_mueller 10y agoI have to disagree on Android being easier to get into. The standard libraries and tooling (especially emulators and profilers) are dumpster fires compared to Apple's offering. Just some examples: Non-Web Javascript integration is a third party library. HTTP requests are a third party library. Everything that needs native resources in the JVM goes through an interface called JNI that has a 512 entries limit in the reference table, often requiring you to do manual reference cleanup in your hot loops.
- wapz 10y agoI think it really depends on what the op is looking to make. I made the generalization mostly based on the OS and languages (most universities starting from at least 15 years ago taught Java in at least a few classes whereas objective-c and swift are only iOS specific). I haven't had to deal with your specific examples but I suppose in your case iOS might be easier. I still believe overall Android is easier to get into for the "average" person.
- m_mueller 10y agoIMO, for the average person, doing iOS with Swift will be easier, except, and only for some simple usecases, if that person is already experienced with Java.