# Product

## Register

product

## Users

Developers and power users embedded in the ATProto ecosystem or new users who want to find more places to share links on the Atmosphere. They use Bluesky or Blacksky; collect links with Semble, Margin or Rabbithole; and/or bookmark with Kipclip, Sill, or Margin, and they want to post once and have it land everywhere. Their context: they've found a link worth sharing, they've decided to share it, and they're in the flow of that decision. The tool should clear the path, not perform.

## Product Purpose

Disperse posts a link or note to multiple ATProto-based destinations in one action. It removes the per-platform friction from cross-posting without becoming a dashboard. Success is measured by how quickly a user can go from intent to posted, ideally without thinking about the tool itself.

## Brand Personality

Sharp, minimal, confident.

Three-word personality: sharp, minimal, confident.

The tool knows exactly what it does and doesn't apologize for being narrow. No onboarding copy. No tooltips explaining things users already understand. The interface is matter-of-fact: the kind of tool a developer builds for themselves and then shares because it's genuinely useful.

## Anti-references

- Generic SaaS blue: no hero metrics, no identical card grids, no "boost your productivity" copy, no lavender backgrounds with cobalt CTAs.
- Social media dark mode: no Twitter/X darkness, no purple gradients, no glow effects, no neon accents.
- Bubbly consumer app: no excessive border-radius, no emoji-heavy UI, no playful brand voice that undercuts the tool's seriousness.
- Over-engineered dashboard: no sidebar navigation, no analytics panels, no data-density overload. This is not a content management system.
- Buffer's marketing layer (but take Buffer's interaction quality): clean form interactions, calm color use, clear hierarchy, not its marketing copy or growth-oriented framing.

## Design Principles

1. **The tool disappears into the task.** Every element present because the user needs it at that moment. Nothing decorative, nothing aspirational, nothing instructional for users who already know what they're doing.
2. **Restrained until it earns more.** Product register defaults. Accent color for primary action only: the Send button and selected states. Everything else: neutral.
3. **Consistency as affordance.** Same component vocabulary throughout. If a checkbox looks one way in Microblogs, it looks the same in Collections. Predictability is a feature.
4. **States that feel complete.** Every interactive state (hover, focus, active, disabled, loading, error, success) deliberately designed. No state that looks like an afterthought.
5. **Respect the user's context.** They've already decided to share. The UI acknowledges that and gets out of the way.

## Accessibility & Inclusion

WCAG 2.1 AA minimum. All interactive elements keyboard-navigable with visible focus states. `prefers-reduced-motion` respected. Semantic HTML first, no ARIA workarounds.