Native app built, not in the stores yet
The iOS and Android apps are built. They read a completed run from Apple Health or Health Connect and mark the matching planned workout done. They are not listed on the App Store or Google Play yet. Until they are, Pheidi works today as a Progressive Web App (PWA): install it to your home screen for a near-native experience: full-screen with a fast launch. It needs a connection to load your plan; offline use is in the native app.
Install on iPhone
- Open
https://app.pheidi.trainingin Safari - Tap the Share button
- Choose Add to Home Screen
Install on Android
- Open
https://app.pheidi.trainingin Chrome - Tap the menu
- Choose Install app or Add to Home screen
Why a Mobile App
Pheidi works in your phone's browser today. A native app is what can read the health store. Reading a completed run from Apple Health or Health Connect, and marking the planned workout done, is built in the app. Writing Pheidi workouts back to your health profile is not.
The app also keeps working without a connection: it opens your last saved plan, and the workouts you log offline are sent when you're back online (see Phase 4 below). Push notifications are already built but need the native app to deliver them, and the app is not in the stores yet (see Phase 3 below).
How It Works
The mobile app uses Blazor MAUI Hybrid: the same UI you see on the web, running natively on your phone instead of in a browser. Your training plan, calendar, onboarding, and settings look and work the same. The app talks to Pheidi's server via a secure API. When you switch it on in Settings, it reads your phone's health data.
What stays the same
- Same interface, same calendar views, same onboarding wizard
- Same OTP sign-in (email)
- Same training plan engine and calculations
- The web app keeps working. The mobile app is an alternative, not a replacement
Roadmap
Phase 1, Mobile App Shell
The core mobile app: same Pheidi experience, native on your phone. Creating plans, viewing your calendar, logging workouts, and managing injuries and vacations work in the app. It is not listed on the App Store or Google Play yet.
What this includes
- iOS and Android app with the existing Pheidi features
- Secure sign-in via OTP (same email flow)
- Home screen icon with instant launch
- No new Azure infrastructure. The app calls the same server
- Store listing is still ahead
Phase 2, Health Data Sync
In the mobile app, Settings has a card for Apple Health on iOS and Health Connect on Android. Switch it on and Pheidi reads runs from the last 7 days when you open the app or bring it back. A confident match marks the planned workout done. Pheidi does not write workouts back to your health profile. That write path is still planned, and the privacy policy says the app never writes to the health store.
Health platforms
| Platform | Read | Write |
|---|---|---|
| Apple Health (iOS) | Running workouts, distance, duration, heart rate, pace | Planned, not built |
| Health Connect (Android) | Exercise sessions, distance, duration, heart rate | Planned, not built |
How auto-complete works
Pheidi matches a health-store run to a planned workout on the same local day, by how close the distance is. A confident match marks that workout done. A weak match, or two open workouts that both fit, is left alone. Workouts you already logged or skipped are never changed. Runs that match nothing are not stored. You log those by hand.
Phase 3, Push Notifications
The four push notifications are already built. How push notifications work describes each one, including today's run, the evening check-in, a phase change, and the weekly recap. Nothing is sending yet. Delivery stays switched off until a notification hub is configured, and the notifications need the native app, which is not in the stores yet.
Phase 4, Offline Access
Built in the app. When it can't reach Pheidi, the app opens the last copy of your plan it saved on your phone and says you're offline. Logging a workout, recording a run, reporting an injury, and moving or swapping a workout are queued on the phone and sent in order once you're back online. When they land, the plan reloads to show them. Useful for traveling, running in areas with poor signal, or checking your plan on airplane mode.
The queue is sent while the app is open: when the connection returns, on a retry timer, or the next time you open the app. There is no background job that sends it while the app is closed. A change the server refuses is kept, not dropped, so you can retry or discard it. The browser version needs a connection to load your plan.
Relationship to Other Roadmaps
The mobile app is how several still-planned features will reach the phone:
- Heart rate training Phase 3 (wearable integration), will require the mobile app to read HRV and resting HR from Apple Health / Health Connect
- Watch export Phase 3 (Apple Watch support) and Phase 4 (auto-log), the mobile app will enable two-way sync with your watch
| Phase | Feature | Status |
|---|---|---|
| Phase 1 | Mobile app shell (iOS + Android) | Built, not listed |
| Phase 2 | Read runs from Apple Health and Health Connect, mark the planned workout done | Built, waiting on the store |
| Phase 2 | Write workouts back to Apple Health and Health Connect | Planned |
| Phase 3 | Push notifications | Built, not sending |
| Phase 4 | Offline plan access, queued changes sent on reconnect | Built, not listed |
Design Principles
- Web-first, app-enhanced. The browser version isn't going away. The mobile app adds a health-store read and offline use that a browser cannot do. Write-back and push delivery are still ahead. If you prefer the browser, the web app still works.
- One UI, two hosts. The same interface code runs in the browser and the app. What works on web works on mobile.
- Permission, not assumption. Health data access is requested in Settings and explained there. You choose whether to switch it on. Pheidi does not read the health store without that, and you can switch it off or disconnect it in the health app at any time.
- Match, don't nag. Auto-complete marks a run done only when the match is clear. An ambiguous day is left alone for you to log. No prompt asking you to pick a run.
Key Takeaway
The native app is built and not listed in the App Store or on Google Play yet. Until it is, install Pheidi as a Progressive Web App from app.pheidi.training in your phone's browser. You get a home screen icon, full-screen launch, and the same training plan experience. The app already reads Apple Health and Health Connect to mark a planned run done. It also opens your last saved plan offline and sends the changes you made once you reconnect. Writing workouts back is still planned. Push is already built and stays off until a notification hub exists.
The web app is live today, sign in to build a plan.
Research & evidence
Science behind this feature from pheidi.training.
- Wearables and Biofeedback for Injury Prevention Readiness metrics, recovery scores, and what they predict.
- Streaks and Fitness App Retention Why streaks work for adherence and when they hurt.
- Each Hour of Sleep Cuts Injury Risk 43% 2023 meta-analysis on sleep duration and next-day injury rate.
- Sleep Quality Predicts Injury Why 8 fragmented hours is not the same as 8 consolidated hours.
- Sleep and Recovery for Runners Consistent, sufficient sleep predicts injury risk more than most training metrics.
See also
- Heart Rate Training Roadmap Where Pheidi is and where it is going with heart rate-based training. Polarized 3-zone model, wearable readiness, and adaptive intensity targeting.
- How Calendar Export Works Sync your training plan with Google Calendar, Apple Calendar, or Outlook via a live iCal subscription, or download a printable HTML copy.
- How Garmin Watch Export Works Send structured workouts to your Garmin watch with pace targets and interval cues. Export FIT files from any Pheidi workout.