Build your own Bitly.

# Build an original app inspired by Bitly

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: Web. Explicit customized Product & audience and Tech stack requirements take precedence over this starting target.

## Product & audience
Build an original short-link manager called Linknest, inspired by Bitly. A signed-in user creates a short URL for a validated destination, shares it, updates or disables it, and views aggregate visit counts. Start with one configured short-link domain and a small authenticated publisher group.

## Design
Create an original link dashboard, a concise creation form, destination preview, and aggregate activity chart. Clearly distinguish active, expired, disabled, and missing aliases. Make the short domain and eventual destination visible before copying a link.

## Features
1. Link creation: validate HTTP(S) destinations, generate collision-resistant aliases, optionally accept a validated custom alias, and reserve application routes. Keep alias creation atomic under concurrent requests.

2. Redirects: resolve active links with a documented redirect status, enforce expiration and disablement server-side, prevent links that loop back into the shortener, and show honest missing/expired pages.

3. Management: search and tag owned links, edit permitted destinations, disable/restore links, and show a destination history. Check ownership on every mutation and export.

4. Counts and reports: record bounded aggregate redirect activity by link/day and coarse referrer category, with a documented bot/duplicate policy. Label counts as requests or estimated visits accurately rather than claiming unique people.

5. Sharing and abuse controls: copy the URL, generate a QR code for that URL, export owned-link metadata as CSV, rate-limit creation/redirect abuse, and let administrators disable reported destinations.

## Tech stack
Use a Go redirect/API service, PostgreSQL, and a TypeScript dashboard. Index unique aliases and aggregate counts asynchronously without preventing redirects. Avoid server-side destination fetching; if previews are later fetched, add a dedicated SSRF-safe fetcher. Set a clear event-retention policy.

## Data & behavior
User; Link {ownerId, alias, destination, expiresAt, disabledAt}; Tag; LinkTag; DestinationRevision; ClickAggregate {linkId, date, referrerClass, count}; AbuseReport; AdminAction. Never store full query strings, full referrer URLs, or persistent visitor fingerprints by default.

Acceptance checks and scope:
Test alias collisions, reserved paths, invalid schemes, Unicode/encoded destinations, self-redirect loops, expiry boundaries, disabled links, permission checks, and aggregates after repeated redirects. Exclude arbitrary custom-domain provisioning, guaranteed unique-user counts, location fingerprinting, and unconfigured malware scanning claims.

## 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.