Developer Tools Product Design

Developer tools product design is the design of the console a developer works in after the first API call: environments, API keys and their permissions, webhook endpoints, API versions and the actions that cannot be undone. Gestures designs developer tools so every console action has an exact equivalent in the API and the CLI, and every irreversible action names what it will break before it runs.

Developer tools product design with Gestures costs $2,250 per week, $4,000 for a two-week sprint or $7,500 per month for ongoing work across releases and API versions. Every plan covers strategy, design and review on a scope agreed before work starts.

Every console action has a code equivalent

Developers switch between the console, the CLI and the API within the same task, so a setting that exists in only one of them sends them searching. Gestures designs each console action with the matching API request and CLI command beside it, filled with the values the person just chose and ready to copy.

  • A copy-as-cURL or CLI command next to every form that creates or changes a resource.
  • Resource IDs shown in full and in the exact format the API returns, copyable in one click.
  • Form fields that carry the API parameter name beside the human label.
  • Console filters that map to query parameters, so a filtered view can be repeated in a script.
Model playground with system prompt, model, response format, temperature and token settings beside the response, and a Get Code button.
A model playground whose Get Code button turns the chosen settings into code, a Gestures interface study on Dribbble.

Keep test and live impossible to confuse

A change made in the wrong environment is the most expensive mistake a developer console allows, so the current environment must be visible on every screen and inside every copied value. Stripe's API keys documentation shows the pattern: sandbox keys start with pk_test_, rk_test_ and sk_test_, and live keys with pk_live_, rk_live_ and sk_live_.

Environment cues in a developer console and the mistake each prevents
CueWhere it appearsMistake it prevents
Environment name and color in the headerWhere it appearsEvery console screenMistake it preventsEditing live settings while believing it is a sandbox
Environment prefix in keys and IDsWhere it appearsCopied keys, log entries and support ticketsMistake it preventsPasting a live key into test code, or the reverse
A confirmation that names the environmentWhere it appearsDestructive and billing actions in live modeMistake it preventsDeleting live data out of habit
Separate data in each environmentWhere it appearsLists, logs and usageMistake it preventsTest traffic read as real customer activity

API keys with scopes, a one-time reveal and safe rotation

An API key screen is a security control, and its design decides how much damage a leaked key can do. Stripe displays a live secret key one time when it is created and cannot reveal it later, so a console that follows this pattern needs a creation screen where copying the key is the obvious next step.

API key lifecycle and the screen each step needs
StepWhat the screen provides
CreateWhat the screen providesName, environment and scopes chosen before the key exists, with the narrowest scope as the default
RevealWhat the screen providesThe full key shown once, a copy button and a plain warning that it will not be shown again
UseWhat the screen providesThe date the key was last used, the sources of recent requests and the scopes in effect
RotateWhat the screen providesA new key issued while the old one keeps working for a period the developer chooses
RevokeWhat the screen providesThe integrations that will start failing, named before the key is disabled

Webhook endpoints that show each delivery attempt

Webhooks fail out of sight, so an endpoint screen has to show what was sent, what came back and what happens next. Stripe's webhook documentation states that in live mode it attempts delivery for up to three days with an exponential back off, which means a developer needs the time of the next attempt and a way to resend a single event.

  • A delivery list with the event type, HTTP status, response time and attempt number.
  • The request payload and the endpoint's response shown side by side.
  • The time of the next automatic attempt, plus a resend control for one event.
  • Disabling an endpoint as a separate, reversible step before deleting it.

Destructive actions that name what they break

A destructive action in a developer product breaks systems outside the console, so the confirmation must list those consequences, not ask whether the person is sure.

Destructive developer console actions and the safeguard each needs
ActionWhat the person must know firstSafeguard
Delete a projectWhat the person must know firstThe keys, endpoints and stored data deleted with itSafeguardType the project name to confirm, with a waiting period before data is erased
Revoke a keyWhat the person must know firstThe services that called the API with it recentlySafeguardShow recent request sources and offer rotation instead
Change the default API versionWhat the person must know firstThe response fields that change for existing integrationsSafeguardA sample response in both versions and a rollback window
Remove a team memberWhat the person must know firstKeys and endpoints they created that stay activeSafeguardA list of their keys with transfer or revoke options

