Na#ve  vs  Hybrid

Stephen  Forte  @worksonmypc  

Mobile  &  Cloud  are  disrup#ng  so8ware  development.

Yesterday Today

X

UI is harder than ever.

Multiple skillsets Many platforms

Many SDKs Wildly different UX

Unpredictable screens More time consuming Indirect debugging Rapidly changing

Cloud is easier than ever. Lower costs | Reduce setup time | Easily scale | On-demand capabilities

Yesterday Today

<include>  SERVERS

INSTALLS

CUSTOM CODE

Reach of

Web Richness of

Native Efficiency of

Hybrid

$ $$$

Reach of

Web Richness of

Native Efficiency of

Hybrid Web Hybrid Native

What  About  My  Startup?

MVP Facebook Launch Web Hybrid Native

Rapid  MVP  are  great  for  Responsive  Web

If  you  launch  with  iOS  only,  you  are  ignoring  70%  of  the  market  

(or  more)!

Don’t  let  this  happen  to  you

Yes  I  am  talking  to  you  Snaptee!

But  Wait,  Mark  Zuckerberg  Said  HTML5  Sucks!

No  He  Didn’t

       "When  I'm  introspec#ve  about  the  last  few  years  I  think  the  biggest  mistake  that  we  made,  as  a  company,  is  be[ng  too  much  on  HTML5  as  opposed  to  na#ve...  because  it  just  wasn't  there.  And  it's  not  that  HTML5  is  bad.  I'm  actually,  on  long-­‐term,  really  excited  about  it.  One  of  the  things  that's  interes#ng  is  we  actually  have  more  people  on  a  daily  basis  using  mobile  Web  Facebook  than  we  have  using  our  iOS  or  Android  apps  combined.  So  mobile  Web  is  a  big  thing  for  us."

       

                               -­‐-­‐Mark  Zuckerberg,  Disrupt  SF,  September  2012.

Facebook  moved  to  Na#ve  from  HTML5  when  they  had  

$1b  in  profit.  

When  you  have  $1b  in  profit,  you  can  go  na#ve.  J

The  End