Week 4 Worklog

Week 4 Objectives:

  • Backend: Build the System Workout module — the master exercise and workout plan data managed by admins.
  • Frontend: Build core workout browsing screens — suggested plan wizard and exercise picker.
  • Establish the relationship between GoalType ↔ WorkoutPlan ↔ Exercise for plan recommendations.

Tasks to be carried out this week:

DayTaskStart DateCompletion DateReference Material
2- Build MuscleGroup entity & admin CRUD
  + Entity fields: name (UNIQUE, ≤100 chars), description (≤500 chars)
  + AdminMuscleGroupController (/api/admin/muscle-groups) with @PreAuthorize("hasRole('ADMIN')")
  + CRUD: POST, GET /, GET /{id}, PUT /{id}, DELETE /{id}		01/27/202601/27/2026
3- Build Exercise entity & admin CRUD
  + Entity: name (≤150), description (≤500), equipment, muscleGroup (@ManyToOne)
  + AdminExerciseController (/api/admin/exercises): full CRUD + filter by muscle group
  + Public: GET /api/workouts/exercises, GET /api/workouts/exercises/{id}, GET /api/workouts/exercises/by-muscle-group/{id}, POST /api/workouts/exercises/custom		01/28/202601/28/2026
4- Build WorkoutPlan & WorkoutPlanExercise entities
  + WorkoutPlan: name, description, goalType (@ManyToOne), difficultyLevel, estimatedDurationMinutes, isSystemPlan
  + WorkoutPlanExercise: dayOfWeek (1-7), sets, reps, restSeconds, dayIndex, weekIndex, orderIndex
  + AdminWorkoutPlanController with full CRUD + filter by goal type		01/29/202601/29/2026
4- Expose public workout endpoints via WorkoutController (/api/workouts)
  + GET /muscle-groups, GET /muscle-groups/{id}
  + GET /exercises, GET /exercises/{id}, GET /exercises/by-muscle-group/{id}
  + GET /plans, GET /plans/{id}, GET /plans/by-goal-type/{id}		01/29/202601/29/2026
5- Build SuggestedPlanScreen (Frontend) — 3-step wizard
  + Step 1: Select fitness goal type (fetches from GET /api/goal-types)
  + Step 2: Browse system workout plan tiles with images and difficulty level
  + Step 3: View full plan detail with exercises grouped by day → clone via cloneFromSystemPlan		01/30/202601/30/2026
6- Build PlanExercisePicker screen (Frontend)
  + List all system exercises with images and muscle group labels
  + Search/filter by name
  + On select: call addExerciseToPlan(planId, dayOfWeek, exerciseId)
- Seed initial exercise and muscle group data into the local database via DatabaseSeeder		01/31/202601/31/2026

Week 4 Achievements:

  • Backend — System Workout:
    • MuscleGroup entity + admin CRUD fully operational; seeded with common muscle groups (Chest, Back, Legs, Shoulders, Arms, Core).
    • Exercise entity + admin CRUD + public read endpoints working.
    • WorkoutPlan with WorkoutPlanExercise (day-of-week scheduling, multi-week support via weekIndex) implemented.
    • All admin endpoints protected by ROLE_ADMIN; public read endpoints accessible without auth.
    • GET /api/workouts/plans/by-goal-type/{id} correctly filters system plans by goal type.
  • Frontend — Workout Browsing:
    • SuggestedPlanScreen guides users through goal → plan selection in 3 clear steps.
    • Plan tiles display name, difficulty level, estimated duration, and goal type.
    • PlanExercisePicker lists all exercises with muscle group context; exercise selection adds to user plan.
  • DatabaseSeeder robustly parses s3_images_upload.json to seed muscle groups + exercise data on app start, solving mapping issues with special characters and whitespace to ensure 100% S3/CloudFront image URL alignment.

AWS Knowledge Learned:

  • Learned to design media architecture with Amazon S3 for binary objects and PostgreSQL for metadata, keeping each storage system in the role it handles best.
  • Designed object key naming conventions such as workouts/, exercises/, and foods/ to simplify organization, cleanup, and lifecycle policy targeting.
  • Understood private-by-default bucket access and why broad public ACL usage should be avoided for application assets.
  • Studied server-side encryption options, especially SSE-S3 and SSE-KMS, and when KMS-backed control is worth the extra complexity.
  • Learned the value of S3 versioning for protection against accidental overwrite or deletion of important media files.
  • Understood storage and transfer cost tradeoffs for image-heavy applications, especially why optimization of size and format matters.
  • Prepared the storage model so CloudFront can later sit in front of S3 without forcing business logic changes in the app.

In summary, week 4 translated AWS storage knowledge into a maintainable media architecture for exercises and plans.

Next Week Plan:

  • Backend: Build the UserWorkoutPlan module with plan cloning from system templates, soft-delete, and activate/deactivate logic.
  • Frontend: Build MyPlansScreen, CreatePlanScreen, and PlanEditScreen (day-tabbed exercise editor).