Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I tried to use JQM with backbone.js. Problem arose that JQM couldn't handle query params (like http://site.com/page?key=value), so I couldn't build dynamic pages that are bookmarkable. JQM devs were aware of the issue but said that dynamic pages were out of scope for JQM.

I dropped JQM and went with zepto, backbone.js and custom CSS. And wow, the performance gain was eye opening.

I think JQM is a nice tool to build prototypes and to learn about building single page apps. But no way would I consider using JQM for a production app.



What did you use for all the UI and widgets that JQUI gives you? Did you find that a tough gap to fill in when you dropped JQUI?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: