Choose your player tap a card to open their quest board
Route Builder opted-in neighbors build the schedule: 60 min AM + 60 min PM is the goal
Neighbor names and addresses stay in this app for the route only. They are never included in CSV exports or CoreTrack Nexus sync.
Progress per-goal prompt levels: this is your quarterly report data
Exercise Program stays on this device: never exported or baked into a Save File, never synced
StaffSide Duet staff earn points for every documented session
Setup
Players (residents)
Quests (ISP goals)
Exercise Program
Moving to the store app
The app from Google Play or the App Store keeps its own separate data, so nothing carries over on its own. Move a home's data across in four steps.
- On this device, in this web app, tap Export JSON below and save the file.
- Install MileStride from the store on the device the home will use.
- Open it, sign in as admin, then Tools, Import and choose that file.
- Check the player list, then stop using the web app on that device so the two do not drift apart.
Avatar photos and installed exercise programs stay on this device by design. Set those up again on the new device, and record weigh-ins there from then on.
Resident photos
Off by default. A monogram or a plain mark keeps the app initials only, which is what the privacy page promises. A photo never leaves the device, but it is still a picture of a resident sitting on a shared tablet, so turn this on only if the home has permission for it.
CoreTrack Nexus
Linking Nexus IDs connects this device data to real resident records: treat the device as PHI-adjacent once linked (BAAs, device security, MFA on CoreTrack). Sync stays off until you configure it.
Access PINs
When set, the app locks on open and roles limit what is visible: Play (quests only) → Staff (+ progress, exports) → Admin (everything).
PINs are a deterrent, not encryption. Device passcode and full-device encryption are the real safeguard.
Device Security
Condition of use: device passcode, device encryption, auto-lock of 5 minutes or less, and the device stays in facility control. In-app PINs are supplemental, not encryption.
Modules
Future add-on modules plug into the same quest engine and data model.
Privacy & compliance
Initials are not Safe Harbor de-identification. In a small group home, initials plus goal data can identify a person to anyone with context. Treat all MileStride data as PHI-adjacent.