Note: I wrote this nearly a year ago, not sure why it's popped up today. Since then, both Bootstrap and jQuery Mobile have improved. I encourage you to consider both options (amongst a host of others, some of which I overviewed in this talk - <a href="http://mobile-app-strategy.appspot.com/" rel="nofollow">http://mobile-app-strategy.appspot.com/</a>) and pick what works best for you.
:-)
Back in January 2011, I built a little website (<a href="http://www.airportgasfinder.com" rel="nofollow">http://www.airportgasfinder.com</a>) to help people find gas stations near airports, so they wouldn't have to worry about refueling rental cars on the way back to the airport. I built it on Rails 3.0, with jQuery Mobile for the mobile interface.<p>I let the site go dormant for a while, but resurrected it recently. When I rebuilt it, I used Bootstrap for the UI and decided to rip out jQM in favor of Bootstrap's responsive features. It took me a lot less time to build the new mobile UI, it feels faster and less clunky, and it has reduced my workload going forward, since I no longer have to maintain parallel sets of views (e.g. index.html.haml and index.mobile.haml).<p>I cannot imagine ever using jQM for another project.
Is this really front page because it has 2 buzz words in it? The article is non-substantive and attempts to compare a mobile app framework with a css toolkit.
This seems like a superficial dive. JQM has a ton of things Bootstrap doesn't, like separate pages based around div tags, hierarchical navigation and app-like transitions between those pages.<p>Not disagreeing with most of the points raised, but I don't think its the full story.
We're contemplating this as well but I'm worried about how many little gotchas we'll have to rebuild from scratch to get similar support on many different mobile browsers.
This might work well for a single page site, but one of jqm's features is to out every page into divs and have the JavaScript deal with the page transitions. I'm wondering how that would be replicated using bootstrap. I love bootstrap and it only takes a few minutes to make it look distinctive from other tb apps. I also love how jqm does much of the tedious work in building mobile friendly apps.
You can always use Bootstrap for scaffolding (the grid is the coolest thing), and use jQM for interface elements and rest of the stuff. They are two different tools with different goals, just that several bits (or "features") of them overlap.