about life, technology and how the latter transforms the first.
Monday, May 16, 2011
Mobilism in Amsterdam - a mobile web focused conference
An excellent conference with very good atmosphere
4 Mobiletech'ers was attending the very first mobilsm
conference in Amsterdam May 12-13. Its audience is developers and
semi-technical people, and there is no sales pitches what so ever. Some
of the best brains in the industry were present and it was really an
atmosphere of getting together and trying to solve the new challenges of
the web in general.
Why mobile first ?
1. Growth = Opportunity
2. Constraints = Focus
3. Capabillities = Innovation
Mobile traffic has surpassed desktop traffic an its growth rates
dictates that it will be MUCH larger than desktop web. Morgan stanley
predicted this should happen 2012, but it happened 2 quarters ago in
Amazon have $1 billion in sales from mobile
Facbook : Mobile users use facebook twice as much
Twitter : 40 % is mobile (78 % use twitter.com !) 14% use m.twitter.com)
Size of screen 1024 has lead to polluted web sites. We simpy put
stuff there "Because we can". 320x480 is good - it forces us to focus
Speed : Amozon have tested and 100ms in deley restults in 1% loss in sales
Where are we mobile ? ANYWHERE & EVERYWHERE
84% at home
80% during misc times throughout the day (when we have a small time slot anywhere)
64% at work
Partial attention requires - focused desing.
Ipad is a home device - in bed
Orientation change - use that to enhance the experience - ref mail client on android
Location detection, augmented reality "Overlay relevant digital data based on your current view of the world"
Front face camera
Eric smith "We have technology that can identify you with 7 pictures" - "and there is 7 pictures of you on the web" recongnizr
A live implementation of some of these principles can be found at bagcheck
Mobile web is growing 8 times faster
Native vs Web - YAWWWWWN - The conclusion is : IT DEPENDS
Room for both, we just have to figure out when to use which, and we have started to do so - this is not an interesting problem
- one core app written in CSS, JS THML
deployed to several platforms
Ideally js, and css stored on device
It can be deployed but its still an webside
Tools apparat.io , phonegap
Native apps offer device apis and web apps will have to offer them to (phonegap does this today)
The Fisherman story - anno 2014
Mobile changed the fishermans work, when he could start to call his
friends and find out which harbor he would get the best price for his
in 2014 he will:
Have a smart phone for $25
keep track of prices, and receive alerts against corrupt police officers (wild guesses but not important)
Apps will be transferred P2P via bluetooth or NCF due to cost
Data will be JSON - lighthweight, already works everywhere
Data (JSON) transferred via SMS - it already works everywhere and
has a controllable cost - it is a proven and simple PUSH technology
Premium SMS or something similar
Appstores - what do appstores do for us ?
Works for apple but will it work for anybody else.
Your app have to compete with 10 000 s of other apps and you have to advertise it anyway
future will be not only credid card (because the fisherman does not have a credit card)
Operator billing (because anyone with a phone can pay that way) example m-pesa by vodaphone
Cost of ownership for appstores is to high
documentation and best practises
Of more than a 100's appstores only a very few will survice
It work well for apple because
Apple - has leverage with enthusiatic developers and affiliate consumers
Google - Has leverage with developers, but does not really have leverage with consumers
Nokia, Samsung, RIM - Have leverage with consumers, but not with developers
Appstores will not disappear, but its status as default (a must ) will disappear - apple apps store will survive
Content first - we should think less interface and more content - more semantic structures
Todays web sites are huge data containers - this may make sense if you are google or amazon and have a lot of data.
Content must also be responsive - not only design - what is content was design ?
WAC - Alliance of 72 carriers Standard for appstores ( try to create an federated appstore) Influenced by bondi,
They define a similar set of apis as DAP
Hi5 is a wrapper implementation that bridges the two
PhoneGap is an implementation of upcoming API's (try to support both)
Security like correctnes is not an add on feature. We still need to
find non-intrusive ways to solve the security problen. Will not work if
the API's promt : Can I use your camera ? Can I use your GPS? etc.
API reference at docs.phonegap.com
still need $4000 worh of equiopment to test on all needed devices
Android emulators are just like Android - it takes forever"
Weinre - Web Inspector Remote - debugging tool like firebug for webkit browsers