No Apologies Crew

Inspiration

This project is inspired by the blank issues that many entrepreneurs face — the gap between "I want to build something" and actually shipping it. Home cooking is one of those universal problems everyone talks about but few solve well: families struggle with meal planning, budget tracking, grocery waste, and staying motivated to cook consistently. We took this as a chance to pour every last drop of effort and opportunity into building GoMums — a mobile app that turns home cooking from a daily chore into a connected, goal-driven experience.

What It Does

GoMums is a meal planning and food budgeting app for families and home cooks. It brings together features that are usually scattered across multiple apps:

Weekly Meal Planning — Plan breakfast, lunch, and dinner for every day of the week
Smart Shopping Lists — Auto-generate grocery lists from your meal plan
Budget Scoring — Track food spending and get a weekly budget score with actionable insights
Cooking Journal — Log meals, purchases, mood, and energy to build cooking habits
Missions & Challenges — Gamified goals that reward consistency and creativity
Recipe Discovery — Browse, save, and share recipes with the community
Food Contests & Streams — Premium users compete in cook-offs, earn prestige badges, and watch live cooking events

How We Built It

Frontend: Lit 3 web components + TypeScript + Tailwind CSS 4, built with Vite 7
Backend: Python FastAPI with PostgreSQL (20+ tables, 50+ REST endpoints)
Mobile: Progressive Web App (PWA) wrapped in a Trusted Web Activity (TWA) for Android distribution on Google Play
Hosting: Netlify (frontend) + custom server (backend API)
AI: AI-powered recipe suggestions and meal plan optimization
Monetization: RevenueCat for cross-platform subscription billing

Challenges We Ran Into

Common team opinion issues — aligning on product direction when everyone has strong ideas
Timezone bugs — UTC date shifts causing meals to appear on the wrong day across different regions
Navigation complexity — building a dual routing system (event-based + History API) that works for both PWA and TWA
Keeping the free tier valuable without giving everything away — finding the right line between utility and premium

Accomplishments That We're Proud Of

The knowledge we have built — because our drive to never apologize but instead recreate decisions is something we are proud of. We shipped a fully functional app to Google Play, connected a real backend with 50+ API endpoints, and built a monetization model that doesn't paywall the features people actually need. The budget scoring system, the gamified missions, and the contest-driven premium tier all came from iterating fast and not being afraid to throw things out and rebuild.

What We Learned

A lot. Specifically:

Separate utility from entertainment in monetization — people hate paying for needs, but gladly pay for wants
PWA + TWA is a viable path to Google Play without writing native Android code
Lit web components can power a full mobile app experience with Shadow DOM, reactive stores, and fast rendering
Ship early, fix in production — timezone bugs, navigation edge cases, and API mismatches all surfaced only after real usage
Gamification works — missions, badges, and contests drive engagement far more than feature checklists