apidays Australia 2023 - Mapping Your Business Model To API Design, James Moschou, Criteria

apidays Australia 2023 - Platforms, Products, and People: The Power of APIs
October 11 & 12, 2023
https://www.apidays.global/australia/

Mapping Your Business Model To API Design
James Moschou, Founder of Criteria

------

Check out our conferences at https://www.apidays.global/

Do you want to sponsor or talk at one of our conferences?
https://apidays.typeform.com/to/ILJeAaV8

Learn more on APIscene, the global media made by the community for the community:
https://www.apiscene.io

Explore the API ecosystem with the API Landscape:
https://apilandscape.apiscene.io/
apidays Australia 2023 - Mapping Your Business

Transcript

1. Criteria Mapping your business model to API design apidays Melbourne / 10-11 October 2023
3. An API product owner's story… Case Study
6. Good API design includes product, business and technology.
7. Let's design an Order Fulfilment API! Example Photo by Paul Teysen on Unsplash
8. Our product requirements Place an order Specify the products to order Specify the recipient's address Specify a shipping method Track an order See order status
9. "REST is best"
10. Iteration #1: Resource-oriented design (REST) Order Recipient Shipment Shipments Label Inventory Inventory Products Products Provider
11. "I just want to call one endpoint"
12. API design is a negotiation between the client and provider Client Provider UX All business logic UX + all business logic Just data UX + client logic Common business logic ← Customer Value →
13. Iteration #2: Single endpoint to place and track an order
14. "How do we 10× our revenue?"
15. Awareness Consideration Implementation Expansion Purchase order automation Purchase Global ecommerce retailers Does it scale globally? Transaction pricing Integration time and cost Single integration for all regions Increasing customer volume N/A License fee Does it support my use case?
16. Iteration #3: Parameterise the shipping method
17. Customer and business profiles require different trade-offs Open-ended user experiences Composable resources Zero-touch developers Agility of provider Optimised for immediate needs Total surface area of API Transaction pricing Direct mapping to end-user experience Number of steps per use case High-touch enterprise Client integration time and effort Future proofed Breadth of supported use cases Fixed fee Upsell and cross-sell New customer acquisition
18. Good API design is a function of how many iterations you make. Take-Away
19. TIME PRODUCTION DISCOVERY DESIGN DEVELOPMENT TESTING COST OF CHANGE Fixing a wrong trade-off is costly
20. Prototype Hi-Fi Mockup Hi-Fi Design Lo-Fi Design
21. Thank you Email: james@criteria.sh Book a demo: https://criteria.sh/contact