47
@precedentcomms #PrecSem Putting mobile first 24 th May, 2012 John Campbell Head of mobile Mark Baillie Creative Director

Putting Mobile First

Embed Size (px)

DESCRIPTION

Slides from John Campbell and Mark Baillie's mobile seminar.

Citation preview

Page 1: Putting Mobile First

@precedentcomms #PrecSem

Putting mobile first24th May, 2012

John CampbellHead of mobile

Mark BaillieCreative Director

Page 2: Putting Mobile First

app

Page 3: Putting Mobile First

1.A changing world 2.What are my options

3.The optimum approach

4.Making it happen

5.Considering the future

End

Page 4: Putting Mobile First
Page 5: Putting Mobile First
Page 6: Putting Mobile First

1.A changing world

2.What are my options? 3.The optimum approach

4.Making it happen

5.Considering the future

End

Page 7: Putting Mobile First

Mobi

Responsive

Framework

Native

Page 8: Putting Mobile First
Page 9: Putting Mobile First

1.A changing world

2.What are my options?

3.The optimum approach4.Making it happen

5.Considering the future

End

Page 10: Putting Mobile First

Mobi

Page 11: Putting Mobile First

UI flow flow

Page 12: Putting Mobile First
Page 13: Putting Mobile First

Mobi

What it’s good for:

- Providing focus and clear

structure

- Deploying without impact

on main website

- Delivering quickly

- Wide reach working via

browser

- Can be designed to

understand and respond to

screen size or orientation

Consideration:

- Careful consideration to content

impacting performance.

- Keep the design simply effective

- You need to design for tablet and

phone to maximise experience.

- Links to m. or mobi domain name

Page 14: Putting Mobile First
Page 15: Putting Mobile First

Responsive

Page 16: Putting Mobile First
Page 17: Putting Mobile First
Page 18: Putting Mobile First
Page 19: Putting Mobile First

What it’s good for:

- Reflows the same content

from the website

- Content is presented on all

devices and screen sizes.

- Architecture of the site

remaining the same

- Single update of content

Consideration:

- Cannot apply a different t tone

of voice for mobile usage.

- Experience not built around the

user or context

- Requires to think in % and not

fixed width

- Supported screen size has to

be chosen

Jakob Neilsen – 21st May 2012It's cheap but degrading to reuse content and design across diverging media forms like print vs. online or desktop vs. mobile. Superior UX requires tight platform integration.

Responsive

Page 20: Putting Mobile First
Page 21: Putting Mobile First

Frameworks

Page 22: Putting Mobile First
Page 23: Putting Mobile First

What it’s good for

- Lets you develop once and

deploy many

- Cross device support

widening reach

- A balance between rich

design and reach

- Simplifying the interface

whilst enabling functionality

- Deployment via app stores

Considerations:

- Will not be a rich interface

- Restricted in functions

- Balance between features and

reach

- Typically uses HTML5 and

JavaScript.

Framework

Page 24: Putting Mobile First

Yes No

Page 25: Putting Mobile First

Native apps

Page 26: Putting Mobile First
Page 27: Putting Mobile First
Page 28: Putting Mobile First

What it’s good for

- Provides a rich interface

- Uses the full phone feature

set

- Designed around the user

- Optimal performance

- Provides joy of use

- Can differentiate your brand

Considerations:

- Needs to be developed for

each device type

- Designs typically can be

shared

- Data is a key consideration for

unconnected use

Native

Page 29: Putting Mobile First
Page 30: Putting Mobile First
Page 31: Putting Mobile First

1.A changing world

2.What are my options

3.The optimum approach

4.Making it happen 5.Considering the future

End

Page 32: Putting Mobile First

Content

Mobile from the ground up

- Custom approaches

- Considered context

- Specific content

A mobile first content approach

Making mobile from pre-existing

- Desktop applied to mobile

- Stress / break points

- Reworked content

An adaptation approach

Page 33: Putting Mobile First
Page 34: Putting Mobile First

Typical assets

- Logos

- Iconography

- Image galleries

- Product shots

“What about

performance. Won’t

a lot of images slow

down the mobile

experience?”

Images

Page 35: Putting Mobile First
Page 36: Putting Mobile First

Data

The four point plan:

1. Ensure your existing web API

does not bundle unnecessary

data with requests for data

2. Expand your API to deal with

short, quick requests and hook

it into your CMS solution as

soon as possible

3. FEO is vital. Use mobile

optimisation and analytics tools

to see where your delivery

speeds can be improved

4. Track user interaction in your

app using an analytics tool

Sadly not true:

Users are sympathetic

to poor network

coverage and adjust

their expectations

when WIFI isn’t

available.

Page 37: Putting Mobile First

“The more channels I

run, the more resource

I’ll need, right?”

Avoid digital bloat by

monitoring the

effectiveness of your

channels and adjust your

resourcing accordingly

Resource & Process

Page 38: Putting Mobile First
Page 39: Putting Mobile First

Work sheet

Page 40: Putting Mobile First

1.A changing world

2.What are my options?

3.The optimum approach

4.Making it happen

5.Considering the futureEnd

Page 41: Putting Mobile First

UI flow flow

Page 42: Putting Mobile First

The future of shopping

Page 43: Putting Mobile First

1.A changing world

2.What are my options?

3.The optimum approach

4.Making it happen

5.Considering the future

End

Page 44: Putting Mobile First

Digital Finance Forum 2011

A communications consultancy specialising in delivering creative solutions for a digital world.

A UK Top 10 digital design agency

– 80 experts

– 5 sectors

– 5 locations

– 21 years

About us

Page 45: Putting Mobile First

We believe in…

Page 46: Putting Mobile First

Find our Precedent group on LinkedIn for a chance to find out more about our seminars, network, share ideas and quiz the Precedent team on seminar issues and more!

and follow us at @precedentcomms for Precedent news, seminar info and general observations#PrecSem

Page 47: Putting Mobile First

Content

A quick show of hands…

Q. Could you support a new IA, navigation and structure (Mobi)?

Q. Could you streamline your content and IA for multi device (Responsive)

Q. Could you create content that would support a broad user base (Framework app)

Q. Could you create content that would enhance advanced functionality (Native app)