Feature Use Cases

These use cases show practical ways people can use Jornal's main features together. The focus here is on clear workflows rather than edge cases.

Screenshot placeholder Feature overview collage ../../../images/Jornal/screenshots/features-overview-collage.png

Use Case 1: Build a Clear Daily Record

Typical goal: Keep a reliable personal health record without needing to rebuild the day from memory later.

Main features involved:

• Diary
• food logging
• water tracking
• symptom logging
• journal notes
• tags

Typical flow:

1. Open the Diary during the day.
2. Add meals, drinks, or water close to when they happen.
3. Add symptoms when they start or change.
4. Add short notes or tags for context like travel, poor sleep, stress, or exercise.
5. Review the day's timeline later if something needs correcting.

Why this helps: Related entries stay close together in time, which makes later review easier and clearer.

Use Case 2: Track Symptoms with More Useful Context

Typical goal: Capture symptom timing, severity, and nearby context so patterns are easier to review later.

Main features involved:

• symptom logging
• mood and energy logging
• cycle tracking
• medication logs
• notes

Typical flow:

1. Log the symptom when it starts.
2. Add severity and timing.
3. Add nearby context such as stress, mood, cycle timing, or medication timing when relevant.
4. Add a short note if the episode would be hard to remember clearly later.
5. Review the symptom alongside surrounding entries in the timeline.

Why this helps: The record stays focused on observations from the journal instead of guesses made later.

Use Case 3: Keep Medication and Supplement Tracking Practical

Typical goal: Record what was taken, when it was taken, and whether it appeared near symptom or routine changes.

Main features involved:

• Medications
• supplements
• reminders
• adherence logging
• Diary timeline

Typical flow:

1. Add a medication or supplement.
2. Set schedule details or reminders if needed.
3. Mark entries as taken, pending, or skipped.
4. Review timing in the Diary beside symptoms, meals, and notes.
5. Use Insights or Appointment Prep later if the timing is worth discussing with a clinician.

Why this helps: It creates a clearer treatment record without turning the app into treatment advice.

Use Case 4: Review a Week Instead of Reacting to One Day

Typical goal: Step back from daily detail and look for broader observations from the journal.

Main features involved:

• Weekly Summary
• Insights
• symptom burden review
• mood and energy review
• food context review

Typical flow:

1. Open Weekly Summary at the end of the week.
2. Check how many days were logged and what stood out.
3. Open Insights for a wider view if needed.
4. Compare symptoms with nearby food, treatment, mood, cycle, sleep, or hydration context.
5. Save the clearest observations for later discussion or follow-up logging.

Why this helps: Weekly review encourages steadier interpretation instead of overreading a single rough day.

Use Case 5: Prepare for a GP or Clinician Visit

Typical goal: Build a concise, editable summary from the journal for a selected date range.

Main features involved:

• Appointment Prep
• Weekly Summary
• Insights
• notes
• clinician questions
• sharing and PDF export
• optional saved Insight graph pages

Typical flow:

1. Log consistently in the weeks before the visit.
2. Save important notes and clinician questions as they come up.
3. Review Weekly Summary and Insights before the appointment.
4. Open Appointment Prep and choose the date range.
5. Generate and edit the summary.
6. Share the summary or clinician PDF if needed.

Why this helps: It turns a large journal into a more practical discussion document without presenting it as a diagnosis or treatment plan.

Screenshot placeholder Appointment Prep summary editor ../../../images/Jornal/screenshots/features-appointment-prep-editor.png

Use Case 6: Prepare for an Upcoming Event

Typical goal: Keep event-specific planning and review connected to the same health journal.

Main features involved:

• Event Prep
• prep window
• user-set carbohydrate, hydration, or sleep targets
• prep notes
• food, hydration, sleep, workout, and symptom context
• editable Event Prep summary and PDF

Typical flow:

1. Create an event with a start date, event date, type, location, goal note, and focus note.
2. Set your own prep targets when they are useful.
3. Keep event-specific notes near the rest of your diary.
4. Review food logging, hydration, sleep, symptoms, workouts, and prep notes in the dashboard.
5. Generate an editable event summary when you want a clearer record.

Why this helps: Event Prep keeps planning and record-keeping together without turning the app into a coaching or treatment tool.

Screenshot placeholder Event Prep dashboard ../../../images/Jornal/screenshots/features-event-prep-dashboard.png

Use Case 7: Export, Back Up, or Share Records Carefully

Typical goal: Keep records under user control through export, backup, restore, and support-aware sharing tools.

Main features involved:

• Privacy and Data
• export
• backup and restore
• support sharing

Typical flow:

1. Open Settings for privacy, export, or backup tools.
2. Choose whether the goal is export, backup, restore, or support troubleshooting.
3. Create the file or share artifact needed for that task.
4. Review what is being shared before sending it elsewhere.
5. Keep exports and backups only as long as needed.

Why this helps: It keeps the user's records understandable and user-controlled when they need to move or share information.

A Good Support Mindset for These Workflows

When helping someone choose a workflow, it usually works best to ask:

• Are they trying to capture daily events, review patterns, prepare for an appointment, or share records?
• Do they need fast logging, deeper context, or a cleaner summary?
• Do they need a personal record, or something readable to send to someone else?

Those questions usually point to the right feature combination without making the app feel more complicated than it needs to be.