>>You’re looking at it wrong. You’re looking at it as a hardware person in a fragmented world. You’re looking at it as a hardware manufacturer that doesn’t really know much about software, who doesn’t think about an integrated product but assumes the software will somehow take care of itself. And you’re sitting around saying, well, how can we make this cheaper? Well, we can put a smaller screen on it, and a slower processor, and less memory, and you assume that the software will somehow just come alive on this product that you’re dreaming up, but it won’t. Because these app developers have taken advantage of the products that came before, with faster processors, with larger screens, with more capabilities that they can take advantage of to make better apps for customers. And they’re not… it’s a hard one, because it throws you right back into the beginning of that chicken-and-egg problem again, to change all the assumptions on these developers. Most of them will not follow you. Most of them will say, “I’m sorry, but I’m not going to write down a watered-down version of my app just because you’ve got this phone that you can sell for $50 less, and you’re begging me to write software for it.”<<
http://www.macworld.com/article/154980/2010/10/jobs_transcri...
Now, what they conceivably could do is to look at their aftermarket software and devote less resources to that -- especially in places where Apple's presence in the aftermarket doesn't make or break the platform (e.g. music sequencing -- there are half a dozen mature competitors to Logic that run on OS X). Also, I suspect some of those places Apple is in strategically because it funnels money away from companies they don't like -- Aperture cuts away from Adobe and iWorks pulls away from Microsoft, despite Photoshop and MS Office for Mac being platform-completing tools. Also their offerings there are important as leverage; Apple doesn't want to be back in the position of needing Microsoft or Adobe since they've been burned in the past.