4 ms·
Trying the demos on both a Galaxy S and an iPad, I'm struck by how slow everything feels. Buttons don't react when you press them, but a second later, which isn
by necubi 16y ago
Trying the demos on both a Galaxy S and an iPad, I'm struck by how slow everything feels. Buttons don't react when you press them, but a second later, which isn't acceptable when you're competing with native applications. However, it looks good and they have time to fix the speed issues. I might look into using this instead of something heavier, like sproutcore.
- jasonkester 16y agoTheir demo seems to be loading content from the internet when you click a "stuff >" button. That's a terrible metaphor to use, since the expectation when hitting a button like that is instant feedback. Had they left links looking like links, you would expect a delay while loading and therefore not be disappointed. To make it worse, putting the "loading" dialog up actually makes the operation seem slower. If I was building a site using this library, that's the first thing I'd figure out how to disable.
- harisenbon 16y agolooking at the api, you can also do a number of "pages" within a single html page, and just have it cycle through those when you click links (much like jqtouch worked). While it is kind of slow to load each page with ajax, I do like that they have made that easy to implement, as it was rather difficult to do with jqtouch.
- RedWolves 16y agoWe considered the Alpha 1 release feature complete. The goal now is to work on optimization of the code to make things run more smoothly. Alpha 2 fixed a number of bugs and made a number of improvements. Still much to do. Thanks for your feedback.