Strength for the
sport you play.

A native strength-training app for people who also practise another sport. I developed the product, identity and programme engine together.

Granite native weekly programme. — Granite / Native product capturesOwned product · AlphaTwo native screens · Swipe to compare →

Granite native coach with the waveform and transcript in separate areas. — Granite / Native product capturesOwned product · AlphaTwo native screens · Swipe to compare →

Scope: Identity · Product design · Native iOS
Project: Owned product · Alpha · Dan Andrews · 2026

The brief

The lifting programme has to fit the athlete’s real week.

Available days change. Another sport competes for recovery. A generic workout log does not resolve that. I built Granite around one programme model, connecting planning, coach input, working sets and training history.

The defining decision

Make the programme the centre of the product. Planning, voice input and working sets all act on the same training model.

The product in use

A change becomes a new block.

Follow a training week into the coach, confirm a change and watch the programme rebuild. The native app makes the changed loads visible before the next session.

Recorded 4 October 2026 · iOS simulator · Demo data · Pauses trimmed

Read the walkthrough

The Programme view shows Week 3, with exercises, sets and working loads.
The coach opens with a supplied example: extra jiu-jitsu sessions and a sore shoulder. The user confirms the app’s interpretation. This recording does not demonstrate live speech recognition.
The user chooses “Rebuild my block around this”. The app confirms the rebuild and displays the revised squat, bench press and deadlift loads.

Native app recording. The coach transcript and parsed intent are supplied by demo mode; confirmation and block rebuilding run in the app.

01 / The programmeGranite

The week gives the coach its context.

A strength programme has to share time and recovery with the athlete’s other sport. The week, coach and review are organised around the same programme model.

The captured coach separates the spoken instruction, transcript and listening state. The weekly review shows how a changed week can be explained before training resumes.

Fig. 01The coach: instruction, listening state and input are separate.

02 / The sessionGranite

A working set needs a different hierarchy.

The programme holds the week’s context. During a session, exercise, load, repetitions and rest become the immediate information.

The native screen puts the working sets beside the reason for today’s training. Planning and execution remain connected without asking the athlete to read the whole programme between sets.

Fig. 02The native session: working sets and the reason for today’s training.

03 / First useGranite

Give the first session a clear next step.

The Progress view has a useful job before the first workout is logged. It explains where personal records will appear and links directly back to the programme.

I designed this empty state around the next action: log a working set. The week and session counts provide context without filling the screen with invented progress.

Fig. 03The first-use Progress view: context, an explanation and a route to the programme.

IdentityMovement vocabulary

A language for the work.

Exercise glyphs make movement recognisable throughout the programme. The same vocabulary connects the plan, the session and the product identity.

Movement

Goal

Equipment

Level

Action

Coach

Branding detail · Granite · the glyph setForty-five custom glyphs give movement, goals, equipment and actions a shared geometry. Compact labels and bright state accents carry that language into the week and training screens.

Art directionConcept film

Earlier concept film · Art direction

Art direction

Made before the app existed.