Mobile app / PROJECT CASE STUDY

Fitness App & Programme Dashboard Case Study: Pulse

A fitness product pairing member activity screens with a coach-facing programme view for sessions, schedules and progress.

Workout programme app overview
Industry
Fitness
Focus
Workout Tracking
Experience
Mobile app

Project brief and workflow decisions

The desktop programme screen focuses on a selected member and the training plan assigned to them. Weekly navigation, session state and the next scheduled activity establish the relationship between the coach’s planning work and the member’s ongoing routine.

01

Member-specific programme context

The selected member remains visible while the coach reviews the programme. The adjacent summary names the programme and describes its focus, keeping the schedule connected to the training plan rather than presenting anonymous calendar entries.

02

Sessions with meaningful states

Session entries include an activity, duration, date and completion state. Weekly tabs organise the plan into manageable periods. A completed session and a scheduled session are labelled differently so planned work is not confused with recorded activity.

03

Progress and the next activity

A weekly progress indicator and next-session summary give the programme a clear current state. Assign programme and Edit programme actions remain identifiable. Mobile screens show the related member-facing experience.

Progress views are most useful when their definitions are visible. Distinguish a planned activity, a completed session and the next task instead of compressing them into a single score.

Explore the relevant development service for this project workflow to discuss your requirements.

Enterprise reference architecture

A proposed engineering design for this workflow. The enterprise scenario and stack below are illustrative architecture choices; they are separate from the confirmed project screens.

The enterprise scenario

A fitness organisation connects coaches and members across clubs, with programme changes, scheduled sessions and workouts completed on intermittently connected phones.

Architecture objective: Version training plans and reconcile member activity without confusing a new programme revision with the plan under which an earlier session was completed.

Proposed technology stack and rationale

Member and coach interfaces

React Native for mobile; React and TypeScript for coach tools

Share typed domain contracts while designing each experience around its distinct task.

Application services

Laravel (PHP) with a versioned REST API

Scope queries and mutations by organisation, coach assignment and member access.

Programme records

MySQL with versioned plans and activity records

Preserve the programme revision associated with each scheduled or completed session.

Offline activity

SQLite on the device and a synchronisation outbox

Capture local commands with stable identifiers and reconcile them when connectivity returns.

Reminders and operations

Laravel queues on Redis, APNs/FCM adapters and Sentry

Treat reminder delivery as a separate operational concern from session completion.

Technical challenges and design approach

1

Offline duplicate activity

A phone may resend a completed session. Deduplicate by command identity and retain a clear conflict result when the underlying plan changed.

2

Programme revisions

A coach can change a future plan after activity was recorded. Preserve historical versions and apply an explicit rule for affected future sessions.

3

Personal information boundaries

Club membership alone should not expose every member record. Authorise the actual coach-member relationship at the data boundary.

How the proposed workflow fits together

  1. The coach publishes a versioned programme and assigns it to a member.
  2. The member downloads the assigned plan and records activity locally.
  3. Synchronisation submits stable activity commands with the originating plan version.
  4. The service accepts, rejects or flags a conflict and updates the member’s authoritative progress.
  5. Coach views and reminder jobs use the resulting records rather than estimating completion from app opens.

Acceptance and failure-path checks

  • The same offline completion submitted twice produces one accepted activity.
  • Historical progress remains attributable to the programme revision used.
  • A removed coach loses access to protected member records.
  • Notification failures do not change the recorded completion state.

The tradeoff

Offline support should be limited to clearly defined commands and read models. Attempting to synchronise every possible edit creates avoidable conflict and privacy complexity.

Architecture references: React Native documentation and Laravel queues. These describe engineering patterns, rather than certify this project’s implementation.

What the project brings together

  • Member and programme selection
  • Weekly sessions with completion states
  • Coach summary and next-session information

Let’s create what’s next.

Bring your idea. We’ll help you find a clear way forward.

Discuss your project