A frequent suggestion in blog comments relating to Nokia is to go with Android/WP7 and when it was available, to go buy Palm for WebOS. Why? Nokia has in house, Symbian and Maemo, the latter of which has become MeeGo – though the phone side has no presence on the market since there are no purpose built MeeGo phones.
Well in this transition stage where Symbian is waiting for the major UI change and MeeGo is still waiting to escape the birth canal, frustration rests upon some users and onlookers of Symbian^3 (the only real Nokia smartphone choice atm) as not having the same glitsy glamour and UI appeal of its competition. Nokia is always praised for the hardware, though last year with N900 got rapturous awe for its powerful and potential filled software – but that’s now canned for MeeGo.
Therefore, is it rightly so that Nokia should look to others as a temporary measure? Or is this not suitable for Nokia’s long term success? Does a successful phone manufacturer need it’s own operating system to survive? There’s a lot resting on the events that unfold for Nokia in 2011.
In an ideal world where anything could happen – If Nokia Smartphones could have any but only one Operating System, what would you like it to be? Read more…
In iOS (e.g. iPhone) when you long press the icons, they start shaking about meaning you can move them. You can then drag and drop icons into place and the other icons shuffle around.
You’ve always been able to move icons with Symbian, but needing to go Options>Organize.
“Written in Qt Quick. The entire project is just 70 lines of code!
Runs on Symbian, Maemo, Meego, Windows, Linux, Mac and other Qt Quick supported platforms.
Full source code available on the DevNet wiki: http://developer.qt.nokia.com/wiki/Dr…”
If I understand this correctly, Sencha Touch was built as a mobile framework for building rich applications for HTML5 enabled devices. i.e. WEBAPPS.
Reading their blog, their approach is very intereting. Also moving from button focused (which can clutter your screen) to intelligent gesture focused – with importance on animations to indicate to the user that information is being fetched that’s not currently available on screen (instead of dull blank loads that make you think the app has hung).
The video demo below is called KitchenSink – possibly because their demo has in terms of touch-events everything but the kitchen sink. You’ll note that it’s very iOS/iPhone like.
- Gestures (Carousel Swiping)
This isn’t everything their demo can do but just what the short video shows.
About Sencha Touch