3 ms·
I 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 Pyth
by mclin 17y ago
I 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-...