How to use LiftLog V8.5
Help
Start here
A practical walkthrough instead of a checklist.
Sign in with your own name first. From there, the normal flow is Workout, group, exercise, Start Logging, enter the fields shown, and save. If you are doing chest today, you will see set-based fields. If you are doing running, yoga, or mobility work, you will see duration-style fields instead.
A first workout for a new exercise is simply the baseline. Enter what you actually did today, save it, and LiftLog will have something useful to compare next time. The backend decides whether that exercise tracks sets, minutes, distance, or mobility details.
Signing in as the right person
LiftLog is now a shared family-style app with five fixed users: Babak, Dina, Roushanak, Tony, and Qmars. The user you choose at sign-in controls which exercises, workouts, history, progress, coach messages, and settings you see. When you sign in, the app saves that user and PIN for the session and sends both values with every backend request.
Example
Example: if Dina signs in and logs chest exercises, Babak will not see those exercises or sessions after switching back to Babak. Before someone else uses the same phone or browser, tap Switch User and let them sign in with their own name and PIN.
Starting a workout
To train, open Workout, pick the group for the day, then choose the exercise you want to perform. The exercise card is where logging starts. The fields on the logging screen come from the backend exercise schema, so Bench Press can ask for weight and reps while Running can ask for duration and distance.
Example
Example: for chest day, open Workout, choose Chest, choose Bench Press, tap Start Logging, enter something like 135 lb for 8 reps, add the next sets, and save. For running, choose Cardio/Aerobic, tap Running, enter 30 minutes and optional distance, then save.
Bodyweight exercises and blank weight
Some exercises do not use loaded weight. Bodyweight movements focus on reps and optional added weight. Duration, cardio, yoga, and mobility exercises use their own backend-provided fields, such as minutes, distance, pace, calories, difficulty, and notes.
Example
Example: for Push-Ups, enter 20 reps and optionally add 25 lb if you are wearing a weighted vest. For Yoga & Mobility, enter 20 minutes and a short note such as hip mobility or recovery flow.
Changing your PIN
Change PIN is now a direct menu choice below Settings, and it also appears inside Settings. Use it when you want to replace the default PIN or when a user wants a private PIN. The new PIN must be numeric, at least 4 digits, confirmed correctly, and different from the current PIN.
Example
Example: if the current PIN is 12345678, enter 12345678 as Current PIN, choose a new numeric PIN, repeat it in Confirm new PIN, then tap Change PIN. After it succeeds, the app updates the saved session so you do not have to sign in again immediately.
Email settings and coach behavior
Settings are per user. Email updates are optional and require a valid email address before daily or weekly messages can be enabled. The daily option is intended for a training snapshot, while the weekly option is intended for a broader training digest. AI Coach settings also belong to the signed-in user, including whether coach insights are enabled and whether the coach gets summary or fuller history context.
Example
Example: Tony can enable weekly email updates to one address while Qmars keeps email updates off. Those choices do not overwrite each other because they are saved under different users.
Backend status and recovery
After sign-in, the landing page checks the backend and shows whether LiftLog is connected. If the backend is unavailable, retry from the status card before logging important work. If the backend returns an unauthorized response, the app clears the saved session and sends you back to sign-in so the wrong user or wrong PIN is not reused silently.
Example
Example: if the app suddenly asks you to sign in again, choose your user and enter the current PIN. If your workout history looks empty, first confirm the user name shown in the header or sidebar before assuming data is missing.