Note: If this tutorial was helpful, need further clarification, something is not working or do you have a request for another Ionic post? Furthermore, if you don't like something about this blog, if something is bugging you, don't like how I'm doing stuff here, again leave me a comment below. I'm here to help you, I expect the same from you. Feel free to comment below, subscribe to my blog, mail me to firstname.lastname@example.org, or follow and mention me on twitter (@gajotres). Thanks and have a nice day!
Sencha Touch vs jQuery Mobile
Match 1 – Marketing and platform support
- Usable only one web kit browsers (this is no longer the case)
- There are much more available mobile frameworks then Sencha Touch developers would want you to know
- Large number of available platforms, though not optimized for specific platforms (allegedly should be better optimized from version 1.4
Match 2 – UI and visual impression
- Extremely fast and fluid on mobile devices, all in all, much better feel than jQuery Mobile
- Currently it offers more UI elements/widgets, for example carousel implementation
- SVG support – making it great for games
- This is not directly related to UI, but Sencha Touch IDE is premium product
- Unlike Sencha Touch, jQuery Mobile UI works much like classic web UI
- Everything is done through HTML where final UI is wrapped with a custom jQuery Mobile styles, just like jQuery UI
- UI is easily extendable and morphable, with a little bit of CSS you can change any existing widget, even create new ones. From version 1.4, UI should be extendable to jQuery UI.
- Ajax driven navigation can be confusing to some developers + page transitions, and animations don’t feel ‘native’ enough and can be sluggish sometimes
- CSS usage that makes it great also makes it looking like a clone, one application looks just like another, it requires a lot of time to make it look unique. Excellent example is mobile version of SongMeanings.com.
- Unlike Sencha Touch here you need to worry about page architecture, it can be problematic sometimes. Everything is tied together, which is good and bad at the same time. Version 1.4 should remedy a lot of this concerns.
Match 3 – Availability, ease of use
- Very hard to impossible to debug and fix errors in the framework
- Steep learning curve – at the same time worth of every hour spent on it
- If you like jQuery (like a lot of people do) you will also like jQuery Mobile
- Easy syntax
- Unfortunately out of box MVC is not supported, it can be fixed with Backbone.js or Knockout.js
- Great theme roller support + everything can be easily manipulated through CSS
- Basically any IDE can be used to develop jQuery Mobile application.
Match 4 – Documentation
- Simply better official documentation the jQuery Mobile, large and not confusing, unless its syntax is not confusing all along to you
- Not that much 3rd party support or forums
- Official support is not free, not to mention official IDE platform
- Good official documentation but not on a level of Sencha Touch
- Excellent 3rd party support, blogs, articles, forums, Stackoverflow….
- Better book coverage
Match 5 – Tools, Plugins, 3rd party support
- In house native app wrapper support
- Support for themes
- Unfortunately IDE is a paid application
- Phonegap is used as a native app wrapper, also while PhoneGap is an excellent tool it can behave weirdly when used with jQuery Mobile
- Support for themes, unfortunately, this is not a full support because some core elements CSS can not be changed like this, for example, active element glow
- Large number of 3rd party plugins is available, not to mention compatibility with jQuery plugins
- Can be extended much more easily than Sencha touch