Decisions, Decisions: Native to Mobile Web
Upcoming SlideShare
Loading in...5
×
 

Decisions, Decisions: Native to Mobile Web

on

  • 376 views

 

Statistics

Views

Total Views
376
Views on SlideShare
376
Embed Views
0

Actions

Likes
2
Downloads
5
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Decisions, Decisions: Native to Mobile Web Decisions, Decisions: Native to Mobile Web Presentation Transcript

  • Decisions, Decisi ons Native, Hybrid & Mobile Web Will Iverson CTO, Dev9
  • • Dynacron Group is now Dev9
  • • Dev9 – – – – Kirkland, WA software consulting firm ~40 people, ~3.5 years Specializing in Continuous Delivery Open source, Java, Mobile, NoSQL • Will Iverson – CTO. Author. Speaker. Since 1995.
  • • Mobile is huge. • Mobile is multi-platform. • Secure things are [validated] on servers. – Money, digital goods, identity, etc. • You don’t have infinite resources.
  • Wait…
  • http://developer.android.com/about/dashboards/index.html
  • http://aplus.rs/2013/try-couch-to-5k-ios-and-device-charts/ Note: this particular chart is a smaller sample for one app
  • What exactly IS mobile, anyways? Touch? Small screen? Location aware?
  • • • • • Goals People (aka resources) Tools Processes
  • • Concrete model for describing success – Transactions? – Sales? – Reduce time to complete action? – Ongoing user engagement?
  • • Give 30% to platform vendor? – Give up 50% to retail today, maybe ok – Give up 3% to CC today, maybe not • Do you have the customer’s contact info?
  • • Let’s go build something! • Need a dev team… tools… processes…
  • Native • Use mobile platform vendor SDK & Language • Full device integration • Excellent CPU/GPU performance • Hard to build Mobile Web • Use HTML5, JavaScript to target mobile browser • No device integration • Slow, inferior CPU/GPU experience • Easy to build
  • Web Application Mobile Browser Native Application Web Application Native Wrapper Native App Store * iOS+
  • • Native • Web – Responsive – Canvas • Hybrid – Responsive – Canvas
  • scirra.com/arcade
  • • Subjective vs. Objective – 10,000s of sprites, physics, more… many high perf demos • Requires work – Touch events, JS profiling • Naïve implementations easy to screw up – Use mobile appropriate JS frameworks • Perf improvements help all targets
  • • Biggest challenge • Roll your own, or use a toolkit KendoUI framework shown
  • • Performance? • GPU! • Hardware integration? – Innovation! • App Store! – Discoverability!
  • • Testability – Much easier to test mobile web • Continuous Integration • Deployment Time – Days/weeks for app store updates • Analytics • Budget • Staff Expertise
  • 3D Game? No Yes Unity3D 2D Game? No Yes Scirra Construct2 Internal Customers Only? Yes Mobile Web Only No Mobile Web + Hybrid
  • Q&A