I'm not particularly an Apple fan boy, but I do admire their design decisions. Apple has an _uncanny_ ability to take a block of marble (a set of features for a phone) and grind away at it until what's left is a minimally complete set of features that are (in general) perfect.<p>I was definitely the first to gripe and complain when the iPhone didn't have cut and paste, but I'll also be the first to admit that they _did_ get it right when they finally released it.<p>I was also one of the many loud voices complaining that I couldn't run backgrounded apps, but when you look at the HTC phones coming out right now running Android and full backgrounding, and you hear the stories of how the battery runs out by the early afternoon, you start to realize that, it is true, "it is easy to add <feature x>, but it is hard to get it right" (or whatever it was that jobs said in his announcements)<p>I'm not saying that the features in Android aren't impressive, they very well may be, but Apple's design decisions don't just go after "impressive", they try to go after "perfect", and sometimes getting features perfect means cutting them until you're ready<p>Your entire post is targetted as "features that developers want" and you're right, you need a healthy ecosystem of developers, and Google is certainly building one. However, you also need a healthy ecosystem of consumers who love the product, and at the end of the day, I really think most developers will go to the platform where they can reach the widest audience. Apple cares about their consumers first, and their developers second (and sometimes it feels like second last), but it seems to work for them...<p>edit: of course, sometimes apple's PR doesn't respond to consumers as best as it could (i.e. the "you're holding it wrong"), but I'm trying to focus on design/product decisions