31 ms·
From what I've seen of the CS5 packaging for iPhone, there are no native UI controls. Adobe claims to have a project to port Flex to iPhone, and I can't assume
by wallflower 17y ago
From what I've seen of the CS5 packaging for iPhone, there are no native UI controls. Adobe claims to have a project to port Flex to iPhone, and I can't assume that it will use native UI controls. Since the iPhone is all about the rich user experience, perhaps by limiting access to the AppStore for prior-life Flash 2D games, Apple is protecting the dilution of the quality of the games.
As for the other build an iPhone app application frameworks, the quality of the finished product varies from lackluster to average. At the worst, the finished app looks like one of the RSS reader apps that Apple is now trying to filter out of its AppStore. At the best, it's something like Location Scout. I believe by limiting access to third-party application builders, Apple is going to continue to increase the quality of iPhone apps. Titanium, Adobe et al will never generate anything like Tweetie 2. And, I believe Apple wants more Tweetie 2-caliber applications. To increase the S/N ratio. I believe Apple wants less crap and cookie cutter applications, even though some of the top 25 Free and Paid lists may from time to time have those types of 'Fart' type apps.
Apple is a premium brand. Even for developers. There are barriers to developer entry. It is kind of a privilege to write iPhone apps as you need $99/yr and an Intel Mac. The Cocoa/UIKit framework and CoreData persistence are tools that Apple engineers have invested centuries of programmer years in developing. There aren't many private APIs in Apple land; almost all of the standard iPhone apps could be recreated by third-party developers. And now with OS 4.0, I believe only a small fraction could not be recreated. As another example, Titanium et al. are not using CoreData - CoreData is designed to make managing and persisting an object graph easier. Which is what you need for non-cookie cutter applications. I have yet to find one application built on RhoMobile, Titanium, Ascena etc that leverages CoreData.
And, I wouldn't be surprised if they start rejecting apps for quality (as in what does this app provide that is of value).
"He downloaded Titanium on a Saturday morning, and by Sunday night he had a functional prototype of his Location Scout app..."
http://www.appcelerator.com/partners/case-studies/locationscout/ http://www.appcelerator.com/partners/case-studies/locationsc...
http://labs.adobe.com/wiki/index.php/Applications_for_iPhone:Developer_FAQ http://labs.adobe.com/wiki/index.php/Applications_for_iPhone...
- rimantas 17y agoFrom what I've seen of the CS5 packaging for iPhone, there are no native UI controls. Adobe claims to have a project to port Flex to iPhone, and I can't assume that it will use native UI controls. Adobe did not even bother with their own apps, just visit http://adobegripes.tumblr.com/ http://adobegripes.tumblr.com/ A couple of telling examples: http://adobegripes.tumblr.com/post/296745150/photoshop-why-is-the-file-info-panel-made-in http://adobegripes.tumblr.com/post/296745150/photoshop-why-i... http://adobegripes.tumblr.com/post/236090781/the-many-sliders-of-photoshop-cs4 http://adobegripes.tumblr.com/post/236090781/the-many-slider...
- mclin 17y agoI hope you're not implying that the speed of development is an indicator of bad quality. Any environment where you're working with JavaScript (or Ruby, or Python...) is going to have faster dev time than working with a compiled language. It's not just having to type way less, but less brainless typing leads to better flow. I'm doing both right now, and I love Titanium because it gets me in the zone, whereas with ObjC, so often I have to turn on autopilot to get through the boring stuff when I create a new model or class or something.
- wallflower 17y agoReading all the comments posted on this thread, I'm starting to change my mind. It's not the quality (Titanium mobile apps are nearly indistinguishable from most iPhone apps), the speed of development (like you said, not having to use Objective-C). Unfortunately it is probably protectionism. To protect the dominance of the AppStore. If you can simultaneously write an Android and iPhone app using the same Titanium/Kroll codebase, you're helping to weaken the AppStore (which is arguably the main tent pole of Apple's strategy to dominate computing in this century). "When Apple’s SDK was introduced in July 2008, the company tried over a period of several months to get a basic app up and running. Notes Bart Johnston, Director of Interactive, “I thought that my web development experience would have prepared me for developing on the iPhone, but it felt like I was starting completely from scratch. The learning curve was very high." Does Apple really want to officially allow Titanium to lower the barrier to entry? Premium brands cannot be premium if everyone has access. http://www.appcelerator.com/partners/case-studies/lone-star-beer/ http://www.appcelerator.com/partners/case-studies/lone-star-...
- glenra 17y ago> "He downloaded Titanium on a Saturday morning, and by Sunday night he had a functional prototype of his Location Scout app..." Getting a functional prototype to work should be simple and fast. (There's a big difference between a functional prototype and a finished product!) The fact that it's not fast using the Apple toolchain is exactly what's wrong with them. Developer time/effort is limited. A good dev environment should make the common stuff easy; since Apple seems disinclined to provide tools that do this themselves, our big hope for improvement in that regard was that third parties would get in there and fix the problem with products like Corona or Titanium.