Coach
01
Bring your data together
Activity, sleep, heart rate, HRV and recovery from your watch; calories and nutrients from your diet app; weight and body composition from your bioimpedance scale.
COACH / Full guide
Your plan and progress, step by step.
Connect your sources, define your goal, build an AI plan and take it to your watch. This guide covers tracking, routes and settings using real app screenshots.
Real app screenshots · ES / EN
Plan
COACH / From data to training
A complete cycle. Your training, in context.
Your goal guides the plan. Completed training, recovery, nutrition and body trends provide context for tracking progress and for adjustments proposed by AI.
02
An AI-adapted plan
Your goal, sports, availability and history inform AI. The plan sets out sessions, intensity, recovery and nutrition targets using the available data.
03
Your plan, on your wrist.
Send compatible workouts to Garmin, Suunto or COROS* and follow the session on your sports watch.
04
Tracking that closes the loop
Completed workouts, rest, diet and weight trends return to Coach. Compare the plan with recorded data and use that context when reviewing the plan with AI.
01 / Screens
See the app up close.
The app modules as they appear on Android. Select a screenshot to enlarge it.
Screens
Plan
Your goal, sports, availability and history inform AI. The plan sets out sessions, intensity, recovery and nutrition targets using the available data.
Calendar
Review your planned sessions and see how training and nutrition fit together each day in the calendar.
Today
Sleep, heart health, recovery and movement in one view.
Stats
Completed workouts, rest, diet and weight trends return to Coach. Compare the plan with recorded data and use that context when reviewing the plan with AI.
Routes
Tiles © EsriDownload available GPS tracks from your activities and bring your routes together on the Coach map.
Your route totals
Filter by sport and period. Review activity count, distance, elevation gain and calories, broken down by sport and with a period total.
Nutrition
Energy and macronutrients alongside your daily goals.
Body composition
Weight, body fat, water and other measurements received from your scale, with their trends.
Settings
Eight pages: General, Connections, AI, Coach, Tutorial, Backup, Simulation and About. The goal and the AI settings save when a field loses focus or you leave the app. The manual below walks through each page.
Full screenshots of the real app, using real data. Switch between Spanish and English and enlarge an image to see the details.
02 / Plan
A plan that understands your context.
An AI-adapted plan
Your goal, sports, availability and history inform AI. The plan sets out sessions, intensity, recovery and nutrition targets using the available data.
The plan has phases, a near horizon with detailed sessions, and distant dates that are still provisional. Chat talks about recovery, load and meals, and can propose a change for you to apply to that day. A photo, a camera shot or a dictation replaces only the future day you chose, after a preview.
Workout details
Check the objective, warm-up, blocks, repetitions and instructions for the workout already in your plan.
Tracking that closes the loop
Completed workouts, rest, diet and weight trends return to Coach. Compare the plan with recorded data and use that context when reviewing the plan with AI.
Month and year, with an activity filter. Pick a day and you see the score: workout, calories, protein, carbohydrate, fat and sessions. On target, watch the adjustment and off target sit beside three separate results: confirmed rest, a missed session and unknown coverage. From the detail you can log RPE, RIR, sets, reps and load.
Workout details
Nutrition
Diet app records supply calories and macronutrients when shared with Google Health connect.
Body composition
Your scale supplies weight and the bioimpedance measurements it shares. Their trends add context to planning and progress tracking.
Stats
Completed workouts, rest, diet and weight trends return to Coach. Compare the plan with recorded data and use that context when reviewing the plan with AI.
The standout feature
Your plan, on your wrist.
Follow your training plan on your sports watch.
Enable plan delivery in the manufacturer connection. Then sync Garmin Connect, Suunto or COROS with your watch to access compatible sessions and their instructions.
* This COROS connection only supports following running —including trail/ultra— and cycling workouts on the watch. Gym, strength, HIIT and other sports remain in Coach and are not sent to COROS as executable sessions.
Connections and compatibility ↗Your plan, on your wrist.
Real app screenshots · ES / EN
04 / Routes
Your tracks, stored locally.
Download available GPS tracks from your activities and bring your routes together on the Coach map.
Your route totals
Filter by sport and period. Review activity count, distance, elevation gain and calories, broken down by sport and with a period total.
Downloaded tracks remain on your device. You can import a GPX and export a route from its detail view to save it as a local file.
Local track storage does not include a complete offline map: the initial download and map tiles may require a network connection.
Routes
Tiles © EsriYour route totals
AI / COACH
AI, your way.
AI uses the available context to build the plan and explain progress. Choose local, hybrid or remote execution to suit your device and preferences.
Local
No inference leaves the phone. If the model is missing, identified rules are used, or the app says AI is unavailable.
Hybrid
The plan, chat and summaries of a period may use the remote provider. The daily coach, the evaluation and a detail explanation stay local.
Remote
Inference tasks use the configured provider. If that provider is unavailable, a local model that is already downloaded can step in.
Set up Coach with the tutorial
Open Config → Tutorial → Repeat tutorial. Follow these steps to connect your data and create your first plan.
-
01
Your watch
Choose Garmin, Suunto or COROS so the tutorial shows your manufacturer’s steps. You can also start without a watch.
Your watch
-
02
Google Health connect
Grant access to sleep, heart rate, activity, nutrition and body measurements shared by your apps and devices.
Google Health connect
-
03
Connect your manufacturer
Sign in with the account you use for your watch. Review the options for sending your plan and weight before continuing.
Connect your manufacturer
-
04
Choose your AI
Select on-device or cloud AI. Configure the model and your API key if your provider requires one.
Choose your AI
-
05
Your goal and your plan
Describe your goal, set a date and choose your sports. Tap “Create my plan”, then review your sessions in Coach.
Your goal and your plan
Configure each section separately
All these settings remain available in Config. You can change them without repeating the tutorial.
General
Appearance, language, voice, sync diagnostics and deleting the history.
-
1
Appearance. System, light or dark. By default it follows the phone.
-
2
Language. Automatic, or one of these: Spanish, English, Brazilian Portuguese, French, German, Italian, Simplified Chinese, Hindi, Russian and Japanese. If the system language is not in that list, Automatic uses Spanish. To see the plan in the new language, generate it again.
-
3
Coach voice. The rate affects the whole app. In Spanish you can choose an installed voice and hear a sample.
-
4
Sync. Diagnostics list every source. Garmin Connect updates on its own every 12 hours; from its card you can also force metrics and GPX. A full sync is started from this page.
-
5
Data and privacy. From here you open the health-permission link. Deleting local data removes metrics, sleep, activities, analyses and plans. Connections and keys remain. Sync stays paused until you tap refresh, and weight upload to Garmin turns off.
Connections
Google Health connect, watch accounts and the key used to draw routes. Several accounts can be connected at once.
-
1
Google Health connect. Install or update it, then grant permissions. Coach only reads. Activity, sleep, nutrition, weight and the other types the source app publishes, and that you allow, can arrive. Revoking a permission does not delete what is already stored.
-
2
Garmin Connect. Sign in on Garmin’s website. The app encrypts the tokens and does not see your password. Then you can sync metrics, look for missing GPX files and import one. Two switches work only while the session is open: send the 14-day plan to the calendar, and copy weight and body composition from other scales.
-
3
COROS. Connect the account, sync and, if you want, publish workouts. GPS history arrives from the newest backward, with a maximum of 50 activity files a day. Photos, sending routes to the watch and weight are not part of this connection.
-
4
Suunto. Sign in to the Suunto app account. Workouts, sleep, daily activity and available GPS are read. Guides go to the watch when you sync Suunto. Weight does not come in this way. Text has limits: step title 13 characters, notice 54, field 40, guide name 60 and description 256.
-
5
AI routes. Create a free key at openrouteservice.org and paste it here. Without a key, chat can propose a route and cannot draw it. The longest drawable route is 100 km. Sending to Garmin creates a private course in Garmin Connect.
-
6
Diet, scales and other devices. They must share compatible data with Google Health connect. Authorise reading in Coach. Each metric depends on what the source application publishes.
| When publishing | What the watch executes | What stays as text |
|---|---|---|
| Garmin | Steps, laps and repetitions for strength and HIIT. | Targets without measured heart rate, pace or power. Pool swimming falls under “other”. |
| Suunto | A guide with compatible times and fields. | Exercise names, zones written as “Z2”, and repetitions, which advance with Lap. |
| COROS* | Running, trail/ultra and cycling, with their sections. | * This COROS connection only supports following running —including trail/ultra— and cycling workouts on the watch. Gym, strength, HIIT and other sports remain in Coach and are not sent to COROS as executable sessions. |
Garmin Body Battery, stress, load and readiness do not come out through Google Health connect. Those readings depend on the source delivering them by its own path. The repository has a gateway contract for an authorised server using Garmin’s health API; this app does not ship that server.
AI
First choose where it reasons. The remote provider is shown only in hybrid and remote. Changing mode does not delete the keys.
-
1
Mode. Local, hybrid or remote. The policy for each one is in Where it reasons.
-
2
Local model. Visible in local and hybrid. The runtime runs in another process. Gemma 4 E2B asks for about 8 GB of RAM and is the default: text, image and audio, on GPU or CPU. Gemma 4 E4B asks for 12 GB and GPU only. LFM2.5 2.6B asks for about 6 GB and is text. LFM2.5 1.2B asks for about 4 GB, is text, and the app does not propose it on its own. Download, cancel and delete live on the same card. The speed profile is automatic, quality or fast, and you can measure the model on the phone.
-
3
Remote provider. OpenAI, Azure Foundry, Gemini, Claude, DeepSeek, OpenRouter or OpenCode. Each one keeps its key, model and endpoint. An empty field uses that provider’s default. OpenRouter wants the full identifier, for example
openai/gpt-4.1-mini. OpenCode uses Console IDs, such asglm-5.3-flash; if you leave the endpoint empty, the app picks Chat Completions, Responses, Messages or Gemini from the model. The OpenCode Go subscription is a different API and is not the one Coach uses. -
4
Key and test. The key is never shown again: you see dots when one is saved, and typing replaces it. “Test connection” saves the form first and requires a real reply. A truncated, blocked or empty final reply is rejected.
-
5
Images and audio. The model card says whether it accepts photos. Local Gemma 4 does. The catalog LFM models do not, and the photo is not diverted to another provider. In hybrid, if the chosen remote model is text-only and a local Gemma is ready, the image can stay on that Gemma. DeepSeek Flash accepts vision; DeepSeek Pro does not. Local import audio is up to 30 seconds on the device.
Plan generation can continue in the background, with a notice and cancellation, for about thirty minutes with the CPU awake. The previous plan remains until the new one passes validation. Android may stop the process: an interrupted remote request is not relaunched on its own.
Coach
What the app needs in order to calculate: the goal, the sports, the energy strategy and a reference weight.
-
1
Goal. Free text of up to 3,000 characters: the event, injuries, travel, impossible days, equipment, experience and how you eat. The description and the date decide the structure, the length and the detail. It saves when the field loses focus.
-
2
Sports. Choose the ones you practise. The catalogue covers running, cycling, swimming, multisport, gym, outdoors, winter, water, racket, team, combat and motor. The plan and the watch publish use that selection.
-
3
Energy. Automatic for the goal, maintenance, moderate deficit or moderate surplus. Base weight, between 25 and 300 kg, is used to estimate when the watch has not yet provided enough expenditure. On the plan itself, each day says whether energy came from the watch history, basal metabolism, weight or the other days of the plan.
-
4
Generate plan. The button saves the form and starts generation. You can leave the screen: the notice shows the phase. A generation that stopped partway can resume when the data, the model and the policy still match. Regenerating does not reuse a plan that already finished.
Equipment, limitations and food preferences belong in the goal text, not in separate boxes. Minutes from another sport do not cover the prescribed session.
Tutorial
A short walkthrough to get the app ready: watch, Google Health connect, AI and goal. You can repeat it whenever you want. On the model step, the app looks at the phone’s RAM and proposes a compatible one. Real compatibility also depends on free memory at that moment.
If you already set everything up from the other pages, the tutorial only confirms the same path.
Backup
-
1
What it includes. The whole database: metrics, activities, sleep, nutrition, plans, evaluations, chat and GPS tracks, plus the goal profile. Keys, manufacturer sessions and the backup password stay out.
-
2
Password. Empty: a verifiable, readable file. With a password: an AES-256-GCM envelope. The app does not remember it. The same password is required to restore.
-
3
Create. You choose the destination with the document picker. When it finishes you see the row and table counts. The file is checked as it is written.
-
4
Restore. You choose the file and confirm. Format, size, integrity and tables are checked before the history is replaced. If something fails, the previous database is recovered. Then the app must restart. Sync stays paused and body upload stays off. Credentials on this phone are kept. The file limit is 512 MiB.
Simulation
It can be turned on only when the app is empty: no metrics, activities, routes, plans, meals or sleep. It loads six weeks of example data — state, sleep, workouts with routes, meals and a plan — and pauses every sync. A banner reminds you that you are looking at example data. Leaving deletes the local database, including anything you created during the simulation, and sync returns.
With real watch data, this page stays closed on purpose.
About
Version of this guide: 1.1.23. App email: coach.ia.app@gmail.com.
Connect Garmin, Suunto or COROS*. Nutrition and data from scales and other devices arrive through Google Health connect when the source shares them and you grant permission.
Sleep estimates and plan review are training aids. They are not a clinical model or a validated injury predictor.
Build
For anyone producing the app from this repository. You need JDK 17 and Android SDK Platform 36.
-
1
Checks.
./gradlew :app:testDebugUnitTest :app:lintDebug :app:assembleDebug :app:assembleDebugAndroidTest -
2
Artifacts.
./gradlew :app:assembleRelease :app:bundleRelease. Debug APK:app/build/outputs/apk/debug/Coach-debug-1.1.23.apk. Release:Coach-1.1.23.apkandCoach-1.1.23.aab. -
3
Signing. Distribution uses the upload key, kept outside the repository. Without that key, the release build uses the debug signature and Play will not accept it.
-
4
Schema. Room exports schemas in
app/schemas. The database lives in the app’s private storage. Key preferences use Android Keystore. Android’s automatic backup is off.
Tests that recreate the database require a separate package and a disposable device. They are not part of daily use on an installation that is already configured.
What stays and what can leave
Private by default. Explicit when something leaves the phone.
Stays on the phone
- Metrics, sleep, activities, routes, plans, evaluations and chat.
- Keys and sessions, encrypted with Android Keystore.
- Local-mode inference, including photos Gemma processes.
- The adherence score, calculated here.
Leaves only if you configure it
- Summaries to the AI provider, in hybrid or remote. Chat includes the text and summaries of nutrition and sleep. GPS tracks and full heart-rate series are not attached as tracks.
- Weight to Garmin, with its switch.
- Workouts to the Garmin, Suunto or COROS account, with its switch.
- The visible map area, to the tile provider. The backup file, to the destination you choose.
Storage, network destinations and backups are detailed in the repository’s PRIVACY.md. The public policy linked from Play is coach-ia-app.github.io/coach-privacy.