Main Takeaways:
- Internal customers are customers too
- API Designs need testing & validation just like human designs
- Platform teams = service teams
10. What is a
platform?
- At its core: Sharing
- A platform enables multiple products to run on it by sharing data,
experiences and value with its developers
- Might be
- External - developer.squareup.com
- Internal - Cox
- Hybrid - Kabbage
11. What is a platform?
Examples
- Square Virtual
Terminal
- Bentobox
- Simpletix
12. Shared data, experiences, value
- Data: Building blocks
- Payments, Refunds, Orders, Catalogs, Items, Locations
- Experiences
- Payment entry & processing, seller dashboard, refund notifications, sales
reporting
- Value
- Less to build, managed payments
19. Platform Interfaces
- Application Programming Interfaces -
APIs
- Aka REST APIs, HTTP APIs, JSON APIs, GraphQL
- Software Development Kits - SDKs
- Native “wrappers” or more experiential
- SDKs can have their own APIs
20. What are APIs
- Applications use APIs to interface with your application
- Humans use graphical user interfaces to interface with your application
- Or voice
- Or text
- Less adaptable
- APIs allows software to software operations on resources: Verb +
Noun
- Create
- Read
- Update
- Delete
22. APIs
- Small building blocks
- Spend time designing, stress test your design
- Backwards compatible
- Don’t be afraid to version
- Do be afraid thoughtful of releasing new APIs, new fields, and
endpoints
- Lest you find yourself supporting it while doing The Big Rewrite™
23. Summary
- Platform: Shared data, experiences, value
- External, Internal, Hybrid
- Who is your customer - follow the money
- Even internal platforms have customers!
- Research the developer, and their
customer
- APIs
- Machines talking to machines
- Design, design, design
- Write the docs first
- Validate value, usability