Exercise library
Video demos, rep targets, weight targets, station notes. Reusable across every workout.
// The platform · Group fitness orchestration architecture
Cloud. Edge. Display.
Three layers. One system.
A deeper look at how Choccy Box runs a synchronised group fitness class — from cloud-based design, through on-prem execution, to multi-screen display and trainer control.
// Layer 01 / Content-Ops
Command Center.
Cloud CMS for class design.
The web-based dashboard where every workout, every program, every schedule is built. Multi-location operators design once and push to every site. Single-location operators get the full content toolkit without per-site duplication.
Set templates
Timing patterns ("3 rounds of 60s work / 40s rest") that apply to any exercise grouping.
Block & Workout templates
Compose sets into blocks; compose blocks into full workouts. Reuse without rebuilding.
Programs
Sequenced multi-week structures with progression logic — periodisation, volume blocks, deloads.
Multi-location scheduling
Push the same schedule to every site. Override per location when you need to.
Version history
Every change tracked. Roll back any workout, set, or schedule to an earlier version.
// Layer 02 / Edge-Ops
Edge Engine.
Dedicated hardware per location.
A purpose-built device installed at each gym location. Why dedicated hardware? Because group fitness classes can't tolerate a dropped WebSocket or a buffered video. The Edge Engine runs offline-first by design — schedule, videos, audio cues, station state, leaderboards — all local.
Phase-based timing
Intro · Demo · Warmup · Workout · Finisher · Cooldown. Each phase has its own logic, displays, and audio.
1Hz WebSocket sync
Every connected display ticks to the same clock, every second. No drift.
Offline operation
Internet only matters for syncing tomorrow. Today's class runs entirely locally.
Auto-chaining
Back-to-back classes load automatically. No manual setup between sessions.
Local video streaming
Exercise videos served from the Edge unit — no buffering, no latency, regardless of WiFi.
Audio cue generation
Distinct tones for work, rest, transitions, and completion. Members know what's happening without looking.
Concurrent block validation
Cardio + weights running in parallel zones — the Edge engine keeps every zone's timing aligned.
Exponential-backoff reconnect
Lose a TV mid-class? It rejoins the cluster automatically when it comes back.
// Layer 03 / Edge-Cast
Display & Control.
Apple TV + iOS, native.
Member-facing displays on Apple TV. Trainer control on iPhone or iPad. Built native because performance matters and Apple's ecosystem is the only one that gives a gym-grade TV experience without bespoke hardware.
// tvOS — Apple TV
- 21 station layouts · 1–6 stations per screen
- Horizontal & vertical TV orientations
- Phase-specific views (demo, warmup, timer, cooldown)
- Live competition leaderboards
- Exercise demo videos with rep + weight overlays
- Station-specific content per screen
// iOS — iPhone & iPad
- Trainer remote — start, pause, scrub, advance
- Live phase navigation
- Display management — change layouts on the fly
- Competition time entry — MM:SS.ms judge interface
- Schedule view + reconnect logic
- Station assignment + orientation control
// Why dedicated hardware
Because a class can't pause to reconnect.
Web-based class systems work fine — until the moment they don't. Spotty WiFi, ISP blip, packet loss between member-counted sets. The Edge Engine gives you guaranteed local execution; the cloud is for design and analytics, not class delivery.
Guaranteed offline operation
Class delivery doesn't depend on internet. Period.
Predictable timing
Local execution = no jitter, no buffering, no surprise pauses.
Data sovereignty
Class state lives at your location, not in someone else's cloud.
Lower long-term cost
No per-class cloud compute. The Edge unit pays for itself.
// Ready to dig in
See it on your gym floor.
Discovery call walks through Command Center, the Edge unit, the Apple TV display, and the iOS remote against your specific class formats.