Back to working plan MVP detail

Workout & Program Library

Exercise Library Detail Plan

The exercise library should not be built manually in phase one. The product should integrate with an external exercise content provider, then expose a coach-friendly search and selection workflow inside the program builder.

External provider Program builder search Arabic support check

Provider Assumption

Use an external exercise library such as Funxtion, Wrkout, or another vendor with exercise metadata, video demonstrations, muscle groups, and equipment tags.

  • Vendor decision remains open until API, licensing, Arabic support, content quality, and pricing are reviewed.
  • The app should store provider IDs and normalized metadata, not duplicate full content unless licensing allows it.
  • The integration should be replaceable if the first vendor does not fit the product requirements.

Coach Entry Point

The coach starts from the program builder, not from a separate exercise-management screen.

  1. Coach selects “Add program” or opens an existing program draft.
  2. Coach lands on a program-building screen with exercise search and muscle groups visible together.
  3. Coach searches, reviews, and adds exercises into the selected day or workout block.

Main Coach Flow

  1. Coach chooses to add a program.
  2. System opens the program builder with exercise search and muscle groups on the same screen.
  3. Muscle groups are fetched from the selected external exercise library.
  4. Coach can browse by muscle group before typing.
  5. When the coach starts typing in search, the interface hides the surrounding builder content and emphasizes search in a focused overlay or modal-like state.
  6. Search results are fetched from the external library and shown as the coach types.
  7. Coach selects an exercise and adds it to the current program day/block.
  8. Coach can then configure sets, reps, RPE/RIR, rest, notes, and optional alternatives.

Screen Behavior Reference

Muscle Groups

Fetched from provider.

Chest
Back
Shoulders
Quadriceps
Hamstrings
Core

Arabic Support

Arabic support must be verified during vendor evaluation. If the provider supports Arabic search and Arabic exercise content, use the provider capability directly.

If Arabic is not supported, the app needs a translation/inference layer between Arabic and English.

Fallback Inference Flow

  1. Detect whether the search query is Arabic or English.
  2. If Arabic, map the Arabic term to known English exercise, muscle, and equipment terms using local synonym data or a translation tool.
  3. Search the external provider using the inferred English query.
  4. Return provider results and display Arabic labels where local translations exist.
  5. Capture missing translation terms for admin review and future improvement.

Implementation Requirements

Area Requirement
Provider API Must support exercise search, exercise details, video/media references, muscle groups, equipment, and stable exercise IDs.
Muscle groups Fetched from the same external library so browse and search use one consistent taxonomy.
Search UX Typing in search should enter a focused overlay/modal-like state that hides or dims non-search content until the coach selects an exercise or exits search.
Arabic Vendor Arabic support must be checked. If missing, implement local translation/synonym inference between Arabic and English terms.
Program builder Selected exercises must be inserted into the active program day/block and then configured with sets, reps, rest, RPE/RIR, notes, and alternatives.