HumbleMar 2025—PresentSolo Founder & Indie Developer

Live music discovery for the obsessed

B2C/B2B live music discovery app—solo-built from zero to 1,000 monthly active users.

Team: Solo-Founder (Designer, Engineer, Sales & Support)
Stack: Next.js (web), Expo + React Native (mobile), shared design system in a monorepo
Audience: Live music fans, and artists who want to know their audience

Timeline: Mar 2025—Present
Scope: Monorepo across Next.js (web) and Expo / React Native (mobile), shared design system, B2C consumer app + B2B fan-CRM for artists.
Responsibility: Everything: product strategy, design system, frontend, backend, infra, marketing, sales, design, support.

Context

Why is live music discovery so flat? Ticketing apps optimize for conversion, social feeds for spectacle, listening services for streaming—none of them serve the audience that plans their year around festivals, follows specific artists across stages, and remembers sets from a decade ago. And on the other side of the stage, artists rarely know who's actually in their crowd—first-timer or hundredth show, even at a Coachella, the room doesn't tell them. Humble is organized around both sides: festival and concert review, performance archive, and a fan-to-artist relationship that flows both ways.

Approach

Solo-built monorepo across Next.js (web) and Expo / React Native (mobile), with a shared design system and a B2B fan-CRM layer for artists alongside the consumer app. Wearing every hat—product, design, engineering, marketing.

Impact

Web app launched April 2025; iOS and Android followed in August 2025. Scaled from 0 to 1,000 monthly active users, with hundreds of festivals and thousands of shows tracked across dozens of countries.

What does a festival feel like from inside the app?

Real-time interaction layered on fan-generated content—reviews, statuses, ratings, photos, video—all anchored to the festivals, sets, and shows happening right now. Afterward, they become a live archive of what people want to remember for the rest of their lives.

How do organizers actually build a set-time schedule?

A WYSIWYG editor that lets event organizers lay out stage schedules visually—drag a set, snap it to a time, publish. No spreadsheets, no back-and-forth with a designer. The grid is the schedule, and the schedule is what fans see in the app the moment it's saved. Any change—a time shift, a stage swap, a last-minute drop—pushes a real-time notification to every attendee following that show.

How do you decide who to see?

Swipe right to add an artist to your want-to-see list, swipe up to flag them as a must-see. The app auto-plays each artist's top track as you swipe, so you can preview and discover new acts in seconds. (Note: the video is muted by default—unmute to hear how motion and sound were designed together.)

How do you sweat the details when interaction is the product?

Parametric design—every spring, easing curve, gesture threshold, and return state exposed as a first-class variable instead of a hard-coded magic number. The surface can be micro-tuned and recomposed in place, which is the only way to keep an interaction-heavy product from drifting out of sync with itself.