Just Cook bro

Recipes, organized. Cooking, simplified.

Comment

Just Cook Bro

Inspiration

The inspiration behind Just Cook Bro came from two places: Ethan’s audience — and myself.

Ethan, as a cooking content creator, noticed something powerful. Many people love watching cooking videos on TikTok and YouTube Shorts, but they rarely cook for themselves. They are entertained, but they are not activated.

But the deeper inspiration was personal.

I realized I am exactly that kind of person. I can delay cooking even when I’m hungry. I look for shortcuts. One day, I was extremely hungry and had no convenient options. No delivery. No snacks. No excuses.

And in that moment, something clicked:

Just cook.

If I didn’t cook, I simply wouldn’t eat.

That realization shaped the philosophy of the app.

We can describe it mathematically:

$$ \text{Action} = \text{Hunger} - \text{Excuses} $$

When hunger outweighs excuses, action becomes inevitable.

The name Just Cook Bro is not just branding. It is a psychological trigger — a push against procrastination. It is accountability in two words.

We also observed:

$$ \text{Motivation} \approx \text{Simplicity} + \text{Accountability} $$

The entire product was designed around reducing friction and increasing activation.

What It Does

Just Cook Bro is an AI-powered cooking assistant designed to remove decision fatigue and make cooking immediate.

Users can:

  • Generate recipes from text prompts (e.g., “Spicy Pasta”)
  • Extract structured recipes from YouTube or blog links
  • Generate recipes from food images using AI vision
  • Enforce dietary restrictions (Vegan, Keto, Halal, etc.)
  • Detect allergens with critical confirmation alerts
  • Cook step-by-step using structured Cooking Mode with timers
  • Ask an AI chef for helpful or humorous guidance
  • Discover nearby stores for ingredients
  • Share and rate recipes in a community feed

The AI respects constraints formally:

$$ \text{Recipe Output} = f(\text{Input}, \text{Dietary Preferences}, \text{Allergies}) $$

This ensures personalization and safety.

The goal is not just recipe generation.

It is behavioral activation.

How We Built It

The project was built using:

  • Flutter (Android, iOS, Web)
  • Google Gemini (AI text + vision)
  • Supabase (Authentication, PostgreSQL, Storage)
  • RevenueCat (Freemium subscription management)
  • Shared Preferences (Offline caching)

Development initially began in React Native. Due to configuration friction and time pressure, we made a strategic shift to Flutter — which significantly accelerated execution.

The architecture follows a service-based separation:

$$ \text{UI} \rightarrow \text{Services} \rightarrow \text{External APIs} $$

Clear modular boundaries:

  • GeminiService → AI generation and validation
  • SupabaseService → Backend communication
  • RevenueCatService → Subscription verification
  • StorageService → Local persistence and caching

This structure improved scalability, maintainability, and debugging efficiency.

Challenges We Faced

1. Mid-Project Technology Switch

Switching frameworks required restructuring while maintaining delivery speed.

2. Time Constraints

The entire system was built in under one week while balancing personal responsibilities.

3. AI Reliability

Ensuring dietary enforcement and allergen validation required precise prompt engineering and structured validation checks.

4. API & Environment Configuration

Authentication syncing, environment variables, and subscription validation introduced multi-layer debugging complexity.

In AI-driven systems, failure can occur across multiple layers:

$$ \text{Failure} \in {\text{Frontend}, \text{Backend}, \text{AI Output}, \text{Network}} $$

Each layer required systematic isolation and testing.

Accomplishments

We are proud that we:

  • Built a fully functional AI-powered cooking assistant in under one week
  • Implemented strict allergy confirmation dialogs
  • Designed a synchronized Cooking Mode with timers
  • Integrated a working freemium subscription model
  • Maintained a clean, scalable architecture

Most importantly, we transformed a behavioral problem into a technical system.

What We Learned

This project reinforced a major insight:

Deep user understanding matters more than knowing every technology.

Clear audience definition shaped every design decision.

We learned:

  • Depth in one framework outperforms shallow knowledge across many
  • Prompt engineering determines AI reliability
  • Reducing friction increases activation

We modeled engagement as:

$$ \text{User Engagement} \propto \frac{\text{Enjoyment}}{\text{Friction}} $$

Lower friction leads to higher sustained use.

What’s Next for Just Cook Bro

The next evolution transforms cooking from a solo task into a synchronized social experience.

1. Live Cooking Sessions (Synchronized Mode)

Users will be able to cook together in real time.

When someone starts a recipe:

  • Followers receive a notification
  • The recipe and start time are displayed
  • Users can join a live session

The livestream will synchronize with structured recipe steps.

If the host advances to:

Step 3 — Sauté onions (5 minutes)

Participants see:

  • The same instruction highlighted
  • The same timer activated
  • Real-time stage progression

Formally:

$$ \text{Live Cooking State} = f(\text{Video Stream}, \text{Recipe Step Index}) $$

This creates alignment between watching and executing.

Cooking becomes interactive rather than passive.

2. Stage-Based Notifications

Users can subscribe to creators.

Notifications may include:

  • Session scheduled
  • Session starting now
  • Stage transitions (prep, cook, bake, plate)

Modeled as:

$$ \text{Notification Trigger} = g(\text{User Subscription}, \text{Cooking Stage}) $$

This builds anticipation and accountability.

3. Voice-Only Cooking Stream (Low-Data Mode)

To ensure accessibility, a voice-only stream option will be introduced.

Features:

  • Audio guidance without video
  • Synchronized recipe steps
  • Reduced bandwidth usage

Conceptually:

$$ \text{Engagement} = \text{Guidance} + \text{Synchronization} $$

Video enhances immersion. Voice ensures inclusivity.

Voice streaming will be part of the premium tier to support data-conscious users.

4. Private Cooking Communities

Users will be able to create structured communities:

  • Family groups
  • Cultural cooking circles
  • Creator fan groups
  • Friend communities

Within each space, members can:

  • Share custom recipe folders
  • Upload modified versions
  • Discuss ingredient substitutions
  • Debate techniques
  • Share final dish photos

Community knowledge grows cumulatively:

$$ \text{Community Knowledge} = \sum (\text{Shared Recipes} + \text{Modifications} + \text{Discussions}) $$

Cooking becomes shared memory.

5. Collaborative Recipe Versioning

Recipes within communities can evolve.

For example:

$$ \text{Recipe}{v2} = \text{Recipe}{v1} + \text{Community Modifications} $$

This enables:

  • Family adaptations
  • Cultural variations
  • Iterative improvements

Cooking becomes dynamic rather than static.

Long-Term Vision

We aim to redefine cooking as:

$$ \text{Cooking} = \text{Skill} + \text{Social Energy} $$

And ultimately:

$$ \text{Cooking Adoption Rate} \propto \text{Enjoyment} \times \text{Ease of Use} \times \text{Community} $$

Just Cook Bro is not just a recipe app.

It is an activation engine.

It turns hunger into action. It turns hesitation into execution. And sometimes, all someone needs is a simple reminder:

Just cook.

Built With

Share this project:

Updates