Case Study
Typid
Event Ticketing, Reimagined
How a failed finance app pivoted into a full-featured event ticketing platform in just 14 days — and powered real events within weeks.
Client
Typid
Year
2024
Timeline
14-day pivot + ongoing
Role
Full-Stack Design & Dev
Chapter 1
The Original Vision
Typid started life as a personal finance app built with Flutter. After launching to ~70 users, retention was poor and engagement dropped week over week. The finance space was crowded, and without significant differentiation, Typid was heading toward becoming another abandoned side project.
Chapter 2
The 14-Day Pivot
The turning point came at a church community event. Organizers were tracking attendance manually — paper lists, spreadsheets, cash-in-hand. Within 48 hours, the decision was made: pivot Typid into an event ticketing platform built for community events in the Philippines. The Flutter codebase was shelved. The new stack: Next.js 14 + Supabase.
Chapter 3
Building the Platform
Next.js App Router provided SSR and API routes in one framework. Supabase handled auth, database, and real-time subscriptions. The design system was built from scratch — dark theme, clean typography, mobile-first. Row Level Security ensured organizers could only see their own data. The QR system was built offline-first.
Chapter 4
Key Features
Multi-tier ticketing with up to 5 tiers per event. QR code check-in averaging under 3 seconds per attendee. Real-time organizer dashboard with sales, revenue, and attendance data. GCash and Maya payment integration — matching how the Philippine market actually pays.
Chapter 5
Real-World Validation
Himaya, a community church event, was the first real test. What used to take 3 people and 2 hours of manual work was handled by one person with a phone. Aisen Fest, a larger local festival, confirmed the platform held up at scale. Both events surfaced feedback that went straight into the roadmap.
Chapter 6
Results & Impact
A failing finance app became a working event platform in 14 days. Two real events powered within the first month. 100% QR check-in success rate validated the technical approach. Local payment integration removed the biggest barrier to ticket purchases.
Lessons Learned
Kill your darlings early — 70 users with poor retention is a signal, not a setback.
Build for a specific audience first. Community events in the Philippines, not 'events globally'.
Speed compounds. A 14-day MVP that ships beats a 6-month product that doesn't.
Local payment methods aren't a nice-to-have — they're the entire conversion funnel.