# Product

## Register

product

## Users

Developers, technical power users, and small teams who need instant, secure file sharing without infrastructure. They're comfortable with a CLI, time-constrained, and want a tool that disappears into their workflow. Typical scenarios: sharing a build folder with a remote colleague, giving a client temporary access to design assets, or syncing files across locations via a browser-accessible link.

## Product Purpose

folderex makes any local folder publicly accessible via HTTPS with one command. It exists to eliminate the gap between "I have files on my machine" and "anyone with a link can access them securely." Success is: zero config, instant public URL, basic auth protection, and a file browser UI sharp enough that recipients don't think twice about it.

## Brand Personality

Technical, precise, powerful. The interface should feel like a well-engineered tool: fast, confident, no wasted space. It doesn't try to be fun or playful - it earns trust through clarity and competence. The kind of tool that makes you feel like a pro when you use it.

## Anti-references

- Generic OS file managers (Windows Explorer, default FTP clients) - bland, utilitarian, no craft
- Cheap file-share UIs (WeTransfer clones, free hosting panels) - feel disposable, untrustworthy, ad-laden

## Design Principles

- **Instant comprehension.** Every element explains itself. No hunting, no guessing.
- **Speed is the feature.** Perceived and actual performance. The UI should feel like it responds before you finish clicking.
- **Expert confidence.** The interface assumes competence. Dense information, no hand-holding, no unnecessary confirmations.
- **Zero-friction sharing.** The recipient's experience (the file browser) must be as frictionless as the sharer's (the CLI).
- **Opinionated, not neutral.** Make decisions. Default to the right thing. Don't present options when there's an obvious answer.

## Accessibility & Inclusion

WCAG 2.1 AA compliance. Contrast ratios enforced (4.5:1 body text, 3:1 large text/UI components). Full keyboard navigation. Screen reader compatibility for file listings and actions. Reduced motion support for any animations.
