Back in January 2011, I built a little website (http://www.airportgasfinder.com) 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.
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).
I cannot imagine ever using jQM for another project.
This is a really neat idea. I'm never sure how close to the airport I should be to refuel- too far out and it might not be "full" enough for return, but too close and you might miss the last gas station!
I got the idea after my girlfriend and I went to Maui for Christmas. I had never been there before, and had no idea where I should get gas on our way back to the airport. Like you said, too close and you might miss the last station. Plus, I was already concerned about missing our flight. The last thing I needed was the extra stress of watching for gas.
Zilch, skipped 'em. I'm not saying this is the right solution for every case, especially for situations where you want something more application-like, but this wasn't a high priority for me.
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).
I cannot imagine ever using jQM for another project.