[ LIVE_EVENTS_&_NIGHTLIFE ]

Event Ticketing Platform (Mobile + Web)

2026Marketplaces & Consumer AppsIn-depth

What it is

A full ticketing business: discovery, checkout, QR entry and a social layer.

Client work is shown without identifying imagery

[ THE_PROBLEM ]

Why this existed

Selling through a third-party ticketing platform means giving away the booking fee, the customer relationship and the data — and inheriting their checkout, their branding and their limits.

[ WHAT_WE_BUILT ]

What we built

A React Native application shipping to iOS, Android and web from one codebase. Phone-OTP authentication through an Indian SMS provider with SMS or WhatsApp delivery. Event discovery with categories, stories-style event reels, artist pages, a wishlist, merch and a messaging surface with user profiles, blocking and a ban state. Checkout runs through Razorpay payment links with server-side webhook verification, multi-attendee names and add-on options; tickets are issued as QR codes and downloadable PDFs. Vendor posts, moderation and a desktop-responsive layout round it out — the whole thing was subsequently migrated off its original backend onto a reactive one, with the mobile route parity preserved through the move.

One React Native codebase shipping to iOS, Android and web
Phone-OTP authentication with SMS or WhatsApp delivery
Event discovery with categories, stories-style reels and artist pages
Wishlist, merch and messaging with profiles, blocking and ban states
Checkout via payment links with server-side webhook verification
Multi-attendee names and add-on options at checkout
QR-code tickets with downloadable PDFs
Vendor posts and moderation
Desktop-responsive layout from the same codebase
Backend migrated to a reactive platform with mobile route parity preserved

[ HOW_IT_IS_USED ]

How a company uses it

An events, venue or promoter business owns its ticketing rather than renting it — keeping the customer relationship, the data and the booking fee.

Built with

ExpoReact NativeConvexBetter AuthMSG91Razorpay

[ COMMON_QUESTIONS ]

Questions clients ask

Why phone OTP instead of email sign-up?

Because of who the users are. For events in this market the phone number is the identity people actually have and check, and it doubles as the channel for ticket delivery and day-of updates. Email sign-up would have suppressed conversion.

Why verify payments server-side via webhook?

Because a client can be manipulated. If the app tells your backend a payment succeeded, someone will eventually make it say that without paying. Webhook verification against the provider is the only trustworthy confirmation.

You migrated the backend mid-life — how disruptive was that?

It was a deliberate parallel rebuild with route parity preserved, so the mobile surface stayed stable while the data layer changed underneath. That is the manageable way to do it. Migrating in place, screen by screen, is where these projects go wrong.

[ RELATED_WORK ]