Remix

Make your own version of DaysOfFit Fitness Foundation

Get an exact, working copy in your account, then change anything with chat.

Original by David Alexandru

What would you change?

Start free with 40 credits. No card needed.

Start fresh from this prompt

Builds a brand new app from the first prompt only, so later changes to the original are not included.

Build the first version of a fitness and activity app called DaysOfFit.
The goal of this first phase is to build a polished, functional foundation that we can expand later. Do not add advanced features that are not requested in this prompt. Keep the architecture modular so future phases can add AI, animated characters, points, achievements, exercise detection, voice commands, GPS, buddies, food, languages, and other systems without rebuilding the core.
1. APP IDENTITY
App name:
DaysOfFit
Main idea:
A highly customizable workout and activity app focused primarily on bodyweight exercises, workout creation, activity tracking, and personalization.
Use a clean, modern fitness-app UI. It should feel like a real finished mobile application rather than a prototype.
Use responsive layouts that work well on phones and larger screens.

───

2. ONBOARDING
Create a one-question/screen onboarding flow.
Use one reusable onboarding system controlled by a currentStep value instead of creating completely separate onboarding systems.
Show a clear progress indicator.
Step 1 — Welcome
Title:
DAYS OF FIT
Subtitle:
Your workouts. Your way.
Text:
"Let's personalize DaysOfFit for you."
Button:
LET'S GET STARTED
Small text:
"We'll ask you a few quick questions to set up your experience."
Step 2 — About You
Ask for:
• Age
• Height
• Weight
Use appropriate numeric inputs.
Automatically calculate BMI when enough information is available.
Display BMI as informational data only.
Do not make BMI the sole determinant of fitness recommendations.
Step 3 — Fitness Level
Question:
What's your current fitness level?
Selectable options:
Beginner "I'm just getting started."
Intermediate "I exercise regularly and know the basics."
Advanced "I'm experienced with challenging workouts."
Allow one selection.
Step 4 — Push-Up Level
Question:
How many push-ups can you do without taking a break?
Text:
"Choose the option that best describes you."
Options:
Beginner "5 or fewer"
Intermediate "5–10"
Advanced "10+"
This is ONLY a selection question.
Do NOT create a push-up test.
Do NOT open the camera.
Do NOT make the user perform push-ups.
Do NOT create a push-up counter here.
The selected option should be stored as the user's pushUpLevel.
Step 5 — Goals
Question:
What are your goals?
Allow multiple selections.
Options:
• General fitness
• Strength
• Endurance
• Flexibility
• Mobility
• Conditioning
• Build a workout habit
• Sports performance
• Custom goal
If Custom goal is selected, provide a text field.
Step 6 — Activities
Question:
What activities are you interested in?
Allow multiple selections.
Options:
• Strength workouts
• Cardio
• Mobility
• Explosive exercises
• Walking
• Running
• Cycling
• Dancing
• Sports
• Other
Include a "Skip for now" option.
Step 7 — Favorite Exercises
Question:
Which exercises do you want to use?
Provide a searchable exercise selection interface.
Allow multiple selections.
Include categories such as:
Legs
• Squats
• Lunges
• Glute bridges
• Calf raises
• Wall sit
Upper Body
• Push-ups
• Knee push-ups
• Wide push-ups
• Diamond push-ups
• Pike push-ups
• Shoulder taps
Core
• Plank
• Side plank
• Crunches
• Leg raises
• Bicycle crunches
• Mountain climbers
Full Body
• Burpees
• Bear crawls
• Inchworms
• Jumping jacks
• Squat thrusts
Also provide:
SELECT ALL
and
CLEAR ALL
The exercise library must be structured so many more exercises can be added later without changing the system.
Step 8 — Workout Preferences
Ask:
How do you like to work out?
Typical workout length:
A slider from approximately 5 minutes to 60+ minutes.
Store the selected value in seconds.
For example:
20 minutes =
workoutLength = 1200
Ask:
How often do you want to work out?
Options:
• 1 day/week
• 2 days/week
• 3 days/week
• 4 days/week
• 5 days/week
• 6 days/week
• Every day
Ask:
Workout style
Options:
• Reps
• Timed
• Mixed
• Custom
Step 9 — Personalization
Allow the user to select:
Theme:
• Dark
• Light
• System
Units:
• Metric
• Imperial
Sounds:
• On
• Off
Animations:
• On
• Off
Step 10 — Complete
Title:
YOU'RE ALL SET!
Show a short summary of the user's selections.
Provide:
CREATE MY FIRST WORKOUT
and
BUILD ONE MYSELF
Do not generate the actual AI workout yet. The first button can lead to a placeholder/appropriate future-ready screen if the workout generator is not implemented in this phase.

───

