mobile web and apps world new orleans session 3 lessons learned from multiple deployments

31
Lessons Learned from MultiPlatform Deployments Mobile Web and Apps World Forum May 2012

Upload: nextvision-media

Post on 21-Dec-2014

142 views

Category:

Technology


0 download

DESCRIPTION

Lessons Learned from Multiple Platform Deployments This session will highlight the common pitfalls and issues facing deployment over multiple platforms. We will discuss lessons learned and recommended solutions in bringing application s to markets quickly, efficiently and with maximum coverage. Richard Smith, CTO - OpenPath Products

TRANSCRIPT

Page 1: Mobile Web and Apps World New Orleans Session 3 lessons learned from multiple deployments

Lessons Learned from Multi‐Platform Deployments

Mobile Web and Apps World Forum

May 2012

Page 2: Mobile Web and Apps World New Orleans Session 3 lessons learned from multiple deployments

Background

Page 3: Mobile Web and Apps World New Orleans Session 3 lessons learned from multiple deployments

• One of the oldest mobile app developments shops in the world.

• 2001: SMS, WAP• 2002: J2ME• 2003: Brew• 2005: Billing Subscription Services, Sidekick• 2006: Blackberry, Windows Mobile• 2007: iOS• 2008: Android• 2010: Qt, HTML5, OpenGL• 2011: Windows Phone 7

• Based in Annapolis, Maryland.

Page 4: Mobile Web and Apps World New Orleans Session 3 lessons learned from multiple deployments

3

0

200

400

600

800

1000

1200

1400

1600

01‐M

ar‐01

01‐Sep

‐01

01‐M

ar‐02

01‐Sep

‐02

01‐M

ar‐03

01‐Sep

‐03

01‐M

ar‐04

01‐Sep

‐04

01‐M

ar‐05

01‐Sep

‐05

01‐M

ar‐06

01‐Sep

‐06

01‐M

ar‐07

01‐Sep

‐07

01‐M

ar‐08

01‐Sep

‐08

01‐M

ar‐09

01‐Sep

‐09

01‐M

ar‐10

01‐Sep

‐10

01‐M

ar‐11

Ope

nPath Prod

ucts’ D

evice Inventory

Android

Brew

J2ME

OpenPath Founded

OpenPath launches platform for AT&T app distribution

OpenPath ports WAP apps to J2ME

OpenPath ports J2ME to Brew

OpenPath ports J2ME to multiple carriers & phones

OpenPath releases WAP and SMS Tools OpenPath offers

MRC solutions for AT&T developers

OpenPath ports games and apps for Virgin phonesOpenPath offers

Sidekick porting

OpenPath offers iPhone conversion and development

OpenPath offers Android conversion and development

OpenPath offers porting services for Blackberry and Windows Mobile

OpenPath offers Gamelobby support and libraries

OpenPath offers Nokia Qt porting and conversion

OpenPath releases SMS Testing Tools

OpenPath launches Storefront Deck Analysis service

Trademarks are the properties of their respective ow

ners

Nextel launches

J2ME

Verizon launches

Brew

Sprint, AT&T, T-Mobile

launch J2ME

Sprint launches

GameLobby

Virgin Mobile launches

J2ME

T-Mobile launches Sidekick

Cingular offers MRC

billing

Brew devs

earn $3B

AT&T launchesiPhone

T-MobileAndroid launches

Blackberry World & Ovi

launch

Cingular rebrands as AT&T

iPad released

Windows Phone 7 released

AT&T becomes Cingular

OpenPath offersWP7 conversionand development

OpenPath developsapplications using OpenGL

OpenPath completes over 5,000 Brew builds

OpenPath provides custom application design support

Page 5: Mobile Web and Apps World New Orleans Session 3 lessons learned from multiple deployments

OS Type Distinct QtyAndroid 97Bada 2Blackberry 6Brew 38iPhone 4J2ME 10MeeGo 3Symbian 7Windows Phone 7 11

Android

BadaBlackberry

Brew

iPhoneJ2ME

MeeGoSymbian

Windows Phone 7

See also PhoneArena.com for other industry data

New Devices by Type in OpenPath Inventory since May 2011:

Page 6: Mobile Web and Apps World New Orleans Session 3 lessons learned from multiple deployments

iOS22%

Android28%

WP712%

J2ME/BREW20%

Qt 9%

BB9%

Page 7: Mobile Web and Apps World New Orleans Session 3 lessons learned from multiple deployments

Industry Trends

Page 8: Mobile Web and Apps World New Orleans Session 3 lessons learned from multiple deployments

Manufacturer Innovation

Device Fragmentation

Device Porting & QA 

“Universal Dev Tools”

Tool Fragmentation

Page 9: Mobile Web and Apps World New Orleans Session 3 lessons learned from multiple deployments

• One‐Time Storefront Purchase• Subscription APIs• In‐App Purchase / AVB• In‐App Advertisements

Page 10: Mobile Web and Apps World New Orleans Session 3 lessons learned from multiple deployments

• Good Industry Patterns:– Hardware Innovation– Open, well‐supported SDKs and APIs– Devices that consistently implement APIs– Multiple billing models – Low‐friction store submissions– Balancing Quality and Quantity in the Stores

Page 11: Mobile Web and Apps World New Orleans Session 3 lessons learned from multiple deployments

