Trig is made by one person. Email gets read, and questions about the app usually get an answer within a couple of days.
For bug reports, please include your iPhone model, your iOS version, and what you were doing when it happened. That is usually enough to find it.
On first launch Trig asks about your race, what you are running now, roughly how fast you are, and which days you can train. Five screens. Nothing asks for a weekly mileage total, because most runners do not carry one in their head.
If you let Trig read Apple Health, it fills most of that in from your last eight weeks of runs. Every pre-filled answer stays editable — you know things the data does not, like a move or a layoff.
Trig asks the first time you use something that needs it, never on launch. Access is read-only, and the app holds no permission to write to Health at all.
Only used to notice when something clashes with a planned session. Trig never adds, edits, or deletes an event.
Used to look up the temperature and dew point where you run. Decline it and Trig still builds and adapts your plan — you lose the heat guidance, not the app.
Your training paces come from one thing: the fastest hard effort Trig knows about, either the one you entered or the best qualifying run in your Health history. Everything else is derived from it, so a wrong input there moves every session.
If the paces look far off, check that number first — an easy run logged as a hard effort, or a walk recorded as a run, will drag the whole plan slow.
Race date, distance, goal, and available days can all be changed after the plan exists. Trig rebuilds the block around what is left of the runway rather than trying to keep the old shape.
If the time you want is further away than the training runway allows, Trig will say so once, with the numbers, and let you choose what to do about it. It will not quietly build something else and let you find out on race day.
Trig reads completed runs from Apple Health rather than recording them itself, so a run has to be in Health before Trig can see it.
Runs already recorded before you installed Trig are picked up too, going back eight weeks.
Trig has no account and no server. Everything lives in a single file on your iPhone, and deleting the app deletes it. Your Health and Calendar data belong to those apps and are untouched — Trig only ever read them.
Full detail is in the privacy policy.
Trig is the same app, renamed and expanded. The heat model is unchanged — the same maths HeatPace shipped with. Everything else was built around it: the training plan, the coach, calendar-aware rescheduling, race prediction, and readiness.
Updating from HeatPace keeps your data. There is nothing to migrate.
Both go to the same address, and both are genuinely welcome. Trig is early, and the useful reports so far have all come from people describing what they expected to happen and what happened instead.