The document discusses the benefits of developing mobile web apps over native apps. It notes that executives often want native apps but these can be "vanity apps" that are not necessary. Mobile web apps have advantages like being easier to update and not requiring different versions for different platforms. While native apps have advantages like access to device features, a mobile web app may fulfill users' needs in many cases. The document recommends starting by saying no to native apps and justifying it if one is truly needed later.
9. “Throwaway” user test question
Me: “So have you ever tried to
(almost embarrassed asking it) access utility client’s website on
your phone?”
Participant:
(tradesman, not computer savvy)
10. “Throwaway” user test question
Me: “So have you ever tried to
(almost embarrassed asking it) access utility client’s website on
your phone?”
Participant: “I was sitting on my couch
(tradesman, not computer savvy) watching TV. My computer was
down in the hallway. I couldn’t be
arsed getting off the couch. So, I
tried to see if I could get my bill
on my phone.”
(He couldn’t.)
16. supports 5 native mobile platforms
“We could probably save 70% of our
development budget by switching to a single,
cross-platform client
Phil Lebin, CEO
http://url.ie/a1xl
17. Defining “native” vs. “mobile web”
Objective C HTML, CSS, JS
works best on webkit browsers
Java
C ++
23. Native isn’t always better
Native app only Both Web app only
Gyroscope and Store data offline Much easier to test,
Accelerometer Access GPS prototype, and rollout
Accessing filesystems Have app-like UI and Can update
(e.g. address book, transitions immediately (no app
photos) store approval),
Accessible as app
Fully-immersive customers don’t have
from home screen
experience (e.g. to update the app
gaming) Can link to the app
??Findability?? (e.g. SMS with link to
Support in-app
purchases your bill)
(Apple takes 30% cut) HTML 5 is continually
Camera adding hardware
capabilities
Smoother and more
responsive
33. Be wary -- this stuff changes fast
2010:
“(Website owners interested in developing an
iPhone app might start by developing an iPhone-
targeted website, where most of this book’s
design principles also apply.)”
34. Be wary -- this stuff changes fast
2010:
“(Website owners interested in developing an
iPhone app might start by developing an iPhone-
targeted website, where most of this book’s
design principles also apply.)”
2011:
“Platforms are risky places to put your
business...If you can do it with the
Web -- do it with the Web. It’s
faster, cheaper, and easier.”
Web app masters tour, 2011: http://www.lukew.com/ff/entry.asp?1281
36. The takeaway:
start by saying no to native
It’s not that native apps are the wrong
approach. But your starting point for
your mobile strategy should be a web
app. Force yourself to justify the native
decision.
Stand up to your CEO.
Editor's Notes
How many people have completed or in the process of working on mobile apps?\nHow many people built those apps specifically for iphone or android?\nHow many people built them as web apps?\nWho’s not sure what the difference is?\n
They’re everywhere, on everything\n
Peter-Paul Koch is a mobile platform strategist, consultant, and trainer in Amsterdam, the Netherlands.\n
An app who’s sole purpose is to make a single calculation. These guys just wanted to have something in the app store.\n
\n
It’s an imperative\n
It’s an imperative\n
It was a blackberry phone\n
It’s great if you only care about your customers with iPhones, but, then you have to do it all over again, from scratch, for each platform\nBuild (in different languages), test, maintain – all independently – you’re quadrupling your efforts and costs.\n\nEvernote was making different argument -- but they develop for 5 native platforms!!!\n\n
\n
This is more local, and based on people actually using the web on their phones\n
The context of this quote is he was defending the need to go native\n
Need to get programming language for Blackberry, Windows...\n
\n
\n
\n
Basically what they know is if they download it in the the app store\n
Instagram is a massive hit. But it’s a project that’s conceived of as an app. They have a one-page website. This has nothing to do with your business.\n\nThey have no customers, so they start with one platform. This makes sense for them. You or your clients probably have a lot of customers already -- this approach makes much less sense. It’s not that you’re cutting off potential customers -- you’re cutting off actual customers.\n
\n
http://www.quora.com/What-are-the-best-hybrid-mobile-apps-html5-embedded-in-native-app-for-added-functionality\n\nThis basically eliminates the distinction between native and mobile web app\n
\n
\n
Hold on a second, what about all this talk about this talk about responsive web design?\n
Book is from 2010 -- entirely focused on iphone apps. He puts this point in brackets.\n\n“For the foreseeable future, I believe the best way forward is a common-denominator mobile website—with graceful degradation so that a majority of mobile users are served—paired with one or three audience-appropriate native apps.”\n