With our API experts, we'll be discussing public and non-public API.
API quality has multiple angles, like performance, security, scalability, and usability. And whether you are developing a public or non-public API, still one of the key factors that define its success is the API design, which affects both the underlying architecture, as well as the adoption rate of your API product.
How can you come up with the best API design from scratch? How do you identify all possible use cases – for MVP and further down the line? What should be the ideal API design and governance process that will allow all parties to be involved without becoming a bottleneck for the speed of API development? Code-first or API design-first? And how this all should be evolved throughout multiple iterations of your API development lifecycle?
There is no silver bullet to all these questions because every company and every situation is unique. So let's share our experiences.
Everyone is welcome to join us! We are having Q&A after the speakers' talks. This event will be interesting not only for technical specialists but also for the product, design, and any API enthusiasts.
Head of API
Product Lead, Platform Frameworks
Developer Relations Lead, EMEA
API Management Team Delivery Lead
Colm leads Developer Relations in EMEA at Slack, where he and the team help developers build more pleasant and productive ways to work. Before Slack, he ran the Engineering team at Kitman Labs, and worked on the iOS and Platform teams at Facebook.