I've been working with JQM in a corporate and small business settings since it was in alpha 2 and these are some of the lessons I've learned. If you take these 21 tips to heart, hopefully I can save you some of the same headaches.  Much of this is true about going mobile for anyone. jQuery Mobile was simply my chosen platform. 

Ever wonder what the people who make the web use?

I am so proud to say that only 7% of my readership is using Internet Explorer. I'll even give them the benefit of the doubt that they are viewing my site at their job where they can't get away from it.

Want to create dynamically pages on the fly? Want to use jsRender? Want to do it without overwhelming the browser? Here's how....

You want to use APIs? Want to create dynamically pages on the fly? Want to do it without overwhelming the browser? Here's how....

Note: Here is this same example done with jsRender. jsRender is now the stated direction for templating by the jQuery team. Thanks to @ziodave for pointing this out. Despite that, I am leaving this original post intact because it may still be useful to somebody.

Navigation is the hardest thing to get right in any application. Mobile only compounds the issue. jQuery Mobile doesn't (and shouldn't) have a pre-built global navigation structure. This leaves room for flexibly and creativity on the part of the designers, but also leaves some scratching their heads and wondering what to do. So, here are what I believe to be the three best ways to create global menus and the reasons why you might choose each.