Mintix
Web3 ticketing platform — web app, organizer dashboard, iOS scanner, and on-chain minting.
I built the product end-to-end; the company was still pre-launch when I moved on — so this is a scope-and-craft story, not a traffic one.
Visit live siteWhat I owned
- ▹Marketing site and the core web application (Next.js).
- ▹Organizer dashboard for creating events, managing tickets, and viewing analytics.
- ▹React Native iOS app for scanning and validating tickets at the door.
- ▹Backend APIs, data model, and Redis caching layer.
- ▹On-chain minting pipeline turning each ticket into a Solana NFT (Metaplex).
- ▹Stripe payments wired end-to-end into the purchase → mint flow.
- ▹Seat mapping and selection (Seats.io).
Architecture
Conceptual — reconstructed from the stack, not the live repo.
Two flows carry the product: a standard web + mobile app over an API, and an on-chain pipeline that mints a ticket NFT once payment clears.
Hard problems
A card payment and an on-chain mint are two systems that can each fail on their own.
approachDecoupled purchase from mint — Stripe confirms first, then a background job handles minting, so a slow chain never blocks checkout.
outcomeBuyers get instant confirmation; minting settles reliably in the background.
Seat availability has to stay correct across web, mobile, and the organizer's seat map.
approachTreated Seats.io as the source of truth for layout and synced availability/holds into our own state.
outcomeNo double-booked seats across surfaces.
Two client platforms, one product — web and a React Native app.
approachKept business logic in the backend so both clients consumed the same API contracts.
outcomeFeatures shipped once and behaved the same everywhere.