Upgrade to Pro — share decks privately, control downloads, hide ads and more …

We've got a website for that (Fluent)

We've got a website for that (Fluent)

Fluent Conference, San Francisco

Andrew Betts

May 29, 2012

More Decks by Andrew Betts

Other Decks in Technology


  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
  2. Digital distribution •  Ubiquity across conventional and ‘post PC’ devices

    •  Ease of use •  Lo cost •  Lo risk of obsolescence •  Ideally something designed for publishing
  3. 2001: BlackBerry®. No e’re talking. (except ironically e’re not talking

    because RIM ouldn’t add telephony capabilities for another 3 years)
  4. 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.
  5. 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.
  6. Popularly: app (n).  tool designed for touch sensitive smartphones

    and tablets, hich can be launched from the homescreen, ith a ‘native feel’
  7. 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,
  8. 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
  9. 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
  10. The future of eb Type TV/ Desktop Netbook/ Laptop +

    Phone Tablet Click Touch Point Move Speak
  11. 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
  12. •  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
  13. 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   ☐   莢   丢  
  14. Snoman sniffing •  Speed vs storage •  Encode some stuff,

    don’t encode other stuff •  Encoded strings prefixed ith a snoman ☃嘴璢璪䖪...
  15. 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.