HTML5 web apps talk, Ido Green

Get Started. It's Free
or sign up with your email address
HTML5 web apps talk, Ido Green by Mind Map: HTML5 web apps talk, Ido Green

1. ido-green.appspot.com

2. @greenido

3. Tips

3.1. Let users try without signing up

3.2. Device aware & responsive

3.2.1. formfactorjs.org

3.2.1.1. New Node

3.3. New Node

3.4. Be explicit on the browsers you support

3.5. Use history API for pushing state in single page apps

3.5.1. Levieoutes.com

3.5.2. Twitter mobile do it a lot

3.6. Use client side architecture from the start, for

3.6.1. Offline

3.6.1.1. LawnChair - simple json storage

3.6.1.2. Types

3.6.1.2.1. Local storage

3.6.1.2.2. Index DB

3.6.1.2.3. Fs API

3.6.2. Performance

3.6.2.1. manifest = cache.appcache

3.6.2.1.1. Enable offline scenario

3.6.2.1.2. Add comment with version number at top of manifest file

3.7. Make entering information easy & clear

3.7.1. Required

3.7.2. Placeholder

3.7.3. Pattern

3.7.4. Min max

3.7.5. Well supported in mobile

3.7.5.1. Check in caniuse.com

3.7.6. x-webkit-speech

3.7.6.1. Gives you confidence level

3.8. Keep your users informed

3.8.1. webkitNotifications

3.8.1.1. createNotification

3.9. Treat performance as feature

3.9.1. Caching

3.9.2. Css3 transitions

3.9.2.1. Used GPU

3.9.3. Use WebWorkers

3.9.3.1. More:

3.9.3.1.1. bit.ly/rizNVE

4. Cross browsers

4.1. Polyfills

4.1.1. Modernize

4.2. ChromeFrame

4.3. Chrome update

5. Aim for a great user experience

5.1. Most of the time, everything else will follow

6. Links

6.1. Html5rocks.com

6.2. plus.ly/greenido

7. Q&A

7.1. Cache size

7.1.1. If its Chrome App, you get 100mb not just 5

7.1.2. Usually you use index.db

7.1.3. If you need a lot, use File API

7.1.3.1. That's what Kindle app & Angry Birds use