Inspiration
The inspiration for MumMoney came from recognizing a fundamental gap in the financial app market: most tools assume users have time, financial knowledge, and motivation. But for busy mums juggling work, family, and countless daily responsibilities, these assumptions fall apart.
I saw three critical barriers that traditional finance apps weren't addressing:
- Time scarcity: Mums don't have hours to spend on complex financial dashboards or lengthy educational courses
- Information overload: Financial jargon and overwhelming options create anxiety rather than confidence
- Lack of trust: Generic apps feel impersonal and don't connect with the emotional reality of managing money as a parent
The RevenueCat Shipyard Creator Contest brief resonated deeply because it highlighted the power of creator-led products. I realized that financial guidance works best when it comes from someone you trust—someone who understands your daily reality. This isn't just about money management; it's about building confidence through small, achievable wins that fit into a busy life.
The core philosophy became: "Small actions done consistently create real financial change." Instead of trying to turn users into finance experts, MumMoney helps them feel in control again—one 2-5 minute daily action at a time.
What it does
MumMoney is a creator-led mobile app that helps busy mums take control of their money through small daily wins. The app delivers:
- Daily Money Wins: One clear, actionable item per day that takes 2-5 minutes to complete
- Save Money Section: Practical tips for shopping, food, and home expenses with real savings calculations
- Grow Money Section: Beginner-friendly investing lessons that build confidence without overwhelming users
- Creator Content: Exclusive videos, stories, and weekly guidance from a trusted creator
- Progress Tracking: Visual progress showing estimated savings and learning milestones
- Personalized Experience: Onboarding that adapts to user goals (save money vs. grow money) and time commitment
The app is designed around the principle that financial apps don't have to be overwhelming—they can be calm, achievable, and genuinely helpful. Every screen answers one question: "What should I do right now?"
How we built it
Tech Stack
- Framework: React Native with Expo (~54.0) and Expo Router for file-based routing
- Language: TypeScript for type safety
- State Management: Zustand for global state, React Query for data fetching
- UI Libraries:
@gorhom/bottom-sheetfor smooth bottom sheet interactionslottie-react-nativefor delightful animationsreact-native-reanimatedfor performant animations
- Monetization: RevenueCat SDK (
react-native-purchasesv9.7.6) withreact-native-purchases-uifor the paywall
Architecture
I organized the codebase into clear layers:
src/
├── features/ # Feature modules (home, save-money, grow-money, etc.)
├── stores/ # Zustand state stores
├── services/ # Business logic (PurchaseService, etc.)
├── components/ # Shared UI components
├── contexts/ # React contexts (theme, bottom-sheet)
└── types/ # TypeScript type definitions
Each feature is self-contained with its own components, screens, and types. This made it easy to build incrementally and maintain clear boundaries.
RevenueCat Implementation
The subscription flow is handled through a dedicated PurchaseService class that:
- Initializes RevenueCat on app launch (in the splash screen)
- Fetches customer info to check subscription status
- Retrieves offerings to display available packages
- Handles purchases through the RevenueCat UI component
- Manages lifetime purchases by checking both subscription and non-subscription transactions
The paywall uses RevenueCat's pre-built UI component, which saved significant development time while ensuring a polished, conversion-optimized experience.
Key Features Built
- Onboarding flow with goal personalization (save money vs. grow money, time commitment)
- Daily money wins system that surfaces one actionable item per day
- Save Money section with practical tips for shopping, food, and home expenses
- Grow Money section with beginner-friendly investing lessons
- Creator content section (structure ready for video/story integration)
- Progress tracking with estimated savings calculations
- Dark mode support throughout
- Subscription management with clear free vs. premium differentiation
Challenges we ran into
1. Time Constraints
Building a full-featured app for a hackathon meant making tough decisions about scope. I had to balance feature completeness with quality. The solution was ruthless prioritization—focusing on the core user journey (onboarding → daily action → progress) and ensuring those flows were polished, even if some features remained basic.
2. RevenueCat Configuration
Getting RevenueCat properly configured with test products required understanding the relationship between App Store Connect/Google Play Console products and RevenueCat offerings. The initial setup took longer than expected, but once configured, the SDK handled everything elegantly. I learned the importance of using platform-specific API keys (not just the Test Store) for proper testing.
3. State Management Complexity
Managing subscription status across the app while keeping the UI responsive required careful state design. I ended up centralizing subscription state in a Zustand store that gets initialized early in the app lifecycle, ensuring all screens have access to the current subscription status.
4. Content Structure
Designing a content system that could scale (from JSON files to potentially a CMS) while keeping the MVP simple was a challenge. I structured the data files (daily-money-wins.json, save-money-tips.json, etc.) to be easily replaceable with API calls later, without changing the consuming components.
5. User Experience Balance
The biggest challenge was ensuring the app felt supportive, not demanding. Every interaction had to respect the user's limited time and potential anxiety around money. This meant:
- Keeping copy warm and encouraging
- Making progress visible but not pressure-inducing
- Ensuring the paywall felt like value, not a barrier
6. Platform-Specific Builds
Getting Android builds working with Expo's new architecture required careful configuration of app.config.js and understanding Expo's prebuild process. The edge-to-edge Android configuration and proper package naming were crucial for a production-ready feel.
Accomplishments that we're proud of
Complete RevenueCat Integration: Successfully implemented a production-ready subscription system with lifetime purchases, proper customer info handling, and a polished paywall experience using RevenueCat's UI components.
Thoughtful User Experience: Created an app that respects users' limited time and potential financial anxiety. Every screen is designed to answer "What should I do right now?" without overwhelming users.
Scalable Architecture: Built a feature-based architecture that's maintainable and ready to grow. The separation of concerns (features, stores, services, components) makes it easy to add new functionality without technical debt.
Full MVP in Limited Time: Delivered a complete, functional app with onboarding, daily actions, savings tips, investing lessons, creator content structure, and subscription management—all polished and ready for testing.
Production-Ready Builds: Successfully configured Android builds with Expo's new architecture, proper edge-to-edge support, and all necessary configurations for TestFlight/Google Play testing.
Type Safety Throughout: Maintained full TypeScript coverage across the codebase, making the app more maintainable and reducing runtime errors.
What we learned
RevenueCat Integration
This was my first production implementation of RevenueCat, and I learned how powerful it is for managing subscriptions. The SDK's simplicity—especially react-native-purchases-ui for the paywall—meant I could focus on the user experience rather than wrestling with platform-specific purchase flows. I implemented a lifetime purchase model alongside subscriptions, which required understanding RevenueCat's offerings system and how to check purchase status across different product types.
React Native Architecture
I chose Expo with the new architecture enabled, which gave me access to modern React Native features while maintaining fast iteration. The feature-based architecture I implemented (separating concerns into features/, stores/, services/, and components/) made the codebase maintainable even as it grew. Using Zustand for state management proved perfect for this scale—lightweight, TypeScript-friendly, and easy to reason about.
State Management Patterns
I learned to balance local component state, Zustand stores for global app state, and React Query for server-side data (even though most content is currently local JSON). This separation of concerns made testing and debugging much easier.
User Experience Design
Perhaps the most important learning was understanding how to design for cognitive load. Every screen had to answer one question: "What should I do right now?" This meant ruthless prioritization—removing features that didn't directly serve the core value proposition of daily, achievable money wins.
Platform Integration
I gained deeper understanding of how App Store Connect and Google Play Console products integrate with RevenueCat offerings, and the importance of proper API key configuration for testing and production environments.
What's next for MumMoney
Smarter Personalization: Implement AI-driven content recommendations based on user behavior, goals, and progress. Personalize daily money wins to match individual spending patterns and interests.
Savings Challenges: Add gamified savings challenges that encourage users to save for specific goals (holidays, emergencies, investments) with progress tracking and community support.
Country-Specific Content: Expand the app to support different markets with localized savings tips, currency-specific calculations, and region-appropriate financial guidance.
Brand Partnerships: Integrate with retailers and service providers to offer exclusive deals and cashback opportunities, creating additional value for premium subscribers.
Community-Driven Motivation: Build community features that allow users to share wins, tips, and encouragement while maintaining privacy and safety.
Advanced Analytics: Provide deeper insights into savings patterns, spending habits, and progress toward financial goals with beautiful, easy-to-understand visualizations.
Creator Content Expansion: Enhance the creator content section with live updates, interactive Q&As, and more dynamic content delivery.
Integration with Financial Tools: Connect with bank APIs (with user permission) to provide real-time savings tracking and automated money win suggestions based on actual spending.
The app is built with the future in mind, ready to grow from MVP to a full product that helps busy mums take control of their financial future—one small win at a time.