1. About
1.1. Ido Green
1.1.1. Chrome developers advocate with Google
1.1.2. @greenido
1.1.3. +Ido Green
1.2. talk hashtag
1.2.1. #html5tlv
2. Intelligent API
2.1. animation
2.1.1. window.requestAnimationFrame
2.1.2. browser understands that it's only required when the tab is visible
2.1.2.1. there's also a visibility API
2.2. prerendering
2.2.1. prerender pages
2.2.2. limitations
2.2.2.1. browser not committing to succeed
2.2.2.1.1. there's a cap on the resources
2.2.2.1.2. so, do it when very likely the user will go there
2.3. online/offline events
2.3.1. add listener
2.3.1.1. online
2.3.1.1.1. know that you can cache things
2.3.1.2. offline
2.3.1.2.1. know that you need to use cache
2.4. Web Intents
2.4.1. motivation
2.4.1.1. there are many API's for everything
2.4.1.2. provide thin layer for
2.4.1.2.1. service providers describe their API
2.4.1.2.2. developers that can offer users to choose a provider
2.4.2. how
2.4.2.1. service registers itself
2.4.2.2. App requests to start an action
2.4.2.3. User selects which service to handle the action
2.4.2.4. 2 way communication between client & service provider
2.4.3. similar intents system exists in Android
3. Rich multimedia
3.1. Camera & Mic access
3.1.1. video elements allows recording
3.1.2. you can do things with the recorded data
3.2. Fullscreen content
3.3. Web RTC
3.3.1. browser engine support, without plugins
3.3.2. API
3.3.2.1. break the "dial" paradign
3.3.2.2. full-duplex
3.3.2.3. for
3.3.2.3.1. gaming
3.3.2.3.2. collaboration
3.3.2.3.3. Khan Academy
3.3.2.3.4. robots
3.3.3. webrtc.org
3.4. Web Audio API
3.4.1. low-level audio manipulation
3.4.1.1. also in real-time
4. References
4.1. http://chromestats.com
4.2. html5rocks
4.3. Chrome Frame
4.3.1. get chrome inside IE, without administrator-rights install
4.3.2. just add meta header