46
sponsors Sunday, August 8, 2010

Mobile Strategy & Product Dev. - iRush

Embed Size (px)

DESCRIPTION

Foils from my Presentation at ProductCamp - Austin.

Citation preview

Page 1: Mobile Strategy & Product Dev. - iRush

sponsors

Sunday, August 8, 2010

Page 2: Mobile Strategy & Product Dev. - iRush

Mobile Strategy & Product Developemnt.

Andrew W. Donoho, Donoho Design Group, L.L.C.

[email protected]

Sunday, August 8, 2010

Page 3: Mobile Strategy & Product Dev. - iRush

Who Am I?

I Head a Small iPhone Development Consulting Practice.I also Write iPhone Code Myself.Former Technology Strategy Analyst.Award Winning Mac OS App & HW Dev.

Sunday, August 8, 2010

Page 4: Mobile Strategy & Product Dev. - iRush

The iRush

is almost over.

Sunday, August 8, 2010

Page 5: Mobile Strategy & Product Dev. - iRush

The iFairy

retired.

<http://www.flickr.com/photos/bronwyn_2007/>

Sunday, August 8, 2010

Page 6: Mobile Strategy & Product Dev. - iRush

It’s About

the Business.

L.Gnome <http://www.flickr.com/photos/lgnome/>

Sunday, August 8, 2010

Page 7: Mobile Strategy & Product Dev. - iRush

Sunday, August 8, 2010

Page 8: Mobile Strategy & Product Dev. - iRush

Sunday, August 8, 2010

Page 9: Mobile Strategy & Product Dev. - iRush

Sunday, August 8, 2010

Page 10: Mobile Strategy & Product Dev. - iRush

100+ Million Devices

Sunday, August 8, 2010

Page 11: Mobile Strategy & Product Dev. - iRush

Lester: <http://en.wikipedia.org/wiki/User:Lester>

Sunday, August 8, 2010

Page 12: Mobile Strategy & Product Dev. - iRush

Feb. 2010Sunday, August 8, 2010

Page 13: Mobile Strategy & Product Dev. - iRush

Sunday, August 8, 2010

Page 14: Mobile Strategy & Product Dev. - iRush

What About Developing for:

Nokia S60?

BlackBerry?

Android?

Pré?

Market Size and Development Costs

Sunday, August 8, 2010

Page 15: Mobile Strategy & Product Dev. - iRush

Which One?

Sunday, August 8, 2010

Page 16: Mobile Strategy & Product Dev. - iRush

Which One?

Sunday, August 8, 2010

Page 17: Mobile Strategy & Product Dev. - iRush

View Coordinate Systems

Coordinates in UIKit are based on a coordinate system whose origin is in the top-left corner and whosecoordinate axes extend down and to the right from that point. Coordinate values are represented usingfloating-point numbers, which allow for precise layout and positioning of content and allow for resolutionindependence. Figure 2-3 (page 55) shows this coordinate system relative to the screen, but this coordinatesystem is also used by the UIWindow and UIView classes. This particular orientation was chosen to make it

easier to lay out controls and content in user interfaces, even though it differs from the default coordinatesystems in use by Quartz and Mac OS X.

Figure 2-3 View coordinate system

Standard coordinates

y

x

(0,0)

As you write your interface code, be aware of the coordinate system currently in effect. Every window andview object maintains its own local coordinate system. All drawing in a view occurs relative to the view’slocal coordinate system. The frame rectangle for each view, however, is specified using the coordinate systemof its parent view, and coordinates delivered as part of an event object are specified relative to the coordinatesystem of the enclosing window. For convenience, the UIWindow and UIView classes each provide methods

to convert back and forth between the coordinate systems of different objects.

Although the coordinate system used by Quartz does not use the top-left corner as the origin point, for manyQuartz calls this is not a problem. Before invoking your view’s drawRect: method, UIKit automatically

configures the drawing environment to use a top-left origin. Quartz calls made within this environment drawcorrectly in your view. The only time you need to consider these different coordinate systems is when youset up the drawing environment yourself using Quartz.

For more information about coordinate systems, Quartz, and drawing in general, see “Graphics andDrawing” (page 85).

View Architecture and Geometry 552009-01-06 | © 2009 Apple Inc. All Rights Reserved.

CHAPTER 2

Window and Views

320h x 480vSunday, August 8, 2010

Page 18: Mobile Strategy & Product Dev. - iRush

What about Android?

Sunday, August 8, 2010

Page 19: Mobile Strategy & Product Dev. - iRush

Moto Droid

Sunday, August 8, 2010

Page 20: Mobile Strategy & Product Dev. - iRush

HTC Hero Pro 2

Sunday, August 8, 2010

Page 21: Mobile Strategy & Product Dev. - iRush

Moto Cliq & RIM Storm 2

Sunday, August 8, 2010

Page 22: Mobile Strategy & Product Dev. - iRush

Group Decision:Market Data or

Active Workshop?

Sunday, August 8, 2010

Page 23: Mobile Strategy & Product Dev. - iRush

Sunday, August 8, 2010

Page 24: Mobile Strategy & Product Dev. - iRush

iTunes:It’s a Channel,

Not a Marketing Engine

Sunday, August 8, 2010

Page 25: Mobile Strategy & Product Dev. - iRush

The iFairy

retired.

<http://www.flickr.com/photos/bronwyn_2007/>

Sunday, August 8, 2010

Page 26: Mobile Strategy & Product Dev. - iRush

You still have to create durable

demand.

Sunday, August 8, 2010

Page 27: Mobile Strategy & Product Dev. - iRush

Sunday, August 8, 2010

Page 28: Mobile Strategy & Product Dev. - iRush

Sunday, August 8, 2010

Page 29: Mobile Strategy & Product Dev. - iRush

Sunday, August 8, 2010

Page 30: Mobile Strategy & Product Dev. - iRush

Sunday, August 8, 2010

Page 31: Mobile Strategy & Product Dev. - iRush

Sunday, August 8, 2010

Page 32: Mobile Strategy & Product Dev. - iRush

Sunday, August 8, 2010

Page 33: Mobile Strategy & Product Dev. - iRush

Sunday, August 8, 2010

Page 34: Mobile Strategy & Product Dev. - iRush

There is still lots of money being made.

Sunday, August 8, 2010

Page 35: Mobile Strategy & Product Dev. - iRush

Sunday, August 8, 2010

Page 36: Mobile Strategy & Product Dev. - iRush

Maybe the

iFairy didn’t retire.

<http://www.flickr.com/photos/bronwyn_2007/>

Sunday, August 8, 2010

Page 37: Mobile Strategy & Product Dev. - iRush

WorkshopDefine the market and market size.Matching the Tech. to the opportunity.Make the platform choices to serve that opportunity.Validate your technology choice.Go to market.

Sunday, August 8, 2010

Page 38: Mobile Strategy & Product Dev. - iRush

Sunday, August 8, 2010

Page 39: Mobile Strategy & Product Dev. - iRush

Define the MarketWant help with their Twitter stream.

They have no time. They are overwhelmed.

ch@tter (view in Feb. 2010)70+ million Twitter users.Strong iPhone Community.Entrenched Competitors.

Sunday, August 8, 2010

Page 40: Mobile Strategy & Product Dev. - iRush

Pick The PlatformTweetfall & Screen Real EstateDesktop or Slate? Value prop was based upon making Twitter stream more fun.Always on network. ==> iPadIn April, we hoped for 1 million iPad users in 30 days.

(3 million in 60 days. WoW!)

Sunday, August 8, 2010

Page 41: Mobile Strategy & Product Dev. - iRush

Match the Technology

iPad screen ==> large visualization.We’re just starting here.

Database ==> allows for more complex analysis.

New algorithm’s are coming.

Sunday, August 8, 2010

Page 42: Mobile Strategy & Product Dev. - iRush

Validate Your ChoicesFollow Lean Startup MethodologiesImplement Early, (on cardboard if you have to.)

Interviews are critical.

Standing offer to listen to your design ideas and buy you a beer to boot.

Sunday, August 8, 2010

Page 43: Mobile Strategy & Product Dev. - iRush

Go To MarketMVP “whisper” campaign. (Too quiet)PR session here are useful.Build in techniques to directly engage your customers.Offer to follow our @chatter_onlineEncourage folks to write a review.

Sunday, August 8, 2010

Page 44: Mobile Strategy & Product Dev. - iRush

What was that about the Business?

Sunday, August 8, 2010

Page 45: Mobile Strategy & Product Dev. - iRush

Questions?Contact: Andrew W. Donoho, Donoho Design Group, L.L.C.

[email protected]

+1 (512) 750-7596

Sunday, August 8, 2010

Page 46: Mobile Strategy & Product Dev. - iRush

sponsors

Sunday, August 8, 2010