Titan vs. Sencha - Learning Curve?

Sencha has a steep learning curve, but how does this compare with titanium? is titanium easier to learn?

+4
source share
2 answers

I worked with Sencha Touch 1 (some ST2) and now I am processing my application in Titanium.

  • Sencha Touch simplifies the development time of cross-platform interfaces that look consistent across devices. Titanium offers you to target your platform using common differences in interfaces between iOS and Android platforms.

  • ST has a mature MVC framework to help you develop your application. If you like MVC, Titanium really doesn't work at the level that ST does or at all. They are working on it. On the other hand, having learned a little more about the structure of Ti, I still like it.

  • From what I can understand, Titanium maps your interface elements to its own interface elements on the target platform. With ST, I had performance issues with my interface on some Android platforms. In particular, there were problems with the Android 3.0 platform that I remember. This was the main reason for my transition to another platform.

  • For my needs, both platforms had a way to store data. ST helps you with this, which allows you to automatically download data if you configured them correctly, which was very nice. In titanium, data loading is more controlled by you. Sencha uses a "store" system that can work quite well. Using this takes a little time to figure out if you come from the database world. Titanium allows you to access SQLite, so if you are in the world of databases, you can quickly get to it pretty quickly.

  • Titanium provides you with a way to create your own modules for each target platform. I don’t think Sencha Touch has a method for this. Therefore, if there is something that Titanium has not implemented, you can write it yourself to get some kind of native platform function. I do not think you have this option with Sencha.

I feel like I get a more fascinating look with Titanium over Sencha Touch. There is definitely more work on your part to implement this, so there is a trade-off. I miss the MVC structure that Sencha has because it makes sense to me. There are several ways to use MVC in Titanium, but trying to understand a few attempts to create a community, I abandoned this. The titanium structure makes sense as soon as you give up trying to fit it into the Sencha MVC structure, as I originally tried. The odd OS problems related to Sencha Touch forced me to eventually abandon use. Pages with multiple fields scrolling around will tremble even in sample applications. I know that it was a “platform performance issue” on the Google side with Android, but in the end it turned me into Titanium. I cannot yet confirm the performance of Titanium, because I have not fully tested it for my needs.

+12
source

In both cases, you work in Javascript to write your representations, not HTML. Thus, both require some overclocking time to become familiar with a specific API and workflow.

However, I found that titanium architecture is better suited for rapid development. Sencha Touch seems to have a lot more overhead when it comes to building a basic application. In general, I think that titanium is easier to learn.

This is a rather subjective question, maybe not the most suitable for StackOverflow, but there you go.

+1
source

All Articles