We've got a website for that (Fluent)

Fluent Conference, San Francisco

Transcript

1. e’ve got a ebsite for that The FT eb app and the future of the mobile eb ndre Betts (@triblondon) Fluent, San Francisco, 29th-31st May 2012
3. Nespapers don’t make money from selling papers. e make money from selling content.
4. Less paper. More content.
5. Digital distribution •  Ubiquity across conventional and ‘post PC’ devices •  Ease of use •  Lo cost •  Lo risk of obsolescence •  Ideally something designed for publishing
6. 1999: P. Seriously?
7. 2001: BlackBerry®. No e’re talking. (except ironically e’re not talking because RIM ouldn’t add telephony capabilities for another 3 years)
8. 2007: iPhone. Cracked it.
9. 2008: pps arrive. Er, ait, hat?
10. hat exactly is an “app”, anyay? But ait…
11. Strictly: app (n). abbreviation of ‘application’,  computer program ith an interface, enabling people to use the computer as a tool to accomplish a specific task. ord processing, spreadsheet, and communications softare are all examples of applications.
12. s ‘adopted’ by pple: app (n). n installable computer program ritten for a specific mobile platform, installable via an online app store, ith a touch-optimised interface.
13. Popularly: app (n).  tool designed for touch sensitive smartphones and tablets, hich can be launched from the homescreen, ith a ‘native feel’
14. hat an ‘app’ is to us: app (n). a distributed computer softare application designed for optimal use on specific screen sizes and ith particular interface technologies,
15. Screen size Interface technology + Phone Tablet Notebook TV/desktop Touch Click Type Move Speak Think Point
16. Native/hybrid app + Phone Tablet Touch
17. Traditional eb Type TV/ Desktop Netbook/ Laptop + Phone Tablet Click
18. People built apps because their ebsites eren’t adaptive to the ne touch interfaces
19. The promise of eb today Type TV/ Desktop Netbook/ Laptop + Phone Tablet Click Touch Point
20. Should e use native apps? •  Not ubiquitous •  Can require proprietary tech •  Ne tech, could be obsolete quickly •  Not designed for publishing •  Very easy to use
21. The eb in a ‘post PC’ orld •  Still ubiquitous •  Free and open source •  Very lo risk of obsolescence •  as designed for publishing •  Not easy to use – loest common denominator user experience
22. Make the eb better
23. + Traditional eb Phone Tablet
25. + Touch Traditional eb
27. Make your perfect recipe using eb technologies.
28. The future of eb Type TV/ Desktop Netbook/ Laptop + Phone Tablet Click Touch Point Move Speak
29. Challenges for the eb •  Layout –  dapt, adapt, adapt •  Navigation and interaction –  Interpreting touches is a subtle art •  Offline use –  Just reinvent the hole ay the eb orks •  Rethink backend architecture –  Feer pages, more PIs •  nalytics –  Record activity hile user is offline
30. Floed columns
31. Floed columns
32. •  Load an article page hile offline •  Not in broser cache, not in app cache •  pp cache serves fallback •  Fallback acts like front controller Offline start
33. Re-encoding base64 Original   A   B   C   D   o   p   q   9   b64  index   0   1   2   3   40   41   42   61   As  binary   000000   000001   000010   000011   101000   101001   101010   111101   Shi?ed   00000000  00010000   10000011  10100010   10011010  10111101   As  hex   00  10   83  A2   9A  BD   UTF-­‐16   ☐   莢   丢  
34. eird. Not your father’s compression algorithm, that’s for sure.
35. Snoman sniffing •  Speed vs storage •  Encode some stuff, don’t encode other stuff •  Encoded strings prefixed ith a snoman ☃嘴璢璪䖪...
36. In summary •   ebsite can be an ‘app’ •  But it needs to be tailored for size and interface tech. •  eb technologies can do this •  eb approach retains all the benefits of the eb that you give up hen building native.
37. “Don’t build native apps, build eb apps” -­‐  Tim  Berners-­‐Lee  
38. Thanks andre@labs.ft.com @triblondon, @FTLabs Do you ant to build this stuff? Join in. jobs@labs.ft.com