The only way to get websockets to work in a mobile web application with sencha touch is with firefox. Firefox 4 mobile is the best mobile browser for the android. Sencha should support and android should make it the default browser for all android devices, unless google wants to create a mobile chrome.
Seriously doubt Firefox will be the default browser on Android.
Gecko support would be a good as long as it is a completely separate build of Sencha Touch. As others have pointed out solely targeting webkit gives a lot of benefits and keeps the library as lightweight as possible. While Gecko is good, it is still some way behind Webkit and I don't see that changing anytime soon.
As for IE support: don't even bother, if you need it you should consider writing an ExtJS version of your application.
As for those who would say "you should implement your desktop application in a more appropriate framework, like ExtJS, just to get Firefox support": well if you have the resources to write your application twice - good for you =)
The future will show 3 leading mobile platforms: iOS, Android, Windows Phone. Having a toolkit based on Webkit only browsers will prevent Windows Phone from working as their browser will be IE based.
The future will show 3 leading mobile platforms: iOS, Android, Windows Phone. Having a toolkit based on Webkit only browsers will prevent Windows Phone from working as their browser will be IE based.
Sencha Touch 2 at the 2.0 release will still only support WebKit browsers as we wanted to focus more on performance with iOS, Android, and BB but after 2.0 we will look into supporting other platforms.
Originally Posted by keithoth
Mitchell Simoens @SenchaMitch
Reply With Quote