Overview
ChefRise is a mobile cooking companion built around progress rather than isolated recipe browsing. It combines recipes, pantry awareness, guided cooking, AI assistance, social sharing, and skill progression in one application.
The current codebase is a clean-room Expo and React Native rebuild of an earlier frozen prototype, with a Supabase backend replacing the legacy Firebase implementation.
The problem
Recipe applications are often useful only at the moment of search. They rarely connect what a person already has, what they are learning, what they cooked before, and what they want to improve next.
ChefRise treats cooking as an ongoing practice with inventory, skills, missions, achievements, and shared activity.
Product approach
The application is organized into independent feature modules, including:
- recipe discovery and detailed guided cooking mode;
- AI-assisted recipe creation and chat;
- pantry tracking with camera-supported scanning flows;
- shopping lists;
- skill tracks and home missions;
- profiles, friends, achievements, and activity statistics;
- recipe sharing and leaderboard experiences;
- granular push notification preferences.
Architecture
The mobile application uses Expo and React Native with TypeScript. Supabase provides authentication, relational data, row-level security, Edge Functions, AI workflows, push registration and dispatch, account deletion operations, and subscription synchronization.
Native authentication supports Google and Sign in with Apple. Premium entitlement is validated through RevenueCat rather than being stored as a locally editable flag. Production builds use explicit environment checks and fail when required release configuration is missing.
My role
I rebuilt the mobile product from the reference prototype, reorganized it into feature modules, migrated the backend direction from Firebase to Supabase, implemented authentication and release gates, and integrated notifications, analytics, subscription validation, and production operations.
Current status
ChefRise is a private beta. The core mobile product and live-backend path are implemented, while external store credentials, production billing configuration, and final launch operations remain outside the public repository surface.