3. MAIN APP
After onboarding, show the main DaysOfFit home screen.
Create bottom navigation with:
Home
Workouts
Activities
Progress
Profile
Make the navigation functional.
Home
Show useful cards such as:
• Greeting
• Today's workout
• Quick start
• Recent activity
• Current goals
• Basic progress
Use the user's saved information where appropriate.
Workouts
Provide:
• Saved workouts
• Create Workout
• Start workout
Activities
Provide a basic activity section for:
• Walking
• Running
• Cycling
• Hiking
• Sports
• Dancing
• Other activities
For this first phase, create the basic UI and manual activity structure. Do not implement advanced GPS tracking yet.
Progress
Create a basic progress screen prepared for future statistics.
Include:
• Workouts completed
• Total workout time
• Recent workouts
• Personal records placeholder
• Activity history
Profile
Show the saved onboarding information and settings.
Allow the user to edit their information and preferences.

───

4. EXERCISE LIBRARY
Create a structured exercise database.
Every exercise should have fields that can support future features.
For example:
• id
• name
• category
• difficulty
• trackingType
• description
• instructions
• selectedByUser
Supported tracking types for this phase:
• reps
• time
• custom
Start with the exercises listed in onboarding, but structure the database so many more can be added later.

───

5. WORKOUT BUILDER
Create a functional Create Workout screen.
Title:
Create Workout
Button:
+ ADD EXERCISE
When adding an exercise, allow the user to select:
• Exercise
• Tracking type
• Target value
Tracking types:
Reps
Time
Custom
Example workout:
Push-ups — 20 reps
Plank — 60 seconds
Jumping Jacks — 50 reps
Rest — 30 seconds
Allow users to:
• Reorder exercises
• Edit exercises
• Duplicate exercises
• Delete exercises
• Add rest periods
• Save workout
• Start workout

───

6. WORKOUT PLAYER
Create a functional workout player.
Display:
• Current exercise name
• Exercise description/instructions
• Demonstration placeholder
• Large rep counter or timer
• Pause
• Resume
• Skip
• Next
• Finish workout
Implement rest timers.
Do not implement AI exercise detection yet.
Do not implement camera-based counting yet.
The demonstration area should be designed so a future animated 2.5D character can be inserted without redesigning the workout screen.

───

7. PERSISTENCE — VERY IMPORTANT
Use OPFS (Origin Private File System) for local persistence.
Create one main DaysOfFit application state file, for example:
/days-of-fit-private/app-state.txt
Store the application's state as structured JSON inside this file.
The goal is for the file to eventually contain essentially EVERYTHING persistent about the user.
Do not create a separate persistence architecture for every feature.
Use one central state system.
For example, the JSON can conceptually contain:
json
{
  "profile": {},
  "onboarding": {},
  "exercises": {},
  "workouts": {},
  "activities": {},
  "history": {},
  "progress": {},
  "settings": {},
  "food": {},
  "achievements": {},
  "points": {},
  "themes": {},
  "buddies": {},
  "voice": {},
  "gps": {}
}

Only implement the fields required by this phase now, but keep the structure expandable.
Examples of persistent values:
text
workoutLength = 900
fitnessLevel = "intermediate"
pushUpLevel = "advanced"

squats = true
lunges = false
pushUps = true

goalStrength = true
goalEndurance = true
goalFlexibility = false

theme = "dark"
units = "metric"
sounds = true
animations = true

Use proper JSON internally rather than relying on hundreds of unrelated files.
Every important user change should update the central application state.

───

8. ONBOARDING PERSISTENCE
Save onboarding progress as the user moves through the screens.
Persist:
• Current onboarding step
• All completed answers
• Profile information
• Exercise selections
• Goals
• Activities
• Preferences
If the user closes the app halfway through onboarding, reopening the app should resume from the saved step.
When onboarding is completed:
onboardingComplete = true
On future launches, skip onboarding and open the Home screen.

───

9. APP STATE LOADING
When DaysOfFit launches:
1. Open the OPFS state file.
2. Read the saved JSON.
3. Parse it safely.
4. Restore the application state.
5. Determine whether onboarding is complete.
6. Open Home if complete.
7. Resume onboarding if incomplete.
8. Gracefully handle a missing or corrupted state file by creating a valid default state.
Do not wipe existing user data during normal app updates.

───

10. ARCHITECTURE FOR FUTURE PHASES
Build the code/components so future phases can add:
• OpenAI-powered AI workout generation
• AI fitness assistant
• 2.5D exercise character
• Points
• Themes
• Achievements
• Streaks
• Personal records
• AI exercise detection
• Voice commands
• Running/GPS
• Advanced statistics
• Buddies
• Languages
• Gen Z mode
• Full customization
• Food/recipe system
• Experimental features
without rebuilding the entire application.
Do NOT implement these advanced systems yet.

───

11. DESIGN
Make the UI:
• Modern
• Clean
• Responsive
• Easy to understand
• Touch-friendly
• Consistent
• Smooth
• Fitness-focused
Use consistent cards, buttons, typography, spacing, icons, and navigation.
Avoid unnecessary clutter.
The application should feel like a real product from the first launch.

───

Start fresh from this prompt

Builds a brand new app from the first prompt only, so later changes to the original are not included.