LockIn: tell us what broke.
LockIn has no analytics and no crash reporting SDK. That is a deliberate privacy decision, and it has one honest cost: if something goes wrong on your phone, nothing tells us. This form is the whole reporting pipeline.
What happened?
Half a sentence beats nothing. You do not need to reproduce it, diagnose it, or be polite about it.
Got it.
That is now a ticket in front of the person who wrote the code. There is no support tier and nobody it gets escalated to, so it will be read rather than routed.
You gave an address, so expect a reply if there is anything to say back.You did not leave an address, which is fine, but it does mean this one is a one-way message.
Report something else or read the changelog to see what has already been fixed.
The reports that get fixed fastest.
What you were doing
"I tapped Finish run and it went back to Train without saving." That is enough to find it. The screen you were on matters more than the words for what went wrong.
Whether it happens again
Once is worth reporting. Every time is worth saying so, because a bug that reproduces is usually fixed the same day and one that does not can take a week.
Your phone and version
Some bugs only exist on one manufacturer's Android build. If you can spare the two fields, they rule out half the possibilities.
"This is annoying"
Wording that reads wrong, a button in the wrong place, a nudge that lands at a stupid time. Not bugs, still worth knowing. Most of the app's copy was rewritten because of notes like that.
What this form does with what you type
The boring, honest version.
- ✓What you write is stored on our server and filed as a ticket in the private issue tracker the developer works from, next to the code it is about. It is not a public bug tracker and nobody outside the project can read it.
- ✓Your email address goes on that ticket, so a reply or a follow-up question is possible. It is used for nothing else and is not added to any list.
- ✓The form sends only what you type. It does not read anything from the app, and it cannot: your workouts, food logs and health data never leave your phone. See the privacy policy.
- ✓Do not paste anything you would not want in an email. If a bug involves your own data, describe it rather than attaching it.
Prefer email? support@fitnesslockedin.com reaches the same person, just by way of an inbox instead of a ticket. For a security issue, use email rather than this form and read the security page first, because those deliberately go a different route.
Not in the test yet?
The closed test needs twelve people staying opted in for fourteen days. That is the only thing between LockIn and a public release.