Who am I?
Michael Henretty
HTML5 and Mobile
The problem with Native "Apps"
Apps are hard to develop
- Choose: Android or iOS first
- Hire platform specific engineers
- How long to port?
- Forget about "rapid" prototyping
Apps are hard to publish
- Review process takes days
...weeks
...sometimes months
- Revenue cut, around 30%
- All payments must go through market
Apps create friction
- So many steps
- search
- ...install
- ...login
- ...download
- ...launch
- Cannot try out, must install
- Can't search by content
HTML5 is better, development
- Develop for all platforms simultaneously
- Only need 1 team
- Easy hiring:
10+ million web developers!
- Great tools
chrome & firefox
- Easy rapid prototyping
HTML5 is better, publishing
- Publish whenever you want
You and your users are your only reviewer
- Select your own payment method
- Re-use infrastructure
same as your web site
HTML5 is better, frictionless
- No installation required
1 click
- No waiting
- No need to pay up front
- Easy sharing
just send a link
- Search engines index your content
Side by Side, iOS vs HTML5
iOS
- Sign up for a developer account ($)
- Buy a Mac ($$)
- Set up XCode
- Configure project/team settings
- Request development certificate
- Register Devices
- Develop your app
- Upload to iTunes
- Submit for approval
- wait...
Side by Side, iOS vs HTML5, cont
HTML5
- Develop
- Deploy
- Done
Side by Side, Android vs HTML5
Android
- Install Eclipse
- Install Android Toolkit
- Install Android SDK
- Configure ADT with SDK
- Configure project
- Open debug perspective
- Set breakpoints
- Run application in debug mode
- Select target device
- Hit breakpoint
Side by Side, Android vs HTML5
HTML5
- Open you webpage
- Open Developer Tools
- Set breakpoints
- Hit breakpoints
Why go native?
- Performance
- No hosting required
- Easy payments
- Consumer Trust
Firefox Marketplace
- Bridges gap between html5 and native
- Content Discoverability
- ...or make your own
Questions?