chrome for android_devfestx

37
Hello, I am Dominic, I talk about mobile strategies.

Upload: dominic-travers

Post on 23-Jun-2015

275 views

Category:

Technology


0 download

DESCRIPTION

A strategic overview of developing for Chrome on Android and native on Android. Touching on the migration from the open web to walled gardens of applications.

TRANSCRIPT

Page 1: Chrome for android_devfestx

Hello, I am Dominic, I talk about mobile strategies.

Page 2: Chrome for android_devfestx
Page 3: Chrome for android_devfestx

It used to be an easy call.

Native apps provide a better experience with most types of content. There is plenty of scope for beautiful design, funky UI elements, and integrating location, social, camera, and sensors.

Web apps are thought of as ugly, clunky, and a vastly inferior experience.

Not for long though..

Chrome for Android is shifting this balance...

Page 4: Chrome for android_devfestx

If you develop your app to run in Chrome, you can manage a single code base that can also run perfectly on iPhone and BlackBerry.

With this you can engage your audience across the platforms that really have app users and revenue.

Maybe one day Microsoft will actually learn how to make a decent browser too...

Page 5: Chrome for android_devfestx

The first question you should ask yourself is...

Do you really need to build an app?

The vast majority of apps just package content from the internet, or bundle it up for the user to post online.

With a few CSS3 skills, a great touch design is easy to deliver to a smartphone browser.

Page 6: Chrome for android_devfestx

Many of the big brands have already chosen the web for their mobile presence...

Page 7: Chrome for android_devfestx

Even some of those with famous applications on mobile are now embracing HTML5 for new projects.

Point your mobile browser at...

http://www.nike.com/jumpman23/aj2012/

...and have a scroll...

Page 8: Chrome for android_devfestx

This is not a dumbed down version of the Volvo web site.

This is the full set of content and features that a prospective Volvo buyer wants to find online regardless of what kind of screen their browser is using.

The challenge is to deliver complete content in a layout that allows for touch navigation and makes immediate sense to the user.

Page 9: Chrome for android_devfestx

In June 2011 the Financial Times bucked the app trend and migrated their iOS customers back to the web.

Page 10: Chrome for android_devfestx

Development for iOS Safari took a team of two developers 9 months to complete. Getting it working well enough in Android browsers took another 3 months.

Total cost of the project was £250,000 / Rs 2 Crore

Page 11: Chrome for android_devfestx

The FT says its app has boosted its mobile business to the extent where it now drives 12% of FT.com subscriptions and 19% of traffic. The newspaper says that in the last six months, its smartphone users have increased by 52%, while tablet users are up 49%.

http://www.guardian.co.uk/media/appsblog/2012/apr/24/financial-times-web-app-2m?CMP=twt_gu

"The origins of the web app come from thinking more broadly about our mobile strategy, and particularly how we are going to cope with developing for numerous different platforms"

Rob Grimshaw. Managing Director

Page 12: Chrome for android_devfestx

"But the real problem with apps was more profound. When people read news and features on electronic media, they expect stories to possess the linky-ness of the Web, but stories in apps didn't really link. The apps were, in the jargon of information technology, "walled gardens," and although sometimes beautiful, they were small, stifling gardens. For readers, none of that beauty overcame the weirdness and frustration of reading digital media closed off from other digital media."

http://www.technologyreview.com/business/40319/

Page 13: Chrome for android_devfestx

The capable web.

There's a lot of talk about the dangerous iPhone monoculture in mobile web development.

http://www.quirksmode.org/blog/archives/2012/02/the_iphone_mono.html

There is now a chasm between WebKit based browsers and those on "feature phones". Opera mini et al.

If you're marketing your app or service in India, you'd be crazy not to have a good looking presence on as much of the mobile web as you can reach!

Chrome for Android gives you the tools you need...

Page 14: Chrome for android_devfestx

Remote debugging with Chrome can and should be used as an aid to testing on all the other mobile browsers you can get your hands on.

In a Test Driven Development team this tool set comes in to it's own. Serious mobile developers need to test on the right range of target devices. Having the Chrome environment as a control during the process of debugging other browsers will minimise regression in the code base.

Page 15: Chrome for android_devfestx

So lets take a close look at developing for Android

Reports of "losing developer mindshare" are just an echo chamber of developers whinging... which they do a lot!

Page 16: Chrome for android_devfestx

October 2010.

112 ROM variants in a sample of 36,427 beta testers of tweetdeck

Page 17: Chrome for android_devfestx

9th May 2012. Open Signal Map Android app.

3,997 Device/ROM variants in a sample of 61,389 users

http://opensignalmaps.com/reports/fragmentation.php

Page 18: Chrome for android_devfestx

