Drawbacks of using Appcelerator Titanium (or equivalent)?

Our company has a huge impetus for the development of cross-platform (iOS and Android). Appcelerator Titanium is being considered (and, it seems, the only thing being considered) to achieve cross-platform development without additional development time.

Everyone can think about the reasons for using Titanium. For reasons related to using Titanium, I assume that the performance of the resulting native application from Titanium may not be as good as the application written in Objective-C for iOS. How significant is the difference? Are there other reasons not to use titanium (or equivalent)?

Note: I can write Titanium, but the reasons may not only be titans. All arguments in support of coding in the platform language (for example, Objective-C, Java) are qualified.

+5
source share
4 answers

Good:

  • Can create iPhone apps using very simple Javascript.

Poorly:

  • Apple rejected some Titanium applications due to private API calls, but Appcelerator did not respond to requests for help and did not update their SDK. http://developer.appcelerator.com/question/123785/app-has-bee-rejected-by-non-public-api

  • " " , : ; . .

  • API . ( ).

  • , .
    .

  • Github wiki.

  • Appcelerator : : titanium_mobile github open pull .

  • .

  • .

  • Q & A. .

  • Showstoppers " ":

  • iPhone 4

  • iOS Android,
    / . (/) , Android iphone.

  • ,
    . "" - .

  • " " .

  • Appcelerator .

  • : 30%
    , .
    . .

  • [Seen 8/13/2011] , Q & A: : , . (.. 51-100), , 1- - 6- .

:

[ Q & : , Appcelerator - .]

:

, API . , , XCode Objective-C.

+17

?

AFAIK, Titanium Objective C, , , , .

( )?

, , "".

, - , , PhoneGap. : .

PhoneGap HTML, CSS JavaScript, - HTML5. , PhoneGap, - (, APK Android) API- . , "" , HTML5 . , .: -)

, , - , -, . , , (, Sencha Touch, jQuery Mobile). , - - HTML5, PhoneGap, .

Titanium JavaScript, . API , . - HTML5 , , PhoneGap. - , , HTML5, , Titanium.

PhoneGap, Titanium, (, Rhodes, Flash/AIR) . - , PhoneGap , Flash/AIR , Adobe, .

: , HTML-. ( " ", , ). .

+5

/iOS, 2c.

Native iOS vs Titanium

  • , .
  • , , .
  • javascript, , dom.
  • javascript , , .
  • Coffeescript , js
  • , objc , .
  • , Titanium.
  • .
  • , 5 , .
  • js view , . : (: , app.js)

CONS

  • - . Titanium, .
  • , .
  • Titanium Developer Mac , .
  • .
  • - .
  • , , , , .
  • JSON, . eval .
  • , objc .
+4

Xcode, Visual Studio MonoDevelop, Titanium Studio ( ), ( , ), , , JavaScript... , , iPhone Android, -

We are long and hard at the best option for a cross-platform developer and ultimately using Mono - Touch and Droid. It was great that we really use 80% of the code between the iPhone and Android, and we are just starting the WP port, which is going well (again, the share of 80% of the code). Of course, this is not a miracle to fix - you still need to know how to develop for each platform. I even loved C # much more like Obj-C :-)

Obviously, some will not agree.

0
source

All Articles