Is Titanium a mistake? and is it equally compatible for developing iOS applications like Xcode and Objective-c?

A few days ago, I was almost sure that Titanium is a great development environment for iOS applications, but over the last few days I have looked at several articles about Titanium, and some of these articles have indicated that Titanium is not fully recognized as an iOS development and it is also buggy.

And I came to my StackOverflow friends to find out if this is true? someone really ran into any problem or encountered some kind of error while developing an iOS application using Titanium.

Please advise if I should use it or should I go for Objective-C?

Thanks.

+4
source share
3 answers

I believe that titanium is probably more buggy than Cocoa's native sensor libraries, and by definition is not fully recognized as a native Objective-C development.

The main question before choosing a development method: will you in the future consider porting an iOS application to Android? If the answer is yes! and you don’t know Java, but you are more familiar with web technologies such as CSS, Javascript and HTML / HTML5, not C / C ++ / Objective-C, I believe that Titanium should be the natural choice.

On the other hand, if you quickly learn new languages ​​and have good experience with C / C ++, the method is Objective-C - later you can probably quickly learn Java and switch to the Android platform.

The second criterion is: Is Titanium able to provide the UI / UX that you would like to have in your applications? Successful Titanium Stories Help You Answer This Question - Titanium: A Showcase of Applications . Also try many of your own apps to check what they offer. Compare and make decisions.

Important: I have never tried Titanium. I just face a similar dilemma like you. I want to expand my mobile application skills in the Android world and consider Titanium as one of the ways (I know basic JavaScript / CSS / HTML5, but not Java).

EDIT: I just checked your profile and it seems like you came from the Android world. I would add to my answer: if learning Java was easy for you, and you are already familiar with the ups and downs of Java development for Android, learning Objective-C should be easy. The main difference is that in iOS you have to manage the memory yourself, and that can be a little painful.

Some good things:
1. Memory Management Programming Guide
2. Training Objective-C: Primer
3. Objective-C programming language

+5
source

Titanium mainly uses JavaScript to develop applications in iOS and Android. If you're comfortable using JavaScript and CSS, you can try Titanium.

His personal opinion, try learning Objective-C, his really great language. If you have knowledge of C or C ++, understanding the concepts of Objective-C becomes easier.

Try Objective-C, you won’t be disappointed.

+2
source

I have been using Titanium (and playing with it for several months), and I can justifiably say that these are buggies, like hell. :-) If you are looking for a single-platform solution, that is, only Android or iOS, and plan to only support this single platform, you do not need to avoid TiStudio.

What Titan is trying to do is disengage and simplify the basic nature of the platform you are on. This does not make it fabulous, but for simple applications I have had great success.

However, since attention is concentrated between the three (with Blackberry support), it will always lag behind its own dev systems and will always have a lack of advanced features. This is a compromise.

All that TiStudio said is better than the light years of TiDeveloper (Appcelerator bought Aptana and is now in the process of integrating Titanium development with the Aptana IDE), and they really work hard to make the platform top-notch.

I landed on it as a platform because of my extreme hatred of Java (two months later, trying to reinstall Java using my own IDE path) and my desire to do cross-platform development. I am also sure that I can route Titanium errors / shortcomings, as I basically write my own application development infrastructure on top of the Titanium SDK, so I can automate what suck, correct erroneous behavior, etc. This is a lot of work.

But mostly where mobile development is now. You choose your poison. Stick with a native SDK and be locked on the same platform and deal with an annoying language (both Java and Objective-C are ancient by modern Python / Ruby / standards independently), or try something like Titanium, which offers simplicity and more flexibility language, but it is less closely integrated with a larger error.

Good luck

+2
source

All Articles