Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
In a world of pervasive connectivity, APIs are more important than ever before. We can learn much from the rich history of APIs, but even more promise lies ahead of us. Difficult hardly begins to describe API development, but drawing from other disciplines provides a clearer path to superior APIs. Building and evolving the Heroku APIs has been full of epic wins, tragic fails and ongoing struggles. Learn about our journey and join our community to discuss, document, and build tools to realize the promise of a brighter API future.
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
In the video titled **API by Design**, Wesley Beary discusses the complexities of API development and shares insights from his experience at Heroku. The presentation emphasizes the importance of designing user-friendly APIs while learning from both successes and failures in API evolution. Beary introduces his journey from understanding APIs as a consumer to becoming a creator, highlighting significant distinctions between consuming and producing APIs. Key points discussed include: - **User Experience Design:** Emphasizing that the feel of interacting with an API can be more important than its appearance, deriving lessons from user experience and information design. - **Philosophy of Design:** Drawing from Ruby’s principles, such as the principle of least surprise, to create APIs that are intuitive for users who are already familiar with similar interactions. - **Evolution of Heroku API:** Sharing insights into the organic and often inconsistent nature of the original Heroku API and the need for a more coherent and public-facing API. - **Documentation and Tools:** Introduction of various tools like the HTTP API design guide and JSON schemas to standardize API creation, improve documentation, and streamline team collaboration. - **Structure and Simplicity:** The drawbacks of overly nested structures in APIs are discussed, with Beary advocating for flatter hierarchies that ease navigation and access for users. - **Practical Tools:** He describes tools like Pliny for API creation and Committee for validation, which aid in maintaining consistency and facilitating better practices during development. Significant examples include: - The development of validation tools that automatically confirm compliance with defined schemas, showcasing the importance of structured API responses. - Moving towards an umbrella architecture that allows independent API services while presenting a unified front to consumers. In conclusion, Beary encourages discourse around API design and acknowledges that many professionals in the field share uncertainties about best practices. He emphasizes the value of community and shared experiences to drive the industry forward. The video ultimately serves as a call to action for developers to contribute to the evolving narrative of API design, improving user experience and fostering collaboration within the tech community.
Suggest modifications
Cancel
