Lessons, Innovations, and the Road Ahead with Bruno
Session Description
Session Abstract:
Over the last four years, Bruno has redefined what an API client can be.
By pioneering a file-based, Git-native, local-first model for managing API requests, Bruno introduced a developer-centric alternative to the cloud-heavy tooling that dominates the space.
In this talk, we’ll walk through a technical retrospective - what it took to build a file-based API client from the ground up, the design decisions that shaped it, and the tradeoffs we made along the way.
We'll also unveil OpenCollection: A new open standard for representing API collections.
Designed to be portable, extensible, and versionable, OpenCollection paves the way for open tooling, deeper integrations, and collaboration across teams and tools.
About Bruno:
Bruno is a Local-only, Git-friendly and OpenSource API client. Unlike other tools that rely on cloud based collaboration, Bruno embraces the simplicity of the filesystem based approach along with Git to enable seamless sharing and version control of API Collections.
The project has garnered over 34,000 Github stars, has over 300 contributors and is used by over half a million developers every month. We continue to push the boundaries and are innovating on providing better developer experience while working with API's
Key Takeaways
Key Topics Covered:
Technical Retrospective
Lessons learned from four years of building and scaling a file-based API client - covering architecture, file formats, performance, editor integration.
OpenCollection: An Open Standard for API Collections
A deep dive into the OpenCollection specification - its schema, validation model, and how it's designed for interoperability across tools, systems, and workflows.
Static Documentation from Collections
How to generate clean, dependency-free API documentation directly from local request files and publish it anywhere, without relying on any backend infrastructure.
Session Categories
Which track are you applying for?
Speakers
Anoop M D
Reviews
We have had a "story" and "intro" talk about Bruno before so a technical deep dive will be a welcome addition. This year, I would like if the speaker goes deeper into the technical concepts since the community is already familiar with Bruno
Great job highlighting what you want to get into, this seems like an enriching talk, not an ad.
If you can give many practical examples of the new possibilities and opportunities that this combination of API client and git-based file collaboration has unlocked, then it could be a very good talk.
This is clearly written by someone very familiar with their project and with good anecdotes it could be an enriching time.
Don't be shy about getting into the technical details of what it takes to make an API client and config schemas and all that stuff that goes into being able to import and export settings and collaborate.
As another reviewer said, I do want to see more technical dives in successful project such as Bruno but this exact topic doesnt put up a convincing enough case.
In agreement with other reviewers. The audience is well aware of Bruno. A technical deep dive would be better.