The StellaEats N-of-1 Experimentation Prototype project aims to develop a functional prototype for personalized dietary experiments, allowing users to conduct simple experiments such as diet swaps, eliminations, and reintroductions. The project will be executed using FlutterFlow for the frontend and a mock Firebase backend for data persistence. The primary goal is to translate existing designs into a working MVP that enables users to create experiments from templates, log daily outcomes, and visualize results through a causal map with tolerance badges. This project provides an opportunity for learners to apply their classroom knowledge in a real-world setting, focusing on healthtech experiment workflows and Firebase integration. The project is designed to be completed by a small team of learners within 60 hours each over an 8-week period.

The project deliverables include a functional and clickable FlutterFlow prototype with persistent data storage using a mock Firebase backend. Key components include an experiment creation form, daily symptom and activity logging, and a causal map visualization with mock tolerance calculations. Additionally, the project will produce an exportable summary report and comprehensive documentation, culminating in a final demo presentation.

StellaEats Internship Project Plan

Project: N-of-1 Experimentation Module (Phase 1 Execution)

Timeline: Sep 22 – Nov 14, 2025 (8 weeks)

Interns: 3–4 students (frontend/backend mix)

Mentor/PM: Primie Cegnar (CEO & Product Vision)

🗂️ Project Overview

The N-of-1 Experimentation Module enables users to run simple, personalized experiments (diet swap, elimination, reintro). The designs are already complete — interns will focus on building a working functional prototype in FlutterFlow with mock backend support.

This MVP will allow:

• Users to create experiments from templates.
• Users to log daily outcomes and activities.
• Data to persist in a mock Firebase backend.
• A causal map view to display tolerance badges (mock calculations).
• Export results as a summary report.

🎯 Project Objectives

1. Translate existing designs into a functional prototype (FlutterFlow + Firebase).
2. Implement experiment creation & daily logging with persistence.
3. Create backend schema for experiments, outcomes, activities.
4. Implement causal map UI with mock tolerance calculations.
5. Deliver a demo-ready MVP + documentation.

⏳ Project Duration

• Start Date: Sep 22, 2025
• End Date: Nov 14, 2025
• ~60 hours per student over 8 weeks

🧩 Key Deliverables

• FlutterFlow prototype (functional, clickable, persistent).
• Firebase mock schema (linked to experiments + outcomes).
• Causal map visualization (badges: green/yellow/red).
• Exportable PDF/slide summary of experiment.
• Final demo + documentation.
• 
  

🔹 Weekly Structure

Week 1 (Sep 22–26) SetupKickoff call, access to Figma/FlutterFlow/Firebase, review designs. Deliver: Setup complete.

Week 2 (Sep 29–Oct 3)E xperiment Creation. Implement “Create Experiment” form with Firebase storage. Deliver: Working form.

Week 3 (Oct 6–10)Outcome Logging Implement daily symptom logging (emoji sliders, notes). Deliver: Logs saved to Firebase.

Week 4 (Oct 13–17) Midpoint Review. Demo full flow: create experiment + daily log. Deliver: MVP checkpoint.Week 5 (Oct 20–24) Activity Logging Implement meals/supplements/sleep logs. Deliver: Activity log functional.

Week 6 (Oct 27–31) Causal Map MockBuild UI for causal map w/ badges from mock data. Deliver: Causal map view.

Week 7 (Nov 3–7) Export & Docs. Implement export feature + write developer docs. Deliver: Docs draft.

Week 8 (Nov 10–14)Final DemoPolish, test, and present full flow. Deliver: Final demo + handoff package.

Daily / Weekly Workflow

Daily (Async):

• Update in Google Chat → “Yesterday I built… Today I’ll work on… Blocked by…”

Weekly:

• Monday: Interns post weekly plan.
• Friday: Deliver working feature for that week.
• Biweekly: Live Google Meet demo with Norm + Primie.

👥 Project Roles

• Sponsor/Product Lead: Primie Cegnar
• Intern Roles:
• FlutterFlow implementer
• Firebase backend schema implementer
• QA + testing intern (rotating role)
• Optional: Documentation intern

🔧 Tech Stack

• Frontend: FlutterFlow (execution of designs)
• Backend (mock): Firebase / Firestore
• Docs: Google Docs, Slides
• Comms: Google Chat, Google Meet
• Version Control: GitHub (optional if needed for scripts/APIs)

📈 Success Metrics

• Create + save experiment in Firebase.
• Log daily symptoms + activities successfully.
• Render causal map with badges.
• Export mock summary report.
• End-to-end demo runs with no critical bugs.

🛑 Risks & Mitigations

RiskMitigationFirebase schema confusionProvide pre-drafted schema for internsOver-complicationStick to MVP scope (mock causal map, no real stats)Slow progressWeekly deliverables + Friday sign-offsUX bugsTest flows at midpoint + adjust

✅ Intern Learning Goals

• Building a real-world functional prototype (not just mockups).
• Firebase integration with FlutterFlow.
• Understanding healthtech experiment workflows.
• Delivering an end-to-end MVP module for a startup.
• Creating portfolio material: “I built a personalized nutrition experiment engine.”

Summary

Interns won’t design from scratch — they will execute existing designs into a working, functional prototype. The focus is on making the N-of-1 MVP flow real, storing data, and presenting it in a demo-ready form for customer validation.