Mobile Developer's Dilemma

Post on 11-May-2015

10,858 views 1 download

Tags:

description

Presented at the O2 Litmus Hack Day - Dilemma = what should I develop as a mobile developer?

transcript

(Mobile) Developer’s DilemmaPaul Golding

1

Copyright Paul Golding, 2008

http://wirelesswanders.com

Paul G - Mobile Apps Expert...Help companies with their mobile product strategies and architecture: Operators, Equipment vendors, Media companies, Start-Ups

Done a long time: Mobilist since 1990, last 12 in applications - 14 patents in mobile design. Worked in all parts of the mobile ecosystem. Expert member MIDP 3.

Do it for real: 2006/7 Chief Applications Architect, MotorolaMobile Apps, Mobile TV/IPTV

Done it a lot: Architect/designer of numerous mobile/Internet solutions - First ever mobile portal (Zingo)

Done it widely: Worked on mobile projects in all continents: O2, Vodafone, 3 UK, 3 Italia, Virgin Mobile, Etisalat, Du, BSkyB, OMTP, BT, GSMA, Netscape, Morroc Telecom, Orascom, CSL, Al Jazeera, Lucent, NTT DoCoMo, MTC, Extreme, Metrowalker, mConnected...

2

Copyright Paul Golding, 2008

3

3

The developer’sdilemma:

3

The developer’sdilemma:

What should I build?

4

Copyright Paul Golding, 2008

4

a. Application

Copyright Paul Golding, 2008

4

a. Applicationb. Open APIs

Copyright Paul Golding, 2008

4

a. Applicationb. Open APIsc. Community

Copyright Paul Golding, 2008

4

a. Applicationb. Open APIsc. Community

d. Platform

Copyright Paul Golding, 2008

4

a. Applicationb. Open APIsc. Community

d. Platforme. Service

Copyright Paul Golding, 2008

5

5

What should I build?

5

What should I build?

... f. Experience

Think UX, think whole productPOP3 client is not a product…If the interface clumsy = not a whole product….if the tariff is unclear = not a whole product...Can't easily type = not a whole product….Users like a WHOLE PRODUCT....

6

100% of your emails accessible within seconds...

..Securely....Anytime...

..Anywhere......Fixed price.....Spam-free.....

Copyright Paul Golding, 2008

Successful Mobile Experience

Discovery

Can I easily find the service?

Does it say something meaningful to me on the box?

Does it make me a promise?

Is it one click away?

Unboxing

Does it work out of the box?

Can I play immediately or do I have to “get it?”

Can I invite others?

Investment

Is this easy to use?

Can I access my data?

Can I easily ‘bump into’ this?

Does it get better the more I use it?

Passion/Evangelism

I will love using this because...

I will want to tell others because...

If I stop using this, I will miss it because...

How is my loyalty rewarded?

Anticipation

I will want to keep coming back because...

I look forward to new features because...

Conversation

I can easily use this with others

I can easily find others

It adapts to my social relationships

It adapts to my social context

Accessible/Contextual

I can easily bump into this because...

It understands my needs because...

It adapts to my situation because...

Mobile Web 2.0 Ecosystem

Transparent business terms and tariff

Open, secure and extensible architectures

Reliable networks

7

Copyright Paul Golding (www.paulgolding.com) 2008

Successful mobile UX (in more detail)

Copyright Paul Golding, 2008

Usable devices

Mobile UX: exploit context:

8

Location

Activities

FriendsTime

Proximity

Interests

All mobile products should take context into accountCopyright Paul Golding, 2008

Context: Web 2.0, Microformats:

9

Increasingly, mobile product design needs to take context into account

Location

Activities

Time

Proximity

Interests

Friends

Web 2.0

Microformats

Copyright Paul Golding, 2008

10

10

What should I build?

10

What should I build?

... g. Business!

Think business architecture

11

MarketTrends

Businessmodels

TechnologyEnablers

Profitableapp

(Mega/Micro)Developers aim here

Copyright Paul Golding, 2008

How do we do this?....

Social Business Model - Co-creation & work with Frenemies

12

Techies

Profitablebusiness

Copyright Paul Golding, 2008

UsersCo-create or die! (TODAY: Find some co-conspirators!) Social Coding.

Ecosystem: common log-in, use microformats, exploit mash-ups: Click-off, but not click-out!

Open ideas exchange: it’s mostly in the execution, not the idea or technology

Share the risk - make frenemies

A place to do all the above: O2 Litmus!?

Entrepreneurs

13

Copyright Paul Golding, 2008

13

What should I build?

Copyright Paul Golding, 2008

13

What should I build?2009: Opportunities:

Copyright Paul Golding, 2008

13

What should I build?2009: Opportunities:

Mobilized social applications

Copyright Paul Golding, 2008

13

What should I build?2009: Opportunities:

Mobilized social applicationsVideo apps

Copyright Paul Golding, 2008

13

What should I build?2009: Opportunities:

Mobilized social applicationsVideo apps

Enterprise social software

Copyright Paul Golding, 2008

13

What should I build?2009: Opportunities:

Mobilized social applicationsVideo apps

Enterprise social softwareCloud computing

Copyright Paul Golding, 2008

13

What should I build?2009: Opportunities:

Mobilized social applicationsVideo apps

Enterprise social softwareCloud computingSOHO solutions

Copyright Paul Golding, 2008

14

2009: Mobile Drivers:Increased device usability

Greater Web 2.0-dependencyMore data-friendly tariffs

Mobilized social networksApp stores

Greater user participation/appetiteEasier transactional capability (€)

Copyright Paul Golding, 2008

Thank youPaul Golding

paul@wirelesswanders.comwirelesswanders.com

Follow

@pgolding(C) Copyright Paul Golding, 2008

15