Aop march 2012 presentation


Published on

Second screen strategies: a supplier perspective

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • And that’s the choice we face if we opt for Native app development – a version for iOS, another for Android and, in time, a version for Windows
  • Native apps are programs written for a specific platform . The big advantage of that is that is they can fully use the capabilities of that device incorporating the camara or the compass or the GPS facilties. And thanks to Apple and it Appstore – which begat Android’s marketplace and Blackberry’s app world there is a ready made shop-window for your product and a mechanism to get it out thereBut of course the downside to all this is that they a platform specific – you’ve got to write a new one for each platform. And they are created in expensive development environments like Objective C or Java which is great if you happen to have a lot of object oriented programmers hanging about.And while there are obvious advantages to the app store model it also places some restrictions on how frequently you can update the software
  • Aop march 2012 presentation

    1. 1. Second screen strategies:a supplier perspectivePresented by Ian Eckert
    2. 2. – UK B2B market leader
    3. 3. Second screen’ssecond coming
    4. 4. Second screen goes mobile
    5. 5. A brief history of – How the iPad changed everything
    6. 6. Apple vs Android vs Windows 8
    7. 7. Tablet vs – PC data: IDC. Tablet data: Gartner. Tablet data for 2013 and 2014 inferred from supplied figures
    8. 8. Tablets mean businessForbes Magazine: Erply Launches iPad Card Reader
    9. 9. OS – Gartner Figures for 2013 and 2014 inferred from supplied 2012 and 2015 figures
    10. 10. Development choices
    11. 11. Routes to market
    12. 12. Native PROS • Can use device hardware (eg GPS, camera etc) • Easy platforms for delivery (eg Apple App Store) CONS • Platform specific • Specialised and expensive development time • Restricted version releases
    13. 13. HTML5 PROS • Cheaper and easier to develop • Constantly updated content • Can be cached offline • Cross-platform and cross-device CONS • Functionality and speed can be slower • Can’ t access native functions • Has to be run in the browser so some cross-compatibility issues • Bookmarked and forgotten
    14. 14. PROS• Can split functionality between native app and HTML5• Cheaper and quicker to develop• Cross platform codebase / architecture• Can be marketed via app storesCONS• Reliant on HTML5 design capabilities
    15. 15. Hybrid driven appsNetflix, FB
    16. 16. Desktop publishing driven apps
    17. 17. PROS• Print publication online• High design• Complete freedom for each issueCONS• High production costs for quality• Portrait and landscape versions need designing• Not real-time
    18. 18. Database driven PROS • Non-specialist content curators • Real-time content • Low production costs • Shared content CONS • Less design freedom
    19. 19. Native cms-driven apps
    20. 20. Our solution
    21. 21. Why this works • Best of both worlds • Web standards • Platform independent • Automatic version control • App store independent • Lower production costs • Coexists alongside native apps • Practical for publishers
    22. 22. A practical solution
    23. 23. You don’t need a large team
    24. 24. You don’t have to be Einstein
    25. 25. Just you...
    26. 26. It’s all about the interface
    27. 27. An additional barrier
    28. 28. ADvance access control system
    29. 29. Thank you for listeningAbacus e-Media14 –16 Regent Street, London, SW1Y 4PHTel: +44 (0)20 7766