More Related Content Similar to August Chicago Mobile Meetup talk 8-25-11 Similar to August Chicago Mobile Meetup talk 8-25-11 (20) August Chicago Mobile Meetup talk 8-25-117. My dad would like an easy offline way to figure out which low-sodium drinks he can have because he still likes frappes and cappuccinos 12. If I wanted to build a mobile app to sell, I would probably take the traditional route of native. 17. Now “The plaid fox...” is set like a cookie, but I don't need that, I need an offline database in the browser. 18. Your phone can hold strings...but relational information (pepsi-can-40mg) is what I want in client-side webpage storage. 21. Can also be nested, but for now the database table has 4 columns: id, drink, size, and caffeine which we can add to, extract from, and search. It is permanently stored in the browser until the user physically clears their localstorage cache. 26. “The drink you selected has “ + getdrink["caffeine"] + “mg of caffeine!” 37. Possibly unorthodox at this time (if jqmobile runs all the links, operations such as a back button, form submitting and javascript validation, using the # in links, and css changing take some playing around with) 44. It will compile multi-page websites into an app, but single page (inner linked divs) yield quicker performance 49. Blackberry = whole new ballgame – you should really study this platform before you build for it 50. Still need to configure your Androidmanifest.xml file for permissions – ie, add internet access perm before adding a link 61. Titanium = a javascript app compiler in its own software package. Not intuitive on how to fix bugs or general “how do I do it” 62. Zepto.js = “jquery for only mobile safari and chrome”. Lite, but with transition effects. 63. Webdb / SQLite = I was initially put off by the “browser wars” lack of support. This is a good second option for right now in phone storage. 70. What's good for making money with in-store apps doesn't work with “quick fix tools” such as web app technologies 71. You can do a lot of native things with web app compilers like PhoneGap, but you still need native intelligence to implement those in. 73. By pushing 3 buttons (brand, flavor, size) it keeps track of what and when you drink in a day when you close the app/browser. 74. It tells you when you are close to your limit, and what drinks will be too much caffeine for you at this time. 78. Included brands: Coke, Vitamin Water, Pepsi, Sobe, RC, Snapple, Arizona, Panera, Tim Hortons, Dunkin Donuts, Caribou, Starbucks, Seattle's Best, Jarritos (Mex), Guarana Antartica (Brz), Wahaha (Chn), Dannon Yogurt, Haagan-Dazs, Hershey's, Anacin, Excedrin, Vivarin, Monster, Red Bull, Jones Soda, Yerba Mate, and many other energy/specialty drinks. 81. Big thank you to Gregg and Kelly from the Chicago Mobile meetup for this chance!!!