Client · Developer tools
Betacrew Portle: one developer platform replacing three API tools
Developers were designing, testing and documenting APIs in three disconnected tools, so documentation drifted and onboarding took weeks. We designed Portle, a developer-first platform that brings that work into one workspace.
Executive summary
Developers managed APIs across separate tools for design, testing and documentation, so documentation was always out of date and new team members needed weeks to learn the setup. Designit designed Portle, a developer-first API management platform that brings design, testing, documentation and monitoring into one workspace, with a white-label theming system for enterprise deployments.
What changed is that each view shares context: editing an API definition updates its documentation and test templates, removing the synchronisation problem of a multi-tool setup.
Project facts
- Industry
- Developer tools
- Product
- Portle, an API management platform
- Users
- Developers from junior engineers to senior architects; enterprise admins
- Our role
- Product design, developer UX, design system
- Scope
- One platform replacing three tools; white-label theming
- Tools
- Figma, component library, theming system
Problem statement
How might we replace three disconnected API tools with one workspace developers prefer, that every enterprise customer can make their own?
Empathize
Who we designed for
Developers of every level, and the enterprise admins who deploy Portle under their own brand.
Developers
Design, test and document APIs every day and want one place to do it.
New team members
Need to learn a team's APIs quickly without learning three tools.
Enterprise admins
Brand and configure their own instance without design support.
Pain points
API work was split across three tools.
Documentation drifted out of date.
Onboarding took weeks.
Each deployment needed its own brand without breaking accessibility.
The business and user problem
Documentation lived apart from the API, so it was always outdated. Onboarding to API workflows took weeks because people had to learn three tools and how they connected. The platform also had to support white-label deployment for different enterprise clients.
What we did
Developer experience research
We mapped engineers' daily tool use, timing workflows and documenting every context switch and manual step.
Unified information architecture
A workspace that follows the developer's workflow: define endpoints, test, document, monitor, with shared context across views.
Prototypes with real API data
Tested with developers of different experience levels, which led to an adaptive interface with a density setting and sensible defaults.
White-label theming
Typography, logo placement, terminology overrides and feature toggles, with accessibility maintained under any brand, plus a theme editor for non-technical admins.
Key lessons
- Experts and newcomers need different density. A density setting served both.
- Keep documentation with the thing it documents. Separation guarantees drift.
- White-label is more than colour. Terminology and features vary by client too.
Case studies
The Portle case study
Frequently asked questions
What did Designit design for Betacrew?
Portle, a developer-first API management platform that unifies API design, testing, documentation and monitoring in one interface, with a theming system for white-label deployment.
Why consolidate API tools into one platform?
Because the information is the same. When design, tests and documentation share one definition, documentation stays true and onboarding gets faster.
What is Portle?
Portle is a developer-first API management platform that unifies API design, testing, documentation and monitoring in one interface, designed by Designit for Betacrew.
How does the white-label system work?
Through a theming system that goes beyond colour, covering typography, logo placement, terminology overrides and feature toggles, with accessibility maintained under every theme.
What is white-label theming?
Letting each customer run the product under their own brand: colours, typography, logo, terminology and enabled features, configured by an admin. Portle's themes keep accessibility intact whatever brand colours are applied.
How do you design a developer tool?
Respect the workflow and the expert: define, test, document and monitor in one flow, keyboard shortcuts and density for seniors, progressive disclosure for newcomers, and no ceremony between the developer and the endpoint.
How do you keep API documentation from going stale?
Generate it from the API definition, so editing an endpoint updates its documentation and test templates automatically.
Can Designit work on B2B developer platforms and SaaS products?
Yes. Portle is one example; see our SaaS product design and design systems services for how we approach complex B2B products.
Where can I see the Portle case study?
The full Portle case study, with the problem statement, approach, screens and FAQ, is linked above.
Consolidating tools into one product?
Tell us which tools and which users. We'll tell you how we'd map the workflow first.