• Qualcomm:– $3+ Billion in developer revenue– Consistent SDK and APIs– Consistently implemented on devices– Single submission to multiple storefronts– Good developer support– Good Monetization strategy 

• 1 time billing, subscriptions, demos, IAP

Page 12: Mobile Web and Apps World New Orleans Session 3 lessons learned from multiple deployments

• Carefully select development tools• Carefully select Reference and Target Devices• Effectively use the tools available to you• Learn from past projects & experienced partners• Apply a good QA strategy• Plan a monetization strategy from the start

Page 13: Mobile Web and Apps World New Orleans Session 3 lessons learned from multiple deployments

DevelopmentAndroidiOSWP7

Page 14: Mobile Web and Apps World New Orleans Session 3 lessons learned from multiple deployments

• Native SDKs & APIs• Hybrid Native / Webkit• HTML5• “Rapid” and “Universal” Runtimes

Page 15: Mobile Web and Apps World New Orleans Session 3 lessons learned from multiple deployments

http://developer.android.com/resources/dashboard/platform‐versions.html

Page 16: Mobile Web and Apps World New Orleans Session 3 lessons learned from multiple deployments

Manufacturer Nickname Width Height OSSamsung Galaxy S 2 480 800 2.3.3Motorola Droid X 480 854 2.2.1Motorola Bionic 540 960 2.2.1HTC Rezound 720 1280 2.3.4Amazon Kindle Fire 600 1024 2.3.4Samsung Galaxy Nexus 720 1280 4.0.2Samsung Galaxy Tab 7 600 1024 2.2Samsung Galaxy Note 800 1280 2.3.6

Potential Reference Device List as of April 2012:

Page 17: Mobile Web and Apps World New Orleans Session 3 lessons learned from multiple deployments

• Cocos2d• TapJoy• Analytics: Omniture, Flurry• Openfeint• Urban Airship• Open Street Maps• JabFab (http://www.JabFab.com )• AllJoyn

Always check the licenses first

Page 18: Mobile Web and Apps World New Orleans Session 3 lessons learned from multiple deployments

• Consider using OpenGL.• Use the SD Card ‐ it’s faster.  • Use the platform tools ‐‐ XCodeMemory Analyzer, Eclipse MAT, etc.

• Use NDK if you hit Android memory or performance problems.

• Design separately for tablet vs phone.  

Page 19: Mobile Web and Apps World New Orleans Session 3 lessons learned from multiple deployments

• Don't try to make iOS‐native UI widgets on Android, or vice‐versa.

• When converting menu‐driven applications…– Convert the business logic line for line– But create the display logic appropriately for the target platform.

Page 20: Mobile Web and Apps World New Orleans Session 3 lessons learned from multiple deployments

• Design and develop to provide the best of each platforms.

• Don’t go for lowest‐common‐denominator. 

• … but ensure business logic is consistently implemented across platforms.

Page 21: Mobile Web and Apps World New Orleans Session 3 lessons learned from multiple deployments

• “Beautifully Different”• For Apps, start fresh with your design. Follow Metro Guidelines.

• Find an experienced partner or go to training.  

• If converting from an existing app, try to start from an Android codebase.

Page 22: Mobile Web and Apps World New Orleans Session 3 lessons learned from multiple deployments

MS provides some good info...

http://wp7mapping.interoperabilitybridges.com/Home/Library?source=Android

Page 23: Mobile Web and Apps World New Orleans Session 3 lessons learned from multiple deployments

• CPU processing • Tombstoning• Panorama vs Pivots• Use Live Tiles• Smoothstreaming only• No Flash

Page 24: Mobile Web and Apps World New Orleans Session 3 lessons learned from multiple deployments

QA

Page 25: Mobile Web and Apps World New Orleans Session 3 lessons learned from multiple deployments

• Create Test Plans in conjunction with Design and Development.

• Efficiently address fragmentation.• Always test under multiple network conditions.

• Include automated tools where they make sense.

Page 26: Mobile Web and Apps World New Orleans Session 3 lessons learned from multiple deployments

• Don’t use an API unless there is a clear use case benefitting the user.  

• Be mindful of iOS monetization rules.• Do not use UDIDs.  Use UUIDs.  • Use the iOS configuration.

Page 27: Mobile Web and Apps World New Orleans Session 3 lessons learned from multiple deployments

MonetizationPaths

Page 28: Mobile Web and Apps World New Orleans Session 3 lessons learned from multiple deployments

• Google• Samsung• Nokia

• WAC• Verizon• AT&T / Motricity• AT&T / Playphone• T‐Mobile

• Fortumo• Playphone• Amazon• Boku• Zong

• PayPal• Google Wallet

Page 29: Mobile Web and Apps World New Orleans Session 3 lessons learned from multiple deployments

• iOS Dvl

• Android Dvl

• Google Play IAP

• Amazon IAP / Amazon Store

• Verizon IAP / Verizon Store 

• AT&T IAP / AT&T Store 

• Samsung IAP / Samsung Store 

• Mac OS X

• WP7 / Microsoft Store 

• WAC IAP / WAC Carrier Stores 

• Google TV

Page 30: Mobile Web and Apps World New Orleans Session 3 lessons learned from multiple deployments

Questions?

Page 31: Mobile Web and Apps World New Orleans Session 3 lessons learned from multiple deployments

• We will be in New Orleans this week• Richard Smith, CTO

[email protected]– 1.410.897.0406