Product & Website Design for Developer Tools

Gestures Studio is a developer tools design agency. We design the path from your homepage to a developer's first successful API call, and the dashboards, keys, logs and usage screens they return to after that.

Developers decide in the first hour whether a tool deserves a place in their stack. We shorten that hour, and we make the errors they meet along the way explain themselves.

We design and run a developer integration of our own

Gestures runs a public remote MCP server that ChatGPT, Claude and other compatible AI apps can connect to. It answers questions about the studio's services, current pricing, published articles and introductory-call availability.

We designed its setup page the way we design for developer tools clients. The server URL comes first, with a copy button and a selectable fallback. The connection details follow in one line: no authentication, Streamable HTTP, no API key. Setup steps are written separately for each AI app, and the page says plainly that public tools only read information while creating a booking needs a private authorized connection. The site also publishes an llms.txt content guide built from the same page inventory as the sitemap.

Ragip Diler, who leads Gestures, also designed MCP, security and analytics workflows for AI products as Senior Product Designer at Venice, an independent design studio for AI and venture-backed companies.

Where developers drop off between the homepage and the first API call

Most developer tools lose people before the first successful request, at a step the product team rarely watches. We map each step from the homepage to a working call, find where developers stall and redesign that step first.

The API experience decides adoption. In the 2025 Stack Overflow Developer Survey, developers ranked an easy-to-use API first and a robust and complete API second among the reasons they become fans of a tech tool. The same survey ranked security or privacy concerns, prohibitive pricing and the availability of better alternatives as the top three reasons developers lose interest, with poor usability fourth.

Steps from the homepage to the first API call and how each is designed
StepWhere developers stallWhat we design
HomepageThey cannot tell what the API does without reading marketing copyA real code sample above the fold, with links to the quickstart and the API reference
Sign-upA sales form or long profile stands between them and a keySign-up with GitHub or Google and only the questions the product needs now
First keyThey do not know which key, scope or environment to useA test key created on arrival, clear test and live labels and a show-once secret with a copy button
Install and first callThe snippet does not match their language or frameworkLanguage tabs, snippets prefilled with their test key and a success state when the first request arrives
First errorThe response says what failed but not how to fix itError messages that follow the anatomy below, linked to the matching log entry
Going liveLimits, billing and production keys arrive as a surpriseA go-live checklist with live keys, webhook setup, usage limits and the plan that fits
Developer settings page with an embeddable payment button code sample and a Copy Code button.
A developer settings page with copyable embed code, a Gestures interface study on Dribbble.

An error message developers can act on

A good developer tool error answers four questions in order: what happened, why, how to fix it and where to read more. We design error messages, log entries and dashboard alerts on this structure, so the same failure reads the same way in the API response, the console and the CLI.

The four parts of an actionable error message
PartQuestion it answersExample
What happenedWhich request failed and with which code?Request rejected: invalid_api_key
WhyWhat in the request caused it?The key starts with sk_live but the request was sent to the test environment
How to fix itWhat is the next action?Use a key that starts with sk_test, or send the request to the live endpoint
Read moreWhere is the full explanation?A link to the error reference page and the request ID to search in logs

The examples are illustrative. Your engineers own the error codes and their exact wording, and we design the structure, the tone and where each part appears.

The screens developers come back to every week

After the first call, developers return to four places: keys, logs, webhooks and usage. Each one is used during an incident or a deploy, so we design for speed, copyable values and a clear path back to the docs.

  • Keys and tokens: scopes chosen at creation, rotation without downtime, revocation with a warning about live traffic and the date each key was last used.
  • Logs and request inspector: filters by status, endpoint and time, full request and response bodies, copyable request IDs and the documentation link for every error code.
  • Webhooks: event selection, signing secrets, delivery history, retries and a button that sends a test event.
  • Usage and billing: usage against limits, spend alerts before a quota is reached and the plan change that removes a limit.
  • Teams and access: roles, SSO, two-factor settings and an audit log for companies that adopt the tool across teams.

Our dashboard UX audit shows how we check the tables, filters, states and actions these screens depend on. For new products, our AI-native product development service takes a focused prototype to a working version, and our product design service covers products already in use.

Security settings with two-factor authentication, login alerts and session timeout controls.
Two-factor authentication and security preferences, a Gestures interface study on Dribbble.

What a developer tools homepage needs above the fold

A developer tools homepage works when a developer can judge fit in one screen: what the tool does, how it looks in code and how to try it. Everything else on the site supports a second visit from the engineering lead who approves the purchase.

Above the fold, we place a one-sentence description of the job the tool does, a short code sample in a popular language, a primary action to get a test key and a secondary link to the docs. Below it, pages answer the engineering lead: integrations and SDKs, security and compliance, usage-based pricing with a worked cost example, a changelog that shows the product is maintained and a contact path for larger plans.

Your team owns technical claims and benchmarks, and the design makes each one easy to verify. Our guide to pricing page design covers how to explain usage-based plans. We design and build these sites through our website design service.

Developer-focused website hero with API docs and sandbox key buttons above an SDK code example.
A developer-first website hero with the code sample above the fold, a Gestures interface study on Dribbble.

Start with the quickstart, then the dashboard

Most chosen

Monthly partnership

$7,500$10,500USD / month

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

For a larger product or website effort that continues across API versions and feature releases. Set the current focus and review what should receive 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 flow, such as the quickstart, API key management or the pricing page. Agree the deliverables and dependencies before starting. The weekly rate describes the engagement period; completion timing depends on the scope.

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

Most developer tools teams start with a weekly sprint on the path to the first API call, because it affects every new developer. A monthly partnership then covers keys, logs, usage and the website across API versions.

Your engineers review technical accuracy at each step, and the handoff includes annotated designs and documented error, empty and loading states.

Compare all plans or book a call to discuss the first scope.

Questions from developer tools teams

Do you have developer tools experience?

Yes. Gestures designed and runs its own public MCP server and setup page, and Ragip Diler, who leads Gestures, designed MCP, security and analytics workflows for AI products at Venice. He was also Head of Design at Notch, a company that helps businesses hire software engineers.

Will designers understand our API?

We run your quickstart, read your API reference and use your SDK or CLI before designing anything. Screens are then built around the real errors, limits and permissions your API returns, and your engineers review them for accuracy.

Do you design documentation sites?

Yes. We design docs navigation, search, guide and reference page templates and code sample tabs, and we link product screens to the right docs page. Your team writes the technical content and chooses the docs platform.

Can you design CLI output and error text?

Yes. We apply the same error structure to API responses, CLI output and dashboard messages, so a failure reads the same everywhere. Your engineers implement the final strings.

What does a quickstart sprint cost?

A weekly sprint costs $2,250 per week, and a monthly partnership costs $7,500 per month. The pricing page lists every plan.

Send us your quickstart

Send the link to your quickstart or docs and tell us where new developers stop. On the call, we can walk through it together and agree which step to redesign first. You can also write to [email protected].