Do I need an app for that?

With more than 500,000 apps available to consumers, 2012 has been labeled the year of the app. But as you consider your mobile strategy it is legitimate to ask "Do I need an app for that?" This session will use case studies to explore the contexts in which an app is the right solution and also highlight the situations in which other mobile web solutions are the right choice for your users.

1. DO I NEED AN APP FOR THAT?
2. We simply must have an app! Why exactly? Because everybody has an app!
3. Do we really need an app for that?
4. “We need a website”
5. “We need a flash site”
6. “We must be on facebook”
7. “We must be in the app store”
8. Thanks very much!
9. NOT VERY SENSIBLE
10. Building native is not always best
11. Poor visibility
12. Limited real estate
13. Use lose &
14. future devices
15. Barriers to entry
16. Expensive to build
17. Thanks again!
18. and again and again and again
19. Native apps are right sometimes
20. Clearly defined tasks
21. Used regularly
22. Uses native features
23. Speed
25. BUT, THAT’S IT
26. Documents Applications Native Hybrid Website (content-centric) (behavior-centric)
27. What about content?
28. If not native, then what?
29. DO NOTHING
30. You have a website
33. Responsive web design
34. Build once
35. Single site Smartphone Tablet Mobile Desktop
37. It can be a challenge
38. LET GO OF PIXEL PERFECT
39. Consensual hallucination JEREMY KEITH @ADACTIO
40. There are known knowns; there are things we know that we know. There are known unknowns; that is to say there are things that, we now know we don't know. But there are also unknown unknowns – there are things we do not know we don't know. Donald Rumsfeld United States Secretary of Defense
41. Thinking ‘content out’ is hard
42. Image file size
43. Readability
44. looking to the future
45. More native features
47. APPS HAVE THEIR PLACE
48. BUT CONSIDER THE OPTIONS
49. APPS ARE FOR TASKS
50. THE WEB IS FOR CONTENT
51. THANKS @boaworld or boagworld.com http://www.headscape.co.uk/mobile/