Documentation Index
Fetch the complete documentation index at: https://handbook.polar.sh/llms.txt
Use this file to discover all available pages before exploring further.
The Polar product should feel like a precision instrument. Not software that processes billing. An instrument that measures, captures, and converts with exactness.
Data is the design
In a billing product, numbers are the primary content. The design system exists to make data legible, scannable, and trustworthy at a glance. Typography, spacing, and hierarchy serve the number, not the other way around.
Density with clarity
Applied AI founders need to see a lot of information quickly. The product doesn’t hide complexity behind progressive disclosure and empty states. It presents information densely, precisely, and trusts the user to navigate it. Clarity is achieved through hierarchy, not simplicity.
Zero polish debt
Every screen, every state, every edge case is designed with the same precision as the primary flow. Empty states are not afterthoughts. Error states are not apologies. Every moment a founder encounters the product is a moment they are forming a judgment about Polar’s precision. We treat every state as primary.
Speed as a design value
The product should feel fast in every sense. Fast to load, fast to understand, fast to act on. Latency is a design failure. Cognitive load is a design failure. Every additional second a founder spends understanding the product is a second they’re not building.
The invoice as a design artifact
The invoice is the most tangible expression of Polar in the world. It lands in a founder’s customer’s inbox with the Polar system behind it. It should be the most precisely designed document in that inbox. Typographically exact, informationally clear, unmistakably considered.
