27. #2 RIGHT CHOICES OF TECHNOLOGIES NATIVEWEB WEBVIEW IN APPSFRAMEWORKS
28. 3 Possibilities Webviews in Apps Browsing Apps Highly platform dependent Natural for iPhone Dedicated to games and specific UI needs Better CTR so far, Better user adoption, Higher data volume Longer usage per cession Higher Hardware integration Lower development cost Requires a rendering platform Much quicker deployment Easier inhouse deployment Better control of distribution Higher billing control Lowest portability costs Easier Adservers compatibility Easier audience analytics Easier CRM Using the browser APIs and high portability, Controlled by a light embedded native code dedicated to each platform, Packaged in a widget or App or Webapps depending on priority, The rendering is made locally (page structure as well), Data are provided by server APIs (XML, JSON..) built once for all, SEE Google video: Android App embeds Webview by Google
29. Unified vision 70 to 80 % Smartphone coverage Brings all Web Apps advantages, Lower Maintenance costs Easier and quicker reuse and sharing, Higher CRM feed-back Fed by one single “fits for all” APIs build by IT Group A common Core Web view HTML 5, CSS, Javascript based 20 to 30 % specific per device Brings all Apps advantages: publication, download, visibility, CTR rates.. Brings persistency, Brings background Webpages Downloading Suitable with OEM Guidelines Controlled and built by a dedicated Light resident code App, Widgets, launcher..
30. # 3 KEEP YOUR APPLICATION ALIVE DownloadsReferencingStatisticsUpdates