3 ms·
Like the op, I do both iOS and Android development work. However, as an indie, my platform preference is primarily market-driven. So most of my work has been on
by credo 10y ago
Like the op, I do both iOS and Android development work. However, as an indie, my platform preference is primarily market-driven. So most of my work has been on iOS
Unlike the OP, I like and use Android AsyncTasks. I have no problems with Android fragments either.
However, I did have a lot of other concerns with Android - primarily the low quality of Google's SDK for Android. Here is what I wrote about it
https://blog.cascadesoft.net/2013/12/31/the-bigger-problem-with-android-bugs-and-quality-not-fragmentation-per-se/ https://blog.cascadesoft.net/2013/12/31/the-bigger-problem-w...
- popmystack 10y ago>primarily the low quality of Google's SDK for Android. This has always been my biggest frustration with Android. I've written a few applications for the platform, and while their architecture leaves a lot to be desired I've never had any real problems with it. However, the immense disappoint and anger that comes from their SDK idiosyncrasies is astounding. Google really just hates stability and nice API's, in my opinion. Everything from GAE to Android, it's always just so terribly frustrating to keep track of any one-off decisions they make without any form of actual communication from the development team. I've been writing Android code since the G1 days.
- cloudjacker 10y ago> However, as an indie, my platform preference is primarily market-driven. What do you mean? Where craigslist entrepreneurs and seed stage startups want iOS apps?