Archive for April, 2010

Steve Jobs and Adobe Flash: Our thoughts

Thursday, April 29th, 2010

I wanted to provide everyone an update on the issues related to the iPhone 4.0 Terms of Service. While we have yet to receive any formal word from Apple as it relates to Titanium, this morning, Steve Jobs posted some thoughts on why Apple is banning Flash on the iPhone/iPad. The focus of the article is on making two important arguments: how to ensure a high-quality iPhone experience and the importance of using open technologies. Based on his piece, we have a few followup points as this news relates to Appcelerator Titanium.

- If there was any doubt, Apple’s specific target is Adobe Flash.

- At the crux of every one of Jobs’ points is one overriding theme: ensuring application quality. More specifically, Apple wants to make sure that applications written for the iPhone/iPad are developed using all the great features in the iPhone SDK and that they should not be developed using a lowest common denominator approach. We couldn’t agree more. Split views, popovers, cover flow views, native table views, native maps, native tab bars… There are over 2,000 methods and properties available to Titanium developers to customize their applications with almost every native Apple UI or feature imaginable. And if something isn’t in there that you need, it’s easy to extend the platform by building a native Titanium module. This extensible, native architecture is probably the reason you chose Titanium in the first place. One of the most common statements we hear about Titanium: “You built *that app* in Javascript. Wow!”.

- As it relates to adoption of new iPhone capabilities, we rev our product very quickly. In fact, next week, we’ll introduce support for iPhone 4.0 application development with Titanium 1.3.0. And we’ll continue to add new APIs as Apple finalizes the 4.0 OS. This has always been the case with our stance on updates to the underlying operating systems that we support. In all cases, we are working with Apple APIs under NDA before they’re finally available to the public and we’ll continue to do that as normal.

- Apple has a clear preference for open technologies, specifically HTML5, CSS, and Javascript. Here too, we are in alignment. Titanium developers code in Javascript as executed by the Webkit engine (eg: the kind that Apple prefers in its ToS), and web content can easily be displayed using HTML5 and CSS through a web view. We’re big supporters in these technologies and ourselves have contributed to WebKit (Martin Robinson, one of our desktop engineers, is a WebKit committer).

- We’ve had over 50 applications approved for the App Store over the past 3 weeks under the new terms (which every developer now needs to agree to). Not a single one has been rejected for being built on Titanium. We even updated our own test app, Snapost, after accepting the new terms.

In summary, Apple is targeting Flash (mission accomplished) and Apple wants to push their platform forward by having only high-quality, native applications in the App Store.

We couldn’t agree more. Native application development with open technologies is in our DNA and our continued vision for Appcelerator.

- Jeff

Backend Issues

Monday, April 12th, 2010

We’re having some very unusual Amazon EBS volume issues that we’re working to resolve. Unfortunately, this seems to be impacting several different services. We’ve gotten almost 13 servers on Amazon for high-availability but it seems we’ve run into another issue which we didn’t anticipate with the EBS volumes. One of the volumes is reporting out of space, while it appears we’ve allocated plenty of space. We’re hoping to resolve this ASAP. Thanks for your patience.

Update on Apple SDK 4.0 and ToS

Friday, April 9th, 2010

It’s our belief that we are fully in compliance with iPhone OS 4.0 ToS as we interpret them.

We agree with others that the intent behind the language is probably aimed at Adobe and preventing Flash from landing on an iPhone/iPad and bypassing or otherwise circumventing the iPhone SDK.

As a pre-requisite to using Titanium, developers must install the Apple iPhone SDK and Apple XCode development toolchain. They must install Titanium on a Macintosh and they must have a valid Apple Developer membership before they are even able to create a Titanium-based iPhone/iPad application.

Titanium produces a valid XCode project at application creation, generates Objective-C (and sometimes C/C++) and executes the xcodebuild to compile your XCode project into a native application using Apple’s published APIs. We launch the Apple’s iPhone simulator to test your application, create the correct Apple binary for integration to iTunes when testing your signed application on device and use all the certified Apple tools for signing to create the final distribution. The developer must obtain their own Apple signing certificate for creating applications with Titanium and Xcode and the developer uses their own Apple iTunes Connect membership and login to upload the package to Apple for submission.

We believe Titanium adds value to the Apple Development ecosystem and enhances the Apple platform for many thousands of developers around the world. As we always have, we will continue to work with Apple to ensure we stay in compliance with their terms of service.

iPhone OS 4.0 Announcement and Our Commitment to You

Thursday, April 8th, 2010
Please find the latest update to our position on Apple SDK 4.0

First, and most important: we value each and every one of you. As always, we will do everything within our power to ensure that Appcelerator Titanium remains the best platform to enable each of you to develop mobile and desktop applications on. Should any issue arise that may affect our community, you can expect that we will be as proactive, transparent, and forthcoming as possible.

Now to the issue at hand. As part of its announcement this morning, Apple proposed updating its Terms of Service for iPhone OS 4.0. Since iPhone 4.0 is still in beta, both the APIs and the Terms of Service are covered under NDA, so we cannot speak to specifics or Apple’s intent with its proposed language. However, these terms are subject to clarification and change by Apple up through its official launch, which looks to be mid-summer. Until iPhone 4.0 is actually released, we will work with Apple to ensure that we abide by any updates to its Terms of Service, just as we have done successfully in the past.

We know that you put a lot of trust in Appcelerator and effort into your applications. You have our commitment that we will do everything possible to ensure that Titanium remains the outstanding platform for cross-platform application development for years to come. We will update you with more information as soon as we gain a clearer understanding of today’s announcement. Until that time, iPhone OS 3.2 remains the officially released SDK and 3.2 is still the official Terms of Service. All apps written under 3.2 are in accordance with these terms and all apps written to date for 3.2 have been approved.

Please feel free to reach out to us on our blog, via Twitter, or via email with any questions. Thanks for everyone’s support and well wishes today.

Best Regards,

Jeff Haynie
CEO
Appcelerator, Inc.

Apple 4.0 and Titanium

Thursday, April 8th, 2010

By now, most of you have probably seen or heard about Apple iPhone SDK 4.0 and a little hidden gem in their freshly minted 4.0 Terms of Services, notably 3.3.1:

“Applications that link to Documented APIs through an intermediary translation or compatibility layer or tool are prohibited.”

It’s clear that products like Titanium, Unity3D, Ansca, MonoTouch and others are now a bit in question for iPhone 4.0+ with this language. We’re all trying to get our heads around what this means and trying to reach out to Apple to get clarification.

Hang tight, we’ll try and give you more information as we can figure it out from Apple. We don’t want to make any false promises or claims – and most importantly, we want to make sure we’re abiding by Apple’s rules.

[NOTE: I have posted an update here]