Update on Apple SDK 4.0 and ToS

information superhighway

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.


  1. […] by Jeff Haynie on April 8, 2010 Please find the latest update to our position on Apple SDK 4.0 […]

  2. 100% agree with what you have said above, it will be a real shame if Apple’s dispute with Adobe shut down such a valuable tool.

    I’ve tested my Titanium based app, and several of the showcase ones and they all fail on OS 4.0, they load up the splash screen then fail…

    I’d be interested to know if you think this is just because they are made for 3.2 or if you think that Apple has already put blockers in place for this?

    I’m presuming you guys are also unsure whether to spend time developing your product to work with the 4.0 SDK if it’s not going to be supported!

  3. We haven’t yet pushed Titanium support for 4.0. Since it was just released yesterday, it’ll take a few days to test it given we’re in the middle of a maintenance cycle already. But it should be soon — probably today on Github.

  4. […] Titanium goeth, I go too.  Either you let me do mobile apps in a language I already know, or I don’t […]

  5. If the developer publishing the app did not write the app in objective-c or the other supported languages, or JavaScript for a webview then you are indeed violating the terms regardless of how your translation layer actually builds the app.

    Hey, invest a month or two in your app and see it get shut down if you disagree.

  6. just found you because of the whole new apple sdk mess.

    titanium seems to be a great way to make desktop and mobile apps. and using js as the base lang makes it very, very easy.

    good bye flex, air and the whole closed source rest!

  7. I also completely agree that this is an effort from Apple to block 3rd-party compilers (not xcodebuild) from bypassing the iPhone SDK.

    Standing by y’all 100%!

    Even from an Obj-C programmer, the rapid development of apps using the Ti platform is simply unparalleled. I honestly hope this is the future of all development.

  8. Hi Jeff,

    it’d be interesting to know if you talked to Apple about this, or are in the process of negociating with them?

    PS: Thanks for everything you are doing for iPhone development 🙂

  9. Can you tell us if you have spoken to Apple re: the new TOS and how Titanium would be affected.

    I know many people, included yourselves have interpreted section 3.3.1 in their own way but we really need to know how Apple interprets it.

    I would think many people have stopped development until they have a definitive answer from Apple.

  10. Hi there Jeff,
    If you have an OS4-compatible app from your testing (i.e. Snapost) is there any way that could be passed under the noses of the apple to verify our understanding?


  11. http://www.appleinsider.com/articles/10/04/09/apples_prohibition_of_flash_built_apps_in_iphone_4_0_related_to_multitasking.html

    “The primary reason for the change, say sources familiar with Apple’s plans, is to support sophisticated new multitasking APIs in iPhone 4.0. The system will now be evaluating apps as they run in order to implement smart multitasking. It can’t do this if apps are running within a runtime or are cross compiled with a foreign structure that doesn’t behave identically to a native C/C++/Obj-C app.”

  12. Karlo, interesting link to AI and who knows, maybe it’s right. If you read through the comments though, there’s some serious skepticism.

    Again, I’m happy to see what people are saying on this, but just hope others don’t come here, read that quote, and think that’s definitely Apple’s thinking. Why won’t Apple comment…

  13. I too hope Apple rules that Titanium is on the right side of the TOS language.

    Until, of course, Apple changes the clause to read:
    “iPhone native applications must be manually typed on a QWERTY keyboard in Objective-C/C++/C. The developer may not copy/paste any code snippets or import/link any previously written C libriaries; every line must be hand-typed.” Then we’re really screwed 😛

  14. Just want to say thanks to Jeff for communicating so well on this issue. I’ve paid several hundred dollars for a competing product that’s similarly affected, and they haven’t said a word yet.

    Keep up the good work.

    Would also be interested if direct communication with Apple is happening?

  15. @Steve Perlow: Oh I am definitely on board with the skepticism, I’m just trying to share the info. The me personally, in my opinion, this is absolutely (and very clumsily, if that’s a word) intended to eliminate Adobe’s Flash cross compiler solution. I think, from Apple’s business viewpoint, the fact that there will be numerous other (but much much smaller installed base than Flash) cross compiler type tools out there that will also be casualties (Titanium, PhoneGap, even Unity3D and Unreal Engine) of this new policy is, again from their point of view, worth the price.

  16. @Karlo – totally get that you were just sharing the info. I’m searching around for any news or hint of news I can get too! Reading that link was definitely interesting.

  17. Hey guys any official communication yet? When do you think you can get some official info out of Apple?

    Wish you the beeeessstt of lucks and please count on the community here to help on what we can!

  18. I doubt Apple will respond personally to this, unfortunately. They’ll likely just start rejecting certain apps from the store, and we’ll have to catch on why. This may not start happening for X months from now either.

  19. Yeah,

    The difference between Emacs and Titanium is productivity. In the end every line of code is Objective C. It is totally fair game for a developer to abstract native calls within the framework of the application. Apple can’t restrict developers from making sound business decisions to play on multiple platforms. So what is really going on here?

    Adobe will have to open source it’s runtime to get into compliance. It will have to operate and behave like Titanium. Cross platform “write once render the same” flash widgets are out. So if any business or CRUD app gets made it will have to look and behave like a native app period.

  20. The thing is: we have Titanium, phonegap, unity3d, corona-built apps in the app store – Today.

    The ToS states certain things ARE prohibited in the apps themselves (note: not submission/approval is prohibited), so logically there could (if apples interpretation is different) be thousands of ‘prohibited apps’ in the app store on day one of the new agreement. Wouldn’t there be the basis of a case there?

    in the event these apps suddenly become prohibited, apple would have to sift through the store and remove them And how would they do that – open and analyse/re-review every single app binary?

    Process-wise this gets more bizarro: if you’ve used an apparently prohibited tool (or apple THINK you have) when you submit an app you might not get a rejection, you might get banned from the Apple program for breach of ToS(?)


  21. it’s very important for us, developpers, to have a clear answer, perhaps after you clarify the situation with Apple. Because the 3.3.1 says “Applications that link to Documented APIs through an intermediary translation or compatibility layer or tool are prohibited).”

    Even though the target is flash, this quoted text, I think, affects directly Titanium. I hope you can clarify more this situation and we can continue working with titanium.


  22. Chris R:
    They might not have to. The tableviews in my app stopped working in OS4 , so unless Titanium can keep on adding OS4-support I will remove it myself.

  23. Question does Titanium convert JavaScript -> Objective-C, if so it pretty clearly is in violation of the apple ToS, since the terms say JavaScript is only acceptable if its being run by apples JS interpreter.

  24. Apphacker: If the developer publishing the app did not write the app in objective-c … then you are indeed violating the terms regardless of how your translation layer actually builds the app.

    Next step, all the developers need to write their code with left hand only ?? The point is to have a valid objective c code which will be compiled by xcode. How to get it should be secondary (I hope !!).

    Still, if Apple wants to make sure that new apps are coded only with there own tool, they could generate some kind of validation key in cocoa which will be verified during validation no?

    In my opinion, Apple will ask Titanium and others(who compile with xcode) to raise the bar to iPhone 4.0 sdk level, taking in account multi tasking as Karlo pointed out… lot of work ahead!

    At least I’m really happy to be part of Titanium community, it feels safe to be here! Thank you guys, we’re all behind you!

  25. […] Official reactions from PhoneGap, ELIPS, Appcelerator, Unity, and […]

  26. I was about to pay for the Apple developer program, but I’ll give it another thought after the recent announcements. I can understand that they want to ban resource intensive Flash, but this should not affect tools like Titanium. I hope this can be resolved and clarified. It’d be nice to have a written statement by Apple, but I doubt that they would ever do such a thing being more and more restrictive…

  27. I think the big question here is:
    Is this apple trying to eradicate all cross-device portablity toolkits? Because Unity, flash, and even phonegap do something that does not sound like its in Apple’s interest. Lessen the pain and cost of cross-device development. This is not beneficial to apple, or arguably (as seen online) Apple’s customers. Obviously the biggest threat is Adobe, however these terms do not appear to be purely for them.. It looks like a broader strategy. Apple wants developer lock-in, and they want titles 100% optimized for their platform and thus all these toolkits are the enemy. Now the main problem developers seem to have against these new terms is not even the portability aspect, its the fact that they now are prohibited from picking the tools THEY want to solve a problem. Which is a different case altogether, but is the unfortunate victim. What would the response be if Apple would allow these technologies that make life easier to develop applications, but only if they are exclusive to the Apple platform? On another note; isn’t Apple being anti-competitive in the extreme? I thought there were laws against this kind of stuff. Maybe the EU should get on apple’s case like they have done with Microsoft for far less scary stuff. Imagine Microsoft saying portable software violates the windows TOS…..

  28. I find the prescription that one has to originally write i Objective-C to be draconian. I know Objective-C (and many other languages) and don’t really like it at all. Despite spending a lot of time reading it, I find it very hard to mentally parse compared to, say, Python, or even well-written ANSI C. And knowledge of Objective-C really doesn’t help you anywhere else, save the Mac itself.

    When I wrote my app, I used C for the bulk of the code (after all, the OpenGL and Audio calls I was using from Apple are C libraries) and Objective-C where I had to. Since I had to alloc and free memory anyway (only the Mac has the Obj-C garbage collection), I figured I might as well actually be able to SEE the mallocs and frees, instead of guessing what was holding on to memory and what wasn’t.

    Suppose I write in haXe (which is very much like ActionScript and JavaScript) and compile it to C++ source (which is one of the haXe options). What is wrong with that generated code compared to the C I might write? It’s probably better quality code, since I can think in a higher level language that lets me, say, return an array or an object from a function. With haXe I could port the heavy-duty logic elements to C (for iPhone and Android’s Native), to JavaScript (for Palm and the web), and to PHP for cases where some code that has to live on both the server and the client need to share code that I don’t want to write twice.

    I find that clause about what the app is originally written in preposterous.

    Imagine how you’d feel now if you spend $400, or $1000, or $5000 on MonoTouch and got up to speed in what is a pretty cool modern language (C#) designed by the guy who did all those great Borland compilers.

    My gut feeling is that Apple’s moves make me want to write apps for all other phones, but webapps in HTML5 for iPhone and iPad.


  29. Have appcelerator checked the logs for potential signs of apple folks using developer to train themselves on how to identify a Titanium-assisted app?

  30. I wonder if Titanium could be changed to produce Objective-C that really looked like code rather than the JavaScript interpreter hex that it is. If it compiled the JS into objective C directly, and automatically helped us launch the apps faster than in XCode, they would get around the TOS. I suppose this would be a tough row to hoe.

    I used to hate JavaScript until I started doing Ajax stuff. Now I’m very impressed with it, and I love the idea of writing iPhone apps in it.

    Thank you Appcellerator. You do us all a great service.


  31. Just keep us posted, as you guys have.

    We have a lot on the line, 10+ apps in development. We hope to keep using titanium, we love your product.



  32. @Rhett Anderson,

    Not sure how tough it is but perhaps the Appcelerator folks could rework Titanium with (as simple as possible) guidelines for javascript development such that you can only use a subset of the language that can be 100% translated to the native language paradigm.

    Things like “don’t access objects’ prototypes”, “isms” to enforce strong typing like naming your variables “var name_string”, “var count_int”, etc.

    It would kind of suck, but I’d still rather be coding something high level than low level.

  33. After seeing the presentation on multitasking features to come in 4.0 I’m wondering whether Apple’s motivation to only allow Xcode-built apps is so they can be sure apps will fit in with their mechanisms for multitasking, suspending, switching, etc.

    Would there be any difference between a Ti app and an ObjC app in this regard?

    I’m split on this. While I applaud Apple for shunning flash apps with their generic UI (and poor performance), I hope they see the benefit of Titanium’s native UI and the great utility and development speed it affords. If they insist I use a development environment that doesn’t have self-contained memory management they will lose me. ObjC, for me, is obtuse, verbose and cranky.

    Jeff, thanks for communicating with your fan-base so well. I hope we can get certainty that Ti apps will get through approval at the app store.


  34. I really hope Appcelerator will have a good answear from Apple, really really hope.

    For now, all my devs are stop until a response at this question : will Titanium survive at this anounce ????

    Please give answear fast as you can, can’t wait more longer…

    Anyway, you did (and will do) a great work with Appcelerator, i love your job and the solution you give us, so do all you can do,


    Vivien Brissat from Atonis Technologies

  35. I don’t see how Appcelerator can be hurt by this news. To me, it seems more validating than terrifying. Apple wants apps written in Obj-C and Javascript that can be run by Webkit. Titanium doesn’t recompile to Obj-C like Adobe was trying to do. Instead, the Appcelerator folks provide a javascript interpreter written in Obj-C/Webkit using exactly the technologies apple wants us to use. To outlaw titanium would mean outlawing all objective c libraries not built by apple, and that’s just ridiculous.

  36. Sounds like a to be or not to be question to me…

    So apart from all the speculation…

    If all goes well, then Appcelerator and the rest of us have nothing to worry about but if not and I don’t mean to sound like a pessimist; what then?

    What would the possible plan B or C be Mr. Haynie?

  37. Appcelerator Titanium is truly wonderful tool so Jeff, thanks to you guys for providing us with that. But I have a question about future of Titanium.

    Suppose, In the end we come to know for sure that Appcelerator apps are not in compliance with section 3.3.1 . Will then Appcelerator still continue to keep updating their tools for android and blackberry platforms?

  38. I think this is buh-bye for Titanium Apps. Steve Jobs cited this post as a good explanation behind their reasoning for the change.


    From the post:
    “So what Apple does not want is for some other company to establish a de facto standard software platform on top of Cocoa Touch. Not Adobe’s Flash. Not .NET (through MonoTouch). If that were to happen, there’s no lock-in advantage. If, say, a mobile Flash software platform — which encompassed multiple lower-level platforms, running on iPhone, Android, Windows Phone 7, and BlackBerry — were established, that app market would not give people a reason to prefer the iPhone.”

    I think that’s a pretty good explanation. This is what happens when you guys focus on catering to companies like Apple. Perhaps you should have focused more on Maemo and continue to support Android. Abandon Apple while you can.

  39. It’s rather weird to see Apple’s attitude regarding apps there, do they have such little faith in the value of the actual device?
    Do they truly, honestly think that a user would be swayed towards a Windows or Android as their next phone because there was a tweetie app for it? As if the display, the OS itself, the battery life, the camera, the weight/balance, the OS itself, how it responds to gestures, are insignificant to customers choosing a mobile phone.

    Jonathon Ive reading that must wondering why he bothered.

  40. […] Appcelerator about Titanium: It’s our belief that we are fully in compliance with iPhone OS 4.0 ToS as we interpret them. […]

  41. This post is willfully misleading your customers. There is no chance Titanium produces code “originally written in C/C++/Objective C”. What you’re doing is exactly the same as MonoTouch and Adobe.

  42. I’ll be surprised if Apple doesn’t get an anti-competitive lawsuit over this, they just killed analytics and 3rd party development with their new TOS

  43. @Anon

    I wondering no, but it seems that other solutions gave another responses, and i think Titanium is more “valid” than other


    (in french, so Phonegap said “it’s OK, we pass ToS”)

    Is it true ? Or just some kind of “sand in eyes” ?!?!

    If phoneGap is OK for ToS, i really don’t know why Titanium would not…

    But the silence of appcelerator Staff make me in doubt…. :/

    I just decided to rewrite my app in Objective-c, but it’s lot of work :/

  44. Yeah… After going over 3.3.1 a few times and looking up some Articles that Steve Jobs endorsed (more or less) I think its pretty straight forward. They mean to kill ALL platforms that translate into Objective-C. This makes me both angry and sad. It was not so long ago Apple survived ONLY by Adobe products and if they had not developed for MAC in its pre and just post OSX days. The company would of died. Nice to see how they repay the support in the end. This is not limited. to Titanium. This is a big black eye to Unity 3D as well. Currently they are safe in terms of game designs for the MAC. But Kills there iPhone and iPad development.

    Accelerator, get some direct, straight answers, IN WRITING, from apple quick or forget about the apple platform entirely. And focus on all others so you can survive. Like i said sad. But if thats the ego game they want to play then there is nothing much that can be done except for Class Action Lawsuit.

  45. I truly look forward to see Titanium face the Section331 storm. From my experience, I would like to have (and buy) a Titanium app dedicated to the iPhone platform. Crossplatform is a dream, but it doesn’t work out of the box. Considering the same app on the iPhone vs Android I can see that porting the app to Andoid requires pretty much code rewriting. In France where I live nobody cares about Android Apps that are not mainstream for the moment. What we need is a main Appcellerator framework/suite with dedicated software for each platform to complie precise requirements from mobile manufacturers. What Apple did today could happen again with someone else.

  46. @Brad, I agree.

    Android and other mobile platforms are catching the iPhone pretty quickly and I would love to use Titanium to develop for these platforms if full support was given for them.

    I think Steve Jobs has given us a clear answer to what the TOS mean and it’s now time for you guys to forget about Apple and concentrate on Android and the many other rising platforms.

    Open source and freedom of choice will win in the end.

  47. Since TechCrunch’s permalinks (re: my post above) to comments don’t work when they paginate them, I’ll paste my whole comment here:

    Just some facts about Appcelerator’s Titanium tools and their app creation process, which we hope will see them on the safe side of Section 3.3.1:

    “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 (*.xcodeproj) at application creation, generates Objective-C (and sometimes C/C++) and executes the xcodebuild to compile the XCode project into a native application using Apple’s published APIs.”

    The tools launch Apple’s iPhone simulator to test applications, create the correct Apple binary for integration to iTunes when testing the signed application on a device and uses 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. ”

    via their developer blog : http://bit.ly/cVfY0w

    Adobe’s CS5 however, would allow developers to build iPhone app on Windows, which I’m sure is an absolute no-no. The process appears to be quite a kludge (of the AIR publishing process), from what can be seen in this tutorial by Lee Brimelow (who was extremely vocal about his disdain for Apple in a recent blog post: http://theflashblog.com/?p=1888 )

    See his tutorial on Adobe’s app creation process here : http://gotoandlearn.com/play?id=116

    One thing to note after watching this tutorial is the resulting iPhone app filesize of the (less than 20 lines of AS3 code) Flash app: 3.2Mb !

    That’s pretty big for what it is! And this makes me wonder what else Adobe are bundling with the app. Possibly its ‘LLVM’ (a low-level virtual machine – which is known as an ‘Ahead Of Time’ compiler – see here from Adobe: http://bit.ly/MQtRZ – as opposed to a ‘Just In Time’ compiler, which is effectively what the desktop Flash player is)

    I have been using Titanium to create a far more complex app than this example for the iPhone, which is capable of doing some things that none of the other potential offenders’ platforms are possible of doing (taking and manipulating photos, recording videos, recording audio, etc.etc) which I write in JavaScript, which then gets compiled using the process stated above to create a proper, signed iPhone app for submission to the AppStore.

    The resulting file size of the app? Only 1.6Mb. Amazing.

    Another key issue here is that Titanium is completely open source, compared to Adobe’s very much closed platform.

    ps: I’m not a Flash hater at all. I’ve built many useful things on their platform for many years – when it makes sense to. And I agree that desktop performance of it can be awful – what with web pages and blogs literally riddled with them, often causing any browser to crash.

    Adobe should concentrate on making their tools support the output of HTML5 (please, please without the ‘code bloat’ which Dreamweaver exports HTML!!)

    I have had no experience of Monotouch or Phonegap, though from what I can gather, Phonegap (which is extremely simple, yet limited to what it can actually do beyond what a browser/webapp can do – but with some hooks into a few of the hardware APIs) might also be on the safe side too, since they ironed out issues with Apple a while ago.

    I fully support Appcelerator and their Titanium tool for iPhone app development. I have found it to be the most exciting and enabling project I have ever seen in many years (15) of mobile and web development.

  48. For Phonegap, these guys are holding on the the fact that Apple presented the Phonegap Webkit to Objective-C api bridging method at WWDC 2009 as ‘the way to do such communications’ And of course the fact it had some apps accepted at the Appstore. However i find this a pretty weak basis to claim Phonegap is OK without explicit approval. The Apple developer relations guys that did these presentations, are hardly something you can hide behind when the policy changes higher up. So whenever you see ‘Phonegap is OK’ its just based on this, nothing more. Seems to have permeated the media though.

  49. Is there any *official* update/statement from GestApple?
    Belief is a good thing, but written documents are better when basing a business on a platform..

  50. Thanks Kosso for this positive and optimistic attitude. I hope your well argumented demonstration is right and that we’ll be able to still develop mobile apps with Titanium for iPhone. I spent 4 month on a project using Titanium and I recon that I don’t know what to say to my client. Should I keep on working this way or try to learn Objective C that sound very difficult to me. Titanium development is fast, fun and intuitive, well adapted for light applications. I would be really disapointed if was forced to give up.

  51. @Kosso

    I am totally agree with you. Titanium is the most exciting project i ever seen since many years, i started recently to make some apps on desktop with it, wonderful.

    @michel Perrin

    I am in the same situation. Want to learn Objective C, but the market right now need a fast development cycle, that i can’t do with native Obj-c for now : i know all i can do in Obj-c will never be optimised like titanium apps until i know well Obj-c.

    So for other platform : don’t care about Android : the only big market that make the “buzz” is AppStore.

    Even if Apple make a lot of damage with ToS, i am sure the majority of developpers will follow their devs in this way, even if they are not agree with terms.

    The fact is : the market of Mobile is clearly on the side of Iphone, this is not only a fashion device or tendance, but a really “good product” !!! Every body know this i think.

    The difference between Iphone OS and other Mobile OS is like the difference between Mac OS and Windows. (So don’t feed the Troll, my apologize ^^”” )

    In anycase, i’m waiting for a good (or bad…. :/ ) news from Titanium Staff, i hope it will be allright….

  52. 4 days ago I contacted Apple (I’m a paying developer).
    Here’s what I wrote to them:

    “I want to know if Titanium appcelerator platform is in accord with Apple iPhone 4.0 Terms of Service.

    I have spend a lot of time and effort on learning and developing on the Titanium platform and I hope to get a clear and straight answer.

    (Please note that I am using a Mac and the Titanium Appcelerator platform produces an XCode project file).”

    here’s what they wrote back to me:

    “Thank you for contacting Apple Developer Support regarding the iPhone Developer Program.

    For information regarding your enquiry, please refer to the Program License Agreement.

    You can view a copy of our program agreements by logging in to the Member Center:

    thank you for your clear, honest and supporting answer dear Apple.

  53. So what does this mean for those of us who have spent hours, days, months, learning titanium and developing our apps? Worst case scenario…

    Is it possible to get titanium to spit out the xcode source which you can then transfer to use with approved development tools?

    Also, does this mean we can develop apps using pre 4.0 sdk’s and not have them rejected?

  54. I developed a small app in 3 days last week while learning Titanium. Then this news came. I started learning Objective C the same day and still doing it. I then signed up for apple dev program where I had to agree to new agreement.

    I still went ahead and submitted my app that was developed in Titanium. And it got approved in 3 days. Waiting for it to appear in app store now. 🙂

    I started to like xcode, interface builder, IBOutlet and @synthesize and what not but still think Titanium is a great tool to help speed up in development.

    I hope this light at the end of the tunnel stays on 🙂

  55. So what is the process to determine whether Titanium apps will be accepted with Apple SDK 4? Do we have to wait til it’s released or are you folks asking for clarification from Apple now?

  56. […] Just where will the line be drawn? Common sense would say that development tools that generated Objective-C, but used XCode to compile the source would be safe. Then again, common sense would say that ostracizing a large portion of your developer pool would be bad business. 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. – Jeff Haynie, Update on Apple SDK and Tos […]

  57. dBeb, there is no process. Apple will not provide you with the informations you need, no matter how friend you ask or how long you beg. The only way to find out is to create a project with the platform you are unsure about and submit it. After a few weeks you’ll hear from Apple if they accept it or not. That’s not 100% safe since Apple didn’t follow their own rules in many cases but that’s as near as you can get.

    Apple- the company where developers are treated worse then trash.

  58. Hi, I develop a small application (Psicosis) with titanium and it got approved in 3 days.

    The sdk target of app is 3.1.
    Titanium is OK, pass the new ToS

    Waiting for it to appear in app store now.

Comments are closed.