"Custom ROMs can overwrite the android.build.MODEL variable that we use for the device model.

This partly explains why a staggering 1363 device models appear only once in our database. That said most of these are indeed genuine devices, just not popular ones.

Some examples of these solitary devices include: the Concorde Tab (a hungarian 10.1 inch device), the Lemon P1 (a dual SIM Indian phone), the Energy Tablet i724 (a Spanish Tablet aimed at home entertainment), the EBEST E68, the MASTONE W18."

Page 19: Chrome for android_devfestx

"It's surprising how little change there has been, 2.3 (Gingebread) was the dominant version 1 year ago, now it's 2.3.3+ which is a revision of 2.3.3 with various bug fixes and minimal changes to the APIs (i.e. few new features for developers to tap into, though NFC and Voice Recognition were added). Note also, one year ago the top two Android versions accounted for 90% of devices now it's closer to 75% - a challenge for developers."

Page 20: Chrome for android_devfestx

This graphic shows the diversity of screen sizes and aspects in the Android ecosystem.Using some sensible break points in a responsive design can serve a good looking layout to any of them.

Page 21: Chrome for android_devfestx

This fragmentation is only going to increase.Get used to it, and develop a strategy to mitigate it.

Page 22: Chrome for android_devfestx

The bigger picture.

Over the last few years internet use has migrated to proprietary platforms.

Facebook, iPhone, Android...

Traffic is migrating to mobile everywhere. The vast majority of growth is from mobile devices.

Increasingly, more & more of this traffic is siloed away from the open internet.

Page 23: Chrome for android_devfestx
Page 24: Chrome for android_devfestx

"the generative Internet is on a path to a lockdown, ending its cycle of innovation"

http://futureoftheinternet.org/download

Page 25: Chrome for android_devfestx

“A year here and he still dreamed of cyberspace, hope fading nightly. All the speed he took, all the turns he’d taken and the corners he’d cut in Night City, and he’d still see the matrix in his sleep, bright lattices of logic unfolding across that colourless void….”

Neuromancer: William Gibson. 1993

Page 26: Chrome for android_devfestx

Gibson's character, Henry Case, is shut off from accessing the networks as a result of a prior indiscretion.

If the internet is allowed to fragment, or is simply cannibalised by proprietary applications. Who's to stop the platform owner revoking your access for any spurious reason they choose?

India is very nearly there with the #ITrules legislation.

Page 27: Chrome for android_devfestx

If you want to do your bit to help keep an open internet available, you need to include a web site or app in your product plans.

If your product is about content delivery, then consider the route that the Financial Times have gone down and wrap your fine tuned web app up and publish it as an .apk.

Alternatively...

Use the web app as a marketing tool for migrating people to an native Android app. Think freemium!Allow free access to selected content or features, then use in app purchasing, or subscription to monetise the product.

Users are clamouring for consistent experiences on mobile.

Page 28: Chrome for android_devfestx

All hail the messiah.

Page 29: Chrome for android_devfestx

Web OS was actually a great experience......the developer tools really sucked though.

Page 30: Chrome for android_devfestx

Android 4 is truly awesome...There are some lovely UI paradigms to play with

Page 31: Chrome for android_devfestx

The card metaphor has made it's way to Android along with Matias Duarte.

The swipe to dismiss is possibly the most natural UI paradigm ever designed.

Now Android owns this...

Page 32: Chrome for android_devfestx

The flexibility of the Action Bar model of navigation will accomodate almost any combination of features and navigational hierarchy.

If you cannot make your content work with the action bar, re-examine your content!

You now need to have a very strong UX design and brand rationale to ignore the Action Bar. It provides the consistency that user want to feel instantly familiar with your product.

Page 33: Chrome for android_devfestx

The Action Bar offers a design convention that can be almost infinitely customised to suit both the function, and the required look & feel of the product.

The response from users to apps that have been remodelled with the new design assets and convention is overwhelmingly positive.

Page 34: Chrome for android_devfestx

Lets take another look at the navigation elements of the Financial Times and Volvo sites...

They are offering expanded menus in one of the ways you can utilise the Action Bar for this.

Page 35: Chrome for android_devfestx

The Android Design guidelines are one of the best resources every made for the mobile designer/developer.

Much of the best practise is just as applicable to building mobile web as it is for apps.

I would even suggest that you use the conventions and iconography for your mobile web app.Then migrating users to the premium Android version will be totally painless.

Page 36: Chrome for android_devfestx

Thanks for listening..Lets discuss...

If you're interested in mobile web development, take a look here...

https://developers.google.com/chrome/mobile/docs/overview

http://www.quirksmode.org/

http://adactio.com/

http://yiibu.com/

Page 37: Chrome for android_devfestx