Showrunner

Inspiration

Gabby Beckford is right: many women know the life they want, but hesitate to fully step into it. They consume inspiring content, envision transformation, and plan future versions of themselves — yet action often feels uncertain.

We wanted to build something that shifts the role from observer to creator.

Stop watching the show. Start running it.

What it does

Showrunner turns a goal into a structured season.

Each goal becomes a season
Each week becomes an episode
Each day becomes a scene

AI generates the season arc and daily tasks with minimum, mid, and maximum effort levels. Users log progress, add photos, and receive daily and weekly recaps. When the goal is complete, the app generates a final “film” built from their journey — fully shareable.

The metaphor is cinematic. The structure is practical.

How we built it

We built Showrunner in Flutter using a modular, clean architecture approach.

The backend runs on Firebase (Auth, Firestore, Functions), with Gemini handling structured AI generation through enforced JSON schemas.

We implemented a dynamic runtime theming engine so the entire interface adapts to the selected genre.

RevenueCat manages subscriptions and entitlements, aligned with goal duration (monthly, yearly, 2-month, and 3-month plans).

Challenges we ran into

One of the biggest challenges was balancing metaphor and practicality. We wanted the cinematic framing to feel immersive without turning into a gimmick.

Styling was another major challenge. Each genre required its own visual system, category variations, and poster logic while keeping the architecture maintainable.

Optimizing final film generation — especially compiling user media into a recap without slowing performance — required careful design and iteration.

Accomplishments that we're proud of

We’re proud of the immersion and cohesive look and feel across genres.

More importantly, we’re proud of building a system that can turn a loosely defined dream into a structured, visible journey.

What we learned

We learned how to scope and ship a focused MVP under tight constraints. That meant prioritizing core mechanics, avoiding feature creep, and balancing polish with delivery.