>You are now only looking from the perspective of a developer. I have >yet to find a single non-developer who cares about the vendor lock-in >which currently applies to iPhone development. The only thing some >people find annoying is the fact that some applications are not >available, but most of the time they even don't know why that is the >case.
Looking at the situation from the perspective of a developer is not irrelevant in this issue. I have yet to speak to a non-developer or non-techie who cared about Microsoft abusing its monopoly position. That doesn't mean that it was a non-issue for end users. IMO there's a greater issue at stake: that it's innovation that matters for and benefits end users in the long run. I think most here would agree monopoly abuse stifles innovation. I think opinion would be more divided about some of Apple's policies, but it's definitely a debate worth having - whether or not end users of today are affected. >I really find it hard to see the benefits for the end user of having >multiple appstores. If that would be the case, you would have to check >several 'app stores' in order to find out if there are new interesting >applications. Of course, it would be nice for developers who doesn't >like the Apple regime, but for the end user I, the only benefit I see >is the possibility of lower prices for apps (but currently that isn't >really an issue), but that does not compensate the downsides of >multiple app stores. End users have their choice about which device to buy, and may or may not be aware, or even care about Apple's policies with regard to the app store. They may not want the complications that multiple app stores bring. They may even like that Apple has total control, if it makes them feel there's a barrier of quality for every app they install (though I hear there's no shortage of crap on the App store). Granted, there is the argument that today's users of Apple's devices do benefit from those policies which we developers do not agree with. That does not mean, however, that developers should shirk the responsibility of keeping an eye on the future of innovation, just because today's users are satisfied. Or that we should not raise our concern if we feel fellow developers are falling into a sharecropper model. Or disagree when a company chooses the languages developers are permitted to use for business, not technical reasons. For example, the EU forcing the Windows browser-ballot is arguably just an annoyance for many users who don't care, and just want to get online, but that doesn't mean it's not the right thing to do for the future of innovation in software. To bring this rambling mess back on point, Android outselling iPhones probably has little to do with user's considering their app store policies, but that doesn't mean "only" looking at it from perspective of a developer. Kind regards, Graham -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
