4 ms·
I strongly disagree with you. How many Android apps did you develop? Do you know the newer Android tool chains? Just the non-resolution-independent framework o
by fisherprice 13y ago
I strongly disagree with you. How many Android apps did you develop? Do you know the newer Android tool chains?
Just the non-resolution-independent framework on iOS is a big pain and iOS biggest bottleneck and this is where Apple struggles right now (to make the next bigger iPhones happen).
But your post shows very well again the general attitude of iOS folks and it's your pure fear which speaks out load -- your fear that your dev experience and skills in iOS will be less worth very soon and you have to start at zero again, on Android.
Edited: btw downvoting != disagreeing
- 37prime 13y agoCan the post get any more subjective?
- theswan 13y agoI think downvoting != disagreeing to the point, but rather, downvoting = disagreeing that this article is worth the time to read.
- interpol_p 13y agoI didn't down vote anything, so I'm unsure what you're referring to there. I haven't touched Android development for a few months so I might be out of date. In particular I very much disliked their scroll view and list view implementations. I found Android to be a mess in general, API wise. Things seemed much more ad-hoc and less thought out than on iOS. And I have some very specific disagreements with their API design choices (or lack of them). As I mentioned in my original post, Android seems to lack the built-in high-level rendering, audio, typography, language and other frameworks of iOS. I've never found the screen density stuff to be an issue on iOS — I always design and render my UI elements directly as vector graphics (PDF). This is almost impossible to do efficiently on Android (no native PDF rendering API). I really have no idea what you're talking about when you mention my "fear." I am more than happy to develop on any platform. I just find Android much worse than iOS at the moment. If it gets better I'll happily switch.