SwiftUI
iPhone, Apple Watch and Mac interfaces adapted to each screen, accessible components and native navigation.
Built inA precise look at the architecture, data trade-offs and Apple integrations. Statuses separate what’s built into the code from what still needs validation on real hardware.
Gymios for iPhone and Apple Watch is available on the App Store. The Mac version will come later.
For the information Apple Health exposes, Gymios treats that source as the reference. Gymios data can fill in a missing field, but it never silently replaces an existing value in Health.
Weight, height, sleep, heart rate, state of mind or workouts are only used after permission, with their date and source.
Bluetooth data, a recognized document or an imported entry keeps its origin. Unverified sensitive values remain to be confirmed.
The Gymios profile and questionnaires only ask for missing information. Declining or skipping a data point doesn’t block the analysis of everything else.
An outdoor activity, a compatible reading or a check-in is only added to Apple Health after the matching permission. Importing a Gymios backup neither changes nor deletes Health data.
| Source | Role | Control | Overwrites Apple Health? |
|---|---|---|---|
| Apple Health | Reference for compatible fields | Apple permissions by category | Not applicable |
| Device or import | Traceable additional reading | Technical and human validation | No |
| Gymios entry | Fills in missing information | Explicit user action | No |
| Gymios analysis | Derived, explainable observation | Time period, sources and coverage visible | No |
Gymios is built as a native SwiftUI app. System integrations are isolated so that a declined permission doesn’t disable modules that don’t depend on it.
iPhone, Apple Watch and Mac interfaces adapted to each screen, accessible components and native navigation.
Built inWorkouts, nutrition, confirmed readings, goals and preferences stay available locally.
Built inReading and writing by category, centralized permissions, origin tracking and no general backup to CloudKit.
Device validationWorkout continuity, planned routes and transfer queues that can wait for the connection to return.
Validation on a real pairGPS track, pace, splits, routes that follow roads, GPX import/export and outdoor activity library.
Long-duration validationOptional sync of explicitly allowed categories in the private database of the Apple Account.
Off by defaultDetection of standardized treadmills, bikes and rowers, without promising compatibility before the model is tested.
Hardware validationOn-device recognition of labels, foods and candidate values, always shown before confirmation.
Built inThe “built in” status describes the available code. It doesn’t replace device testing, manufacturer agreements or the professional validations indicated.
The public community and private coach follow-up are two separate spaces. Turning one on never automatically gives access to the other.
The module stays private and off at first. The user then chooses their username, visibility and each connection.
Settings built inTrophies are only posted after permission. Coach profiles only include the checked categories and flag highly sensitive data separately.
Implemented, service to be deployedThe coach role is a simple declaration. Gymios doesn’t verify qualifications: you only share with someone you know.
ImplementedRecipient, purpose, categories, period and expiration are set before access. Server-side revocation is immediate and cuts off the shared profile.
Policy and service built inThe coach never views Apple Health directly. Profiles are prepared on device from a closed list of allowed categories, then encrypted on a service separate from iCloud.
Each channel has its own allowlist. Turning on a sync doesn’t automatically give access to other categories.
Workouts, nutrition, confirmed readings, goals and working data stay on the device.
By defaultReading or writing only for the categories chosen in Apple’s secure interface.
By categoryRoutines and scheduling; planned routes and GPS history recorded by Gymios only with two separate consents. Outdoor activities imported from Health, heart readings and zones, blood glucose and nutrition are excluded.
OptionalAchievement identifier and completion percentage, with no Health readings or detailed route.
OptionalOnly the barcode is sent over HTTPS to look up the product details.
Third-party serviceNon-medical preferences in iCloud; identity, connections, trophies and coach profiles on a separate service, with sensitive content encrypted at rest. The HTTPS API is deployed; opening awaits Apple’s production setup and moderation validation.
API deployedThe technical documentation separates four levels of evidence. The steps below describe the expected checks; validation on hardware and in distribution is still in progress.
Compile the feature and test its automatable rules.
Check the interface and scenarios locally without sensors.
Test GPS, Watch, HealthKit, Bluetooth, battery life and interruptions on devices.
Check signing, privacy, accessibility and Apple requirements for the distributed version.
Gymios presents personal logs, trends and observations. The app is not a medical device, a diagnosis or a treatment, and doesn’t replace any health, sports or nutrition professional.
The roadmap separates what’s built in, what’s being validated and future ideas.