API versions and deprecations inside the console

A breaking change announced only in the changelog reaches developers after their integration fails, so the console should show which API version each account and request uses and what an upgrade changes.

  • The version pinned for the account, and the version of each request in the logs.
  • A deprecation notice on the screens that use the affected feature, with the date it stops working.
  • An upgrade checklist built from the account's own traffic, listing only the changes that affect it.
  • A way to try the new version in a sandbox before switching live traffic.

The developer surface Gestures runs itself

Gestures operates a public MCP server that AI apps connect to for studio information, and its setup page puts the server URL and connection details first, the same order we recommend for a console's connection screen. Ragip Diler, who leads Gestures, worked on MCP and security workflows for AI products as Senior Product Designer at Venice, an independent design studio for AI and venture-backed companies.

Developer tools product design scope and cost with Gestures

Developer tools product design with Gestures costs $2,250 per week, $4,000 for a two-week sprint or $7,500 per month for ongoing work. The plan follows the number of console areas in scope.

Developer tools product design scopes and the plan that fits each
ScopeWhat it coversPlan
API keys and accessWhat it coversCreation, scopes, reveal, rotation, revocation and team accessPlanWeekly sprint, $2,250 per week
Webhooks and eventsWhat it coversEndpoint setup, delivery history, attempts, resend and signingPlanWeekly sprint, $2,250 per week
Environments and destructive actionsWhat it coversTest and live separation, confirmations and recoveryPlanTwo-week sprint, $4,000
A growing developer consoleWhat it coversNew resources, versions, SDK surfaces and a shared component setPlanMonthly partnership, $7,500 per month

For an overview of developer products, from the first API call to error messages, see our developer tools design page. Usage, latency and error charts are covered by developer tools dashboard design, and the homepage and docs entry by developer tools website design.

Most chosen

Monthly partnership

$7,500$10,500USD / month

Studio $7,500 + Growth $3,000 / month

For a developer product that ships new endpoints, SDKs and versions every month. Set the current focus each month and review what needs attention next.

Strategy · Design · Review

Work starts within 1 day of payment.

Cancel anytime.

Start your project

Weekly sprint

$2,250$4,000USD / week / 2 weeks

+ $3,000 / month for Growth

For one console area, such as API keys, webhook endpoints or the version upgrade flow. Agree the API reference and the engineering contact before starting.

Save $500 with two weeks: $4,000 instead of $4,500.

Strategy · Design · Review

Work starts within 1 day of payment.

Cancel anytime.

Start your project

Add Growth to a studio plan

SEO, content strategy and content production, alongside your design team. Growth is billed monthly. Cancel anytime.

+$3,000 / month

See Full Pricing

Compare all plans or book a call to agree the first console area.

Questions about developer tools product design

How much does developer tools product design cost?

Developer tools product design with Gestures costs $2,250 per week, $4,000 for a two-week sprint or $7,500 per month. One console area, such as API keys, fits a weekly sprint. See pricing for every plan.

Do you need to understand our API before designing?

Yes. We read the API reference and the SDK quickstart, make real requests in a sandbox and ask an engineer to walk through the resources before any screen is drawn.

Do you design the CLI as well as the console?

Yes. We design command names, flags, help text and output so the CLI and the console use the same resource names and the same error structure.

Can you work inside our existing design system?

Yes. We extend your components with the patterns developer consoles need, such as copyable values, code blocks, environment banners and confirmation steps, and document each one.

How do you handle secrets in design files and prototypes?

Design files and prototypes use fake keys in the right format, never a real credential, and every screenshot from your sandbox is checked for secrets before it is shared.

Do you design for platform teams inside larger companies?

Yes. Internal developer platforms face the same questions about environments, access and destructive actions, with an internal audience instead of customers.

Do you design the usage and monitoring dashboards too?

Yes. Request volume, error rates, latency and rate limits are covered on our developer tools dashboard design page.

Send us the console screen your support team explains most

Share the console area that creates the most tickets and the matching part of your API reference. We can agree the first console area and whether Gestures is the right fit. For the wider service, see product design.