The webinar discusses how to effectively map out an API strategy, emphasizing the importance of aligning investments with customer needs and defining target segments. It highlights the need for an engaging developer channel and establishing industry goals that differentiate partnerships from platform businesses. The session aims to provide a comprehensive framework for understanding and executing successful API initiatives.

1. Mapping out your API Strategy4.20.11 @ 11:05 PSTVOIP or Dial-in (see chat)Brian Mulloy@landlessnessSam Ramji@sramji

2. Welcome to our first webinar.

3. @landlessness@sramji

4. “Rapid API” Workshop Webinar Series Today: Mapping out your API Strategy 10 Patterns in Successful API ProgramsPragmatic REST: API Design FuAPI Tech & Roadmap ConsiderationsDriving API Adoption

5. Part 1: Mapping out your API Strategy

7. You need a strategy for the explosion in consumption.

10. Do business in the customer’s full context.

12. Align your investments with your customers.

13. Example iPadapp

14. What About Android?

15. And LinkedIn?

16. And Another Partner?

17. And Another Product?

18. Resources Required

19. The Big Bet of Yesterday

20. Many Bets of Today

21. How to Do It All?

22. API Initiatives

23. Internal

24. Partners

25. Open

26. Enterprise API Engine

27. API Value ChainAppUserAPITeamWorld ofAPIsAppStoreInternalSystemsAppDeveloperAPIApp

28. “John MusserProgrammable Web

29. But how?

30. Let’s break it down

31. Establish Target SegmentsEngage Developer ChannelSet Industry Goal

32. target segmentsAn API should extend your core businessinto a new part of the market

33. target segmentsYour core business already has key performance indicators

34. target segmentsSo apply your KPIs to the new market segment you’re targeting with your APIs

35. target segmentsWhat is the market impact you need to create in order to succeed as a business?

36. target segmentsWhat does the targetsegment need that it is not getting from you today?

37. target segmentsThe answer will be the foundation of your API strategy.

38. developer channelIn most cases the channel for your API will be developers, but what do they need?

39. developer channelA profit motive.

40. developer channelHere are the leading profit models for developers today

41. developer channelApp sales

42. developer channelIn-app purchases

43. developer channelAffiliate royalty

44. developer channelYour advertising spend

45. developer channelMarket awareness of their offering

46. industry goalIf you don’t know where you’re going, you definitely won’t get there

47. industry goalPartnerships and platform businesses are very different things.

48. industry goalPartnerships are formed to serve a known set of entities

49. industry goalA partner API should be traceable to each partner’s relationship

50. industry goalAnd support end-to-end business processes

51. industry goalA platform exists to create massive and unpredictable opportunities

52. industry goalAll your technology, support, and community decisions will be about surviving the scale of adoption

53. That’s the strategy dimension.

54. The execution dimension is what you already know.

55. Planning.Management.Organization.

56. Putting all this in context gives us a map for our API strategy

58. In summaryOpen, Partner, or Internal?Align Execution with Strategy (try 9 boxing)

59. Next TimeMapping out your API Strategy10 Patterns in Successful API ProgramsPragmatic REST: API Design FuAPI Tech & Roadmap ConsiderationsDriving API Adoption

60. THANK YOUQuestions and ideas to:@landlessness@sramji@apigee