Most failures are not caused by choosing the wrong app. More often, the right account is signed out, the lift pass is missing, a map was viewed but never downloaded, background location is blocked or the export path was never tested.
Treat setup as a dress rehearsal. Give every important job a primary source, a visible proof that it is ready and, when failure would disrupt the day, a practical fallback.
Your saved setup plan
Entries and checkmarks are stored only in this browser on this device and are not sent to SlopeReady. Print the completed page as a travel sheet or PDF.
Assign every job to a source first
Fill in only the roles you need. One service may cover several roles, provided you understand its limit in each role.
Seven stages to a trip-ready app stack
Complete the stages on the phone and watch you will take. A test on another device with different settings does not count.
1. Confirm the destination and source owner
Every app shows the correct resort, and every important decision has an accountable source.
2. Update, sign in and open the access item
Before departure, you can see the pass, ticket or booking you will need at the destination.
3. Download static information deliberately
Maps, addresses, meeting points and confirmations still open without mobile data.
4. Grant permissions by function
Each app receives only the access required for the job you selected.
5. Prepare connectivity and local help
You know the intended data connection and can find official contacts when coverage is weak.
6. Test power under realistic settings
The phone and watch behave as expected with your recorder, connection mode and power profile.
7. Verify the full recording and data path
A test activity is saved and reaches the place where you plan to analyse it.
- Slopes: current device, GPS, battery and Health guidance, Ski Tracks: offline recording and Health export
- Slopes: current device, GPS, battery and Health guidance
- Apple Support: manage Health data, apps and sources, Apple Support: sync a third-party workout app to Fitness, Ski Tracks: offline recording and Health export
“Offline” describes four different capabilities
Test each row separately. Passing one row tells you nothing about the other three.
On smaller screens, the same information appears as cards.
| Capability | What may work without mobile data | What may still be missing | How to test it |
|---|---|---|---|
| Stored content | a downloaded map, piste plan, address, booking reference or contact | a current closure, lift status, new forecast or changed booking | turn on airplane mode, reopen the app and retrieve the exact item |
| GPS position or recording | the device may continue capturing position and route | map data, syncing, friends or live information | make a short recording with the screen locked and mobile data off |
| Current operations and weather | only the information already loaded | new notices, alerts, cameras and changes | check the timestamp and refresh deliberately after reconnecting |
| Communication | saved numbers and prepared instructions | a call, message, location share, emergency call or help | do not test an emergency call; check the network plan, official demo and a non-digital meeting point |
Stored content
- What may work without mobile data
- a downloaded map, piste plan, address, booking reference or contact
- What may still be missing
- a current closure, lift status, new forecast or changed booking
- How to test it
- turn on airplane mode, reopen the app and retrieve the exact item
GPS position or recording
- What may work without mobile data
- the device may continue capturing position and route
- What may still be missing
- map data, syncing, friends or live information
- How to test it
- make a short recording with the screen locked and mobile data off
Current operations and weather
- What may work without mobile data
- only the information already loaded
- What may still be missing
- new notices, alerts, cameras and changes
- How to test it
- check the timestamp and refresh deliberately after reconnecting
Communication
- What may work without mobile data
- saved numbers and prepared instructions
- What may still be missing
- a call, message, location share, emergency call or help
- How to test it
- do not test an emergency call; check the network plan, official demo and a non-digital meeting point
Apple Support: offline maps on iPhone, OpenSnow: download offline trail maps, Slopes: current device, GPS, battery and Health guidance
Pass two rehearsals before departure
Run both at least once with the final app stack. A critical failure remains a failure until you fix it or define a usable fallback.
Rehearsal A: retrieve it in airplane mode
Pass when you can find the map, address, meeting point, booking reference and local contacts from a cold app launch without a network.
Rehearsal B: record through to the destination system
Pass when the activity is saved and appears where you expect it later, including any required manual export.
Apple Support: manage Health data, apps and sources, Apple Support: sync a third-party workout app to Fitness, Slopes: current device, GPS, battery and Health guidance, Ski Tracks: offline recording and Health export
When a rehearsal fails, narrow the cause instead of hoping
The table points to the next observable check. It does not replace the provider's current support instructions.
On smaller screens, the same information appears as cards.
| What you observe | Check next | Trip fallback |
|---|---|---|
| The pass or booking is missing | account, email address, family assignment, destination, season and blackout date | save the booking reference and the provider's physical or support route |
| The map disappears in airplane mode | download status, selected area, storage and an app restart | also save the official piste plan or another static map |
| Recording stops with the screen locked | background location, watch connection, power mode and current app help | use another verified recorder or skip recording |
| Alerts refer to the wrong place | favourite, coordinates, notification type and old destinations | open the current official page deliberately instead of waiting for a push |
| The activity is in the recorder but not Apple Health | write permission, compatible category, syncing and manual export | keep it in the recorder, note the missing step and inspect the data path again after the trip |
| SlopeReady does not see an expected metric | whether the metric exists in Apple Health and belongs to the allowed read set | work with the available data; do not invent a missing value |
| An emergency or location feature is unavailable | device model, software, country, region, mobile service, open sky and current provider terms | keep official local contacts, the meeting point and known help routes offline |
| Roaming or the eSIM does not work | active line, plan, data roaming, APN or provider activation | use known Wi-Fi points and the fully tested offline fallback |
The pass or booking is missing
- Check next
- account, email address, family assignment, destination, season and blackout date
- Trip fallback
- save the booking reference and the provider's physical or support route
The map disappears in airplane mode
- Check next
- download status, selected area, storage and an app restart
- Trip fallback
- also save the official piste plan or another static map
Recording stops with the screen locked
- Check next
- background location, watch connection, power mode and current app help
- Trip fallback
- use another verified recorder or skip recording
Alerts refer to the wrong place
- Check next
- favourite, coordinates, notification type and old destinations
- Trip fallback
- open the current official page deliberately instead of waiting for a push
The activity is in the recorder but not Apple Health
- Check next
- write permission, compatible category, syncing and manual export
- Trip fallback
- keep it in the recorder, note the missing step and inspect the data path again after the trip
SlopeReady does not see an expected metric
- Check next
- whether the metric exists in Apple Health and belongs to the allowed read set
- Trip fallback
- work with the available data; do not invent a missing value
An emergency or location feature is unavailable
- Check next
- device model, software, country, region, mobile service, open sky and current provider terms
- Trip fallback
- keep official local contacts, the meeting point and known help routes offline
Roaming or the eSIM does not work
- Check next
- active line, plan, data roaming, APN or provider activation
- Trip fallback
- use known Wi-Fi points and the fully tested offline fallback
Open only the next unresolved question
Where SlopeReady belongs in this plan
SlopeReady belongs to preparation and the analysis of existing training and recovery data. It reads only the Apple Health categories you allow and puts the preparation plan in context using the data that is actually available. You can discuss the plan with the AI Coach using your current context; you confirm lasting changes before they are saved.
SlopeReady is not the recorder in this checklist. It does not start or stop workouts, record ski runs, live heart rate, routes or GPS, and it does not write to Apple Health. If you expect a recorded activity to appear in SlopeReady later, your recorder must first make it available in Apple Health and you must allow the relevant read access.
The current Data and Support pages describe Apple Health access, the AI Coach's role and the recording limits. Data in SlopeReady, SlopeReady Support