Build your own Postman.

# Build an original app inspired by Postman

You are an experienced product designer and full-stack engineer. Build a working, polished MVP from the brief below. Implement the core journeys end to end; a static mockup is not sufficient. Inspect the current environment, make sensible implementation decisions, and get started. Ask a question only if a missing answer genuinely blocks implementation.

Starting platform: Desktop. Explicit customized Product & audience and Tech stack requirements take precedence over this starting target.

## Product & audience
Build an original desktop HTTP workbench called Requestbench, inspired by Postman’s API client. A developer creates a request, chooses an environment, sends it from their own machine, inspects the response, and saves the result as a reusable collection. Keep requests local to the desktop rather than creating a public server-side proxy.

## Design
Use an original three-part workspace with a collection tree, tabbed request editor, and response panel. Provide query/header/body tabs, clearly marked secret fields, elapsed time, status, and a cancel control. Make request URL and active environment obvious before sending.

## Features
1. HTTP requests: configure method, HTTP(S) URL, query parameters, headers, JSON/text/form bodies, and bounded file upload. Display the resolved request before execution and never automatically send when a collection is opened.

2. Collections and environments: create folders, save requests, duplicate/reorder them, and switch validated environment variables. Detect missing variables and cycles; keep secret values separate from exportable collection files.

3. Execution: use a native HTTP client with timeouts, cancellation, bounded redirects/response size, and TLS verification enabled. Strip sensitive headers on cross-origin redirects and make localhost access an explicit desktop-user action.

4. Response inspection: show status, headers, timing, content type, and safe text/JSON previews. Treat HTML/SVG as untrusted text or sandboxed content, never executable app UI.

5. History and export: store redacted request history, replay only on explicit action, and import/export a documented collection format. Support structured status/JSON-path assertions without running arbitrary scripts.

## Tech stack
Use Rust with Tauri and a TypeScript interface, a maintained native HTTP client, SQLite, and OS-backed secret storage. Keep network execution in narrowly scoped native commands. Use the current Tauri capability model and explicitly restrict file access, IPC, navigation, and webview content.

## Data & behavior
Collection; Folder; SavedRequest {method, urlTemplate, headers, body}; Environment; Variable {secretRef}; Execution {resolvedUrl, state, timing, redactedRequest, responseMetadata}; Assertion; HistoryEntry. Keep secret values and response bodies out of default exports and diagnostic logs.

Acceptance checks and scope:
Test a local fixture API for verbs, auth headers, redirects, timeout, cancellation, binary/oversized responses, invalid TLS, missing variables, secret-free export, and hostile response HTML. Run the packaged desktop app. Exclude arbitrary pre-request scripts, cloud execution, collaboration, broad Postman format compatibility, and disabling certificate validation by default.

## Originality and assets
The named product is a reference for general workflows only. Use an original product name, visual identity, wording, layout, and assets. Do not copy proprietary code, branded logos, distinctive screens, private APIs, paid templates, or protected media. Use original or appropriately licensed sample data and assets. Build from this brief rather than scraping the reference service. Do not imply affiliation with the referenced company.

## Implementation quality
- Make every visible control work, with clear loading, success, empty, validation, and failure states. Remove controls for unimplemented features.
- Support the target platform and responsive or resizable layouts where appropriate. Use platform-appropriate accessibility semantics, labels, keyboard operation, visible focus, sufficient contrast, and reduced-motion preferences. Provide alternatives for drag-only interactions.
- Validate inputs at the relevant boundary. Treat imported or user-generated content as untrusted; render it safely. Confirm destructive actions or offer undo.
- Keep state changes reliable across navigation and reloads. Never silently lose edits. Handle persistence and network errors with an actionable message.
- Keep the scope realistic. Prioritize the complete primary journey. If a custom Features section differs from the baseline, update the data model, design, and acceptance checks to match it; explicit custom requirements take precedence over baseline assumptions.
- Provide realistic original sample content and a useful empty state. Keep sample data clearly separate from user-created data.

## Delivery and verification
1. Inspect the repository and outline the implementation in a few sentences.
2. Implement the app and connect its actual data flow. Continue until the primary journey works.
3. Run appropriate checks and test the acceptance cases above on the target platform. Verify responsive layouts and keyboard navigation when browser tools are available. For native projects, build with the available SDK and test an emulator or device when possible; report any missing native verification honestly. For games, verify the rules and gameplay loop, not only the menus.
4. Fix observed failures, then provide the runnable result, setup/run instructions, a brief explanation of what is implemented, and any specific configuration or verification limits.

This is a focused MVP. Do not add billing, AI services, or unrelated features unless explicitly requested in the brief. Start building now.