Web Storefront + Desktop App Architecture
Web Storefront + Desktop App Architecture
Architecture for a web storefront that sells a desktop application — covering the full user journey from discovery to purchase, download, license activation, and offline usage.
Tech Stack
| Layer | Technology | Purpose |
|---|---|---|
| Auth | Clerk | User accounts and authentication |
| Payments | LemonSqueezy | Checkout, licensing, and subscription management |
| Database | Supabase | User data, orders, licenses, analytics |
| Website | Next.js (Vercel) | Landing pages, dashboard, download page |
| Desktop App | Electron | Offline-capable desktop application |
Full User Journey
Data Flow Summary
Step-by-Step Walkthrough
| Step | Action | What Happens |
|---|---|---|
| 1 | User discovers the website | Browses features, pricing, and media on landing pages |
| 2 | User creates an account | Clerk authenticates, webhook syncs user to Supabase |
| 3 | User buys the app | LemonSqueezy checkout ($99 lifetime), webhooks create order + license in Supabase |
| 4 | User views dashboard | Sees license key, status, devices, and order history |
| 5 | User downloads the app | Gets Windows .exe or macOS .dmg from the downloads page |
| 6 | User activates the license | Enters license key in the desktop app, validates via LemonSqueezy API (up to 3 devices) |
| 7 | User uses the app offline | Full functionality without internet — no subscription required |
| 8 | User manages devices | Deactivate/reactivate devices from the dashboard anytime |
| 9 | Admin views analytics | All user, order, license, and download data aggregated in Supabase |