-
There is truth to this, but I think it’s absurd to think that a third-party toolkit that failed to keep up with Apple’s APIs and produced poor quality apps would ever be popular. Why would users and/or developers willingly choose to use an inferior product? And if they do, so what? No one is forcing you to use them. Further, the vast majority of applications written for the iPhone *have* been written using Apple’s tools, before these changes were made to Section 3.3.1.
Are these imagined advantages worth the consequences?
Many (if not most) developers do not view a company that is blatantly trying to “lock them in” favorably. It is not a virtue that people respect. If I were to write an app for the iPhone, I would choose the tools that I deemed “the best”, voluntarily, and that probably means I’ll use Objective-C and Xcode. But the notion that those are the only tools that I’m allowed to use scares me, and it seems, many others.
—
Tao Effect Blog » Blog Archive » Steve Jobs’ response on Section 3.3.1
Fair and thoughtful points worth considering. However, you lost me at Firefox. Firefox is exactly the right example of what Apple doesn’t want; a relatively good app that doesn’t conform to the native OS tools and standards. Firefox may me improving but years with out OS spell checking, poor copy, past and drag-and-drop as well as the lack of OS services is indicative of the failures of writing a tool to be cross platform and hacking it into compliance.
Evernote is another example; I love Evernote and it’s getting better every update but it still doesn’t feel like an OS X app in the ways that Soho Notes or MacJournal do. Yes their iPhone app is stunningly good and well integrated with other iPhone services and apps.
-
howardtharp liked this
-
christopherdwhite posted this
