Description

Presented at Denver Startup Week - October 2012

As developers, one of the largest challenges is deciding what kind of mobile application to build: mobile web, hybrid, or native mobile. This is a thorny question because there isn’t a black-and-white answer. The solution can sit anywhere from pure mobile web to pure native mobile, or somewhere in between. In this session, Shane Church, technical lead at EffectiveUI, uncovers how the answer is tied to deep consideration of architecture decisions, the needs of the user, and the business goals for both the short and long term. He goes step-by-step through the questions and project considerations they should address when preparing to embark on a mobile development project. You'll learn that your responses to these questions will drive a clear path to the right decision that keeps end-users and organizational goals in line.

Say if a mobile app is not useful, it results in a negative69% perception about the brand32% Have told others about a bad experience with a mobile app Have avoided downloading applications from a company13% due to a previous bad experience with another app offered by that brand -Harris Interactive, November 2010

Have downloaded an app based on a review or66% recommendation Have recommended an app because of a positive57% experience -Harris Interactive, November 2010

HybridBuilt using a combination of HTML5 and JavaScript and packaged with aframework like PhoneGap or Appcelerator Titanium or a custom native shellPros: Full device capabilities Cost effective multi-device support Sticky app and control over contentCons: User interactions not native Need to build native wrappers for multiple platforms

NativeBuilt using platform native languages and tools like Objective-C for iOS, Javafor Android, and .NET for Windows PhonePros Sticky application access Richest interactions can be built Full device capabilities availableCons Need to build for multiple platforms Typically more expensive to build Requires specialized developer expertise for each platform

Cross-Platform NativeBuilt using .NET and Xamarin’s Mono Touch for iOS and Mono for Android andVisual Studio for Windows PhonePros Same pros as traditional native development Use a common development language 70-90% code reuse between platformsCons Some delays in accommodating OS updates Dependence on a third party vendor

Native Examples iOS Android Windows Phone 7 Pearson eCollege

Native Examples iOS Android Windows Phone 7 Chase Mobile Banking

The Facebook ConundrumWhat does Facebook’s switch from HTML5 to native on iOS mean?

“We deliberately made a trade off to get to scale. We used HTML5 to test and try things out, and people love that in the browser, but they have different expectations of a native IOS app. So with this release we rebuilt the app from scratch over the last 9 months and the main improvement is performance. Now there’s a lot more code built in Objective-C than HTML5.” Mick Johnson Facebook iOS Product Manager

"HTML5 is still incredibly important to us. We get two times the mobile traffic [on m.facebook.com] than from iOS and Android combined." Mick Johnson Facebook iOS Product Manager

How to Pick Your PoisonA guide to selecting the right technology approach for your application

Ruling Out the Mobile Web Do you need access to device hardware capabilities like the camera, or accelerometer? Do you need a presence in the app stores (Google Play, iTunes, Windows Phone Marketplace)? Does your app need to take advantage of push notifications?

Going Native Does the app need to perform any processor or graphics intensive operations like 3D graphics or real-time calculations i.e. most games? Does the app need to be functional offline? To what degree?

Am I a Hybrid? What is the goal the user wants to accomplish by using your app? How sensitive is the app to variance in network performance? What is the platform matrix that you want to support? What is your tolerance for supporting multiple apps and operating systems? What percentage of the market are you comfortable ignoring?

Case StudyHow I Addressed This Question For An EffectiveUI Client

Cartegraph Targeting Municipal Governments Needed an app for mobile field workers who processed multiple work orders for assets such as signs, benches, and fire hydrants Already in the process of developing a Web-based tracking application for desktop clients Needed the ability to upload pictures and access mapping functionality

Cartegraph

The User Is Key

We now have the foundation for easy to deploy, composite applications.But those applications will live or die on the acceptance of their human interfaces. Anthony Franco EffectiveUI Founder and President

UX, UI, Digital Innovation & Strategy Presentations ...

iCloud

iCloud makes sure you always have the latest versions of your most important things — documents, photos, notes, contacts, and more — on all your devices.Read more

These presentations are classified and categorized, so you will always find everything clearly laid out and in context.
You are watching All you need to know about the Microsoft Band presentation right now. We are staying up to date!