Intro

Forward

Who am I?

Luke Daffron
Lead Developer at Foliotek, Inc.
luke@foliotek.com
@thinginab
Wiffle app: http://wiffletracker.appspot.com

Why JQMobile?

Familiar technologies
Rapid development
Great touch UIs, transitions, etc.
Write once, run (almost) anywhere - phones, tablets, desktop
Accessibility and graceful degradation

Why Not?

Not quite native
Comparatively large footprint
At the mercy of the browser and os stack
Some hacking required for best experience

Common Elements

Back Forward

Pages, Dialogs, and History

"Pages" can be in a single file or multiple files - JQM uses ajax to fetch external pages on first load (can do a pre-fetch too)
Dialogs are just pages with a data-rel
JQMobile uses hashtags for state/history
See docs on dynamic page generation

Toolbars

Headers can automatically insert back button
Footers can be floating or fixed, even persistant
Also, Header or Footer tab strip Nav Bars

Lists, collapsibles, and grids

Lots of list options - headings, search, counts, icons, nested, etc
Collapsibles are nice - these pages!
Horizontal grids, 2 to 5 columns
JSFiddle

Form elements and buttons

Custom native-like sliders, toggles, dropdowns, etc.
Inline, Icon, and Group Buttons
JSFiddle

Theming

Several built in swatches, can mix and match with data-theme
Can add new or change swatches with ThemeRoller
Get inspiration from the Gallery