5. Mobile
It's becoming increasingly difficult to determine what
exactly is mobile and what isn't
The challenge is to make it simpler, easier, and
better for users to connect whenever, wherever and
however they want
11. Context
Context doesn’t necessarily determine intent
Making decisions about what people want based
simply on the device they are using is a little
bit like telepathy
21. Foundation Solutions
1. Business/User Goals 1. Native Apps
2. Audience/Personas 2. Web Apps/Mobile Sites
3. Strategy 3. Responsive Design
4. Content 4. Adaptive Process
22. Twitter BBC iPlayer Telegraph Times
Eyewitness British Heart Foundation RSPCA Just Giving
Native Apps
Developed/targeted to a specific OS.
Should have a specific purpose, be beautiful,
accessible, and high quality.
25. Web Apps/
Mobile Sites
Work using a web browser
using HTML5, CSS3,
and Javascript. Can be
targeted to specific devices
26. Responsive Design
Work using a web browser using HTML, CSS,
and Javascript. Devices are treated as a spectrum
(based on capabilities) rather than treated as
mobile vs desktop - provides basic reach
to all platforms/devices
30. Adaptive Process
Start with responsive content/designs...
...then consider a mobile site for specific platforms
if your users would benefit from different
content or presentation
31.
32. App Vs Browser
e Native App Browser/Mobile Site
• Paid or free • Free
• Separate versions required for each • Accessible to all cross-platform/browsers.
operating system (OS) Can be optimised/targeted to specific OS
• Customisable/can integrate with device • Discoverable – search/linked through the
design, features and functions wider web and engaged on social media
• Run locally with quick loading and fluid • Internet reliance. Local caching/HTML5
interaction storage options
• More cost/time investment required • Less investment/native web technologies
• Updated through new versions for users to • Relatively simple to maintain with instant
download. updates to all users.
33. Adaptive Content
Safari Readability Instapaper
User tools now exist to free up content from
a single endpoint. The challenge is how can we
design for our content in such a way that
the reader won’t reach for them?