Live
Dynamic QR
Print one QR code and change what it points to forever — with scheduled content rotation, analytics, and edge redirects that stay fast everywhere.
- Role
- Founder · full-stack
- Timeline
- [n] weeks
- Year
- [2024]
- Stack
- Next.js, TypeScript, PostgreSQL
(01)The problem
Printed QR codes are permanent; the content behind them shouldn't be.
Restaurants, events and retailers want different destinations by time of day or date — menus at lunch, events at night.
(02)My role
- Built the rule engine for scheduled rotation (time windows, date ranges, time zones).
- Implemented low-latency redirects with cached rule resolution and privacy-friendly scan analytics.
- Shipped billing, team workspaces and branded QR design export.
(03)Architecture
Each code resolves through a redirect endpoint that evaluates its schedule rules in the visitor's time window. Rules are cached at the edge and invalidated on change, keeping redirects fast while edits apply within seconds.
- 01
Scan
Short URL hit
- 02
Resolve
Cached rule set, time-zone aware
- 03
Redirect
302 to the active destination
- 04
Record
Async, privacy-friendly analytics
Resolve at the edge
Scans happen on mobile networks; shaving the round-trip matters more than anything else in the product.
Analytics off the hot path
Scan events are queued and written asynchronously so analytics never slow down a redirect.
(04)Tech
App
- Next.js
- TypeScript
- Tailwind CSS
Data
- PostgreSQL
- Redis
Platform
- Edge functions
- Stripe
(05)Outcome
[Customers, scans served, or a business result.]
- ms median redirect
- <50
- scans served
- 100k+
- hour rotation windows
- 24/7
Next case study
Capital Mind
A personal ledger for investments & insurance