Rough Notes for Chris Heathcote – A Mobile Internet Manifesto
It isn’t Nokia policy, he’s trying to be provocative.
1b internet 2b mobile user 5b unconnected
many networks, you’ll be connected to the internet
100% voice, 50% java, 10% native apps
these are not barriers:
display device speed text entry network speed
1000 bln. text messages in 2005
we might be the last gen. that uses querty
fixed 1000M wireless 100M fixed internet 10M wireless internet 1M
people want terabyte speed, we need to think what’s good enough now
we’re there already
barriers: data cost, battery life, 2 hour problem, smart networks
a picture used to cost 15 euros to upload
fixed price is really important in data
battery hasn’t seen innovation like the rest of mobile tech.
in the west we’re always less than 2 hours away from a “real” computer
David S. Isenberg: fat pipe, always on, get out of the way
assumption is that mobile phones can’t work in a dumb network, rich client sutuation
mobile internet does not exist!
good mobile browsers, they’re here
other important stuff: smart clients – easy to develop: Flash Lite, Python
browser is like swiss army knife
E.g.: Backpack. Nice web app. He’s been trying to make a mobile version of Backpack.
Why is that different?
He can’t release it publicly yet, but he will soon.
PC + mobile: home + away
They’re far more useful together than seperate
What’s useful? 10 x easier 10 x cheaper 10 x a day
Mind like water (GTD) mobile is excellent for this, you can action them
Mobile is social
Timekilling? Competition: books, iPods, etc.
Social is more interesting, you want to take those elements from web apps to mobile
Internet is push + pull
Mobile web browser: access to all kinds of phone stuff.
He loves it, he wants to see people build stuff with it.
Out of sight message: because he wanted a domain he’s going through a proxy.
Not being online all the time is interesting from a presence point of view.
no need for separate mobile sites
basic accessibility and web standards still rule
lots of websites are assuming users have lots of bandwidth – that’s bad on both the web and mobile
data is very important (useful data)
APIs are great, XML is great, as long as they work
we’re not special: Google tries to be helpful by forcing you into the mobile version
Don’t repurpose content for mobile.
People are people… they’re the same. They have the same needs. Make sure they have access.
Create mobile sites. Aim at the 2b, not the 1b.
Mobile is going to be the main way to access the internet in the future.
Voice is interesting as well.
Q One thing you mentioned is flat rates. We can’t solve it as devs. Any ideas to force carriers to do it? A Carriers aren’t as uncanny as you think. They realize that money can be made from flat rate.
Sites can be built for mobile using web standards easily. That’s key.
Q What do you need for the mobile Backpack? A The series 60 phones running Python. We want to open source it so people can port it.