This document discusses key factors for a successful mobile application. It emphasizes the importance of preparing well by ensuring quality input data from various sources and providing web services and open APIs. The document also stresses being user-centric rather than ego-centric, not discouraging users with long waits or clicks, and renewing users' interest through relevant notifications and content. Finally, it addresses the right choice of technologies between native, web, and hybrid approaches and the need to keep the application alive through updates, downloads, referencing, and analytics.

1. KEY FACTORS FOR A SUCCESSFUL MOBILE APPLICATION Yvan Gravier www.neosesame.com Twitter, Facebook, Youtube: neosesame

3. rewards obtained during video games after successfully challenged the difficulties,

4. a product that sells well, i.e. music - hit, publishing - bestseller, etc. ...

5. evolutionary success of certain living species as a result of natural selection.Simply put for your App: Set your Goals, Define KPIs, Measure the Gap, FeedBack

6. #1 PREPARE WELL DATAUSER PATHERGONOMICS

8. Images

9. Web services

10. FTP servers

11. Excel files

12. Rssfeeds

13. XML

14. Podcast

15. VoD

16. Live videostreamThe W3C recommends: JSON + base 64 images encoding http://www.w3.org/standards/webofdevices/

17. Do it like... Tweeter, Facebook, Google, Foursquare, Skype, Orange, Bart…and more Repeat after me: “ Build web services and open your APIs! ”

18. BE USER CENTRIC… © Credit Decode Consulting NOT EGO CENTRIC…

19. DO NOT DISCOURAGE THE USER © Credit Decode Consulting AMAZON.fr ZAPPOS

21. Save favorites

23. Fresh content

24. Management of ranking preferences

26. BE CAREFUL WITH ERGONOMICS MINIMIZE THE CLICKS & THE LEVELS

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

31. DOWNLOADING - REFERENCING

32. Statistics: Measure your success

33. Thank you for your attention!Want to know more? Yvan Gravier contact@neosesame.com www.neosesame.com : neosesame