Platforms, ecosystems, and the future of...

40
Platforms, ecosystems, and the future of software Michael Mace, April 7, 2009 mike@rubiconconsulting.com

Transcript of Platforms, ecosystems, and the future of...

Platforms, ecosystems, and the future of software

Michael Mace, April 7, 2009

[email protected]@ g

About Rubicon

• Help high tech organizations win markets through business and market strategyg gy– Since 1999– Practices: define, deliver, defend, optimize

Software ecosystems Page 2

About me

• Macintosh software developerApple• Apple– Director of Mac platform marketing– Director of customer & competitive analysis– Director of customer & competitive analysis

• Palm/PalmSource– VP of product planningVP of product planning– Chief competitive officer

Software ecosystems Page 3

Everybody wants a platform

Software ecosystems Page 4

Where did this "platform" thingWhere did this platform thing come from in the first place?

Software ecosystems Page 5

Agenda

• A quick history of software platformsWhat makes a platform win?• What makes a platform win?

• Where will the industry go next?

Software ecosystems Page 6

W b h d b ttWe remember hardware better than software

• What's the firstfirst electronic computer?p

• ENIAC 1946• ENIAC, 1946

Software ecosystems Page 7

What was the first business computer?

Software ecosystems Page 8

J. Lyons & Co.

Software ecosystems Page 9

J. Lyons & Co.

• 30,000 employees150m meals a year• 150m meals a year

• 36 miles of Swiss roll a day

• ...all on paper

Software ecosystems Page 10

1951: The first business computer

• Lyons LEO, 1951– Paid Cambridge $5k

5 000 sq are feet 4k of memor– 5,000 square feet, 4k of memory weighing half a ton

– Payroll, inventory, order management...

• Processed an employee's wages in 1.5 seconds (vs. 8 minutes)

L• Lyons spun out as a computer company

Software ecosystems Page 11

David Caminer, the first business app programmer / systems analyst

Software was synonymous with hardwarewith hardware

• First verified use of term "software"

• John Tukey, 1958– Statistician

software

Statistician• Princeton and Bell Labs

– Helped design the U2– Popularized the term "bit"

Software ecosystems Page 12

What was the first third party app?

Software ecosystems Page 13

The first third-party app

• Applied Data Research Autoflow, 1964

– An automatic flowcharting program• Also the first patented software

– RCA first then IBM– RCA first, then IBM– IBM: free clone– US government antitrust suit, 1969– January 1, 1970: IBM unbundles

Software ecosystems Page 14

The first third-party app

• Martin GoetzProject Manager– Project Manager, Autoflow

– Holder of first software patent

• Mike Guzik– Lead programmer,

Autoflow

Software ecosystems Page 15

Computerworld, June1968

1970s: Rise of the killer app

Software ecosystems Page 16

1979: VisiCalc

• "Visicalc could some day become the software tailbecome the software tail that wags (and sells) the personal computer dog."p p g– Ben Rosen, later the founder

of Compaq, writing as an l t ith M St l Dan Bricklin at theanalyst with Morgan Stanley Dan Bricklin at the

West Coast Computer Faire, May 1979

Software ecosystems Page 17

1980s: Separation of OS from hardware

• August 1980– IBM signs Microsoft

to supply the OS forto supply the OS for its new computer

• August 1981– IBM PC ships

• 1982– Microsoft licensesMicrosoft licenses

MS-DOS to 50 hardware manufacturers

Software ecosystems Page 18

Agenda

• A quick history of software platformsWhat makes a platform win?• What makes a platform win?

• Where will the industry go next?

Software ecosystems Page 19

The web discovers APIs

• Mashups

Software ecosystems Page 20

Mobile discovers APIsOne-year growth in

• Intense interest due to recent successes of a

25,000

registered developers

recent successes of a certain mobile device

15 000

20,000

10,000

15,000

0

5,000

Software ecosystems Page 21

0

Mobile discovers APIsOne-year growth in

• Intense interest due to recent successes of a

25,000

registered Palm developers

recent successes of a certain mobile device

15 000

20,000

10,000

15,000

0

5,000

Software ecosystems Page 22

01998 1999

"That's unfair"

Software ecosystems Page 23

Reality: Most platforms fail

Software ecosystems Page 24

Definition of failure depends on your goalon your goal

– Give me a marketing boost over h i i

Need for developers

Don't carethe competition

– Get developers to add features

Don t care

C h tI don't have time to develop

– Address user problems and sub-

Care somewhat

dd ess use p ob e s a d submarkets that neither of us could have tackled alone

Care a lot

Software ecosystems Page 25

What motivates developers?

Software ecosystems Page 26

How platforms fail

Almost impossible to

Apps hard to findStore financials outrageous

monetizeg

Inconsistent APIs (raises cost)Very hard to get on device

Software ecosystems Page 27

The PC and Windows

• The RiseIBM drives belief in large user base– IBM drives belief in large user base

– Hardware architecture permits powerful apps (for the time)– Open APIsOpen APIs– Clone licensing drives additional growth; virtuous circle

• The Decline– Microsoft preys on successful software developers– Intel and Microsoft can't coordinate innovation

Software ecosystems Page 28

The less friction, the more apps

• Easy to developPowerful APIs great documentation and support uses– Powerful APIs, great documentation and support, uses existing tools/languages, easy to debug

• Easy to sellasy to se– No artificial barriers, easy discovery, marketing,

installation, billing, reasonable financials

• Large user base– Or the belief that it'll get large

Software ecosystems Page 29

Pluses and minuses of iPhone ecosystemecosystem

Strength WeaknessA f i liAPIs Very capable App functionality limited

Develop- Familiar if you're a Mac Nonstandard; Java and pment

ydeveloper Flash missing

Store Built in, pretty good terms Arbitrary screening by Apple price pressureApple, price pressure

User basePerception of world domination, high traffic seen by websites

(Will it continue to grow?)by websites

Software ecosystems Page 30

The ultimate ecosystem doesn't yet existdoesn t yet exist

• Advantages of an integrated platformAdvantages of an integrated platform– Great discovery, billing, support, APIs

• Advantages of web app developmentAdvantages of web app development– Lots of Ajax-style tools, instant deployment, huge user

base, write once run anywhere

Software ecosystems Page 31

Agenda

• A quick history of software platformsWhat makes a platform win?• What makes a platform win?

• Where will the industry go next?

Software ecosystems Page 32

Opportunity in disaggregation

1940s 1950s 1960s 1970s 1980s 1990s 2000s

•Computers

•Software that lets computers do multiple tasks

• Independent software

•OS platforms separated from hardwarehardware

•Platforms separated from OS

Software ecosystems Page 33

"The Network is the Computer"

Application Windows PC hardware

SolarisApplication

Solarisor Java Sparc servers

Software ecosystems Page 34

Problems

• LatencyRichness of APIs• Richness of APIs

• Access to on-device features and data

– High latency• Mobile makes it worse

– Limited bandwidth– High cost– Battery life

– Limited capacity– Limited coverage

Software ecosystems Page 35

Next: The OS disaggregates

Application Local hardwareLocal OS

Software ecosystems Page 36

The Meta-Platform is the Computer

Cloud servers

Cloud components

Application

L l OS

Local hardware

Local OS

Software ecosystems Page 37

Local hardware

Remember

• If you're a developer"Which platform gives me the best long term business– Which platform gives me the best long-term business proposition?"

• If you're a platform vendoryou e a p at o e do– "How can I create a better ecosystem than the other

guy?"

• Opportunity: Disaggregating the OS– Balancing local and cloud OS services

Software ecosystems Page 38

Discussion

[email protected]://mobileopportunity blogspot com• http://mobileopportunity.blogspot.com

Software ecosystems Page 39

Win MarketsT d Ad i hi h h fi kiTrusted Advisors to high-tech firms seeking to transform their visions into strategies, strategies into plans, and plans into results.

Practices:

Define / Design / Defend / Optimize

Software ecosystems Page 40