The Fastly
journal.
A quiet corner for practical ideas, thoughtful reflections, and making Fastly your own.
Your first session in Fastly
A first session is mainly an exercise in understanding the controls.
Read the timer without watching every second
The large timer value is elapsed time.
Choose a goal without choosing a verdict
A goal in Fastly is a timer setting. Treat it as a description of the session you currently intend to record, rather than a promise that every day must resemble the last.
Start now or correct an earlier start
Starting now and backdating a start solve different problems. One begins a new record at the current clock time; the other makes the timer match a session you already began.
Correct a running start time
A forgotten tap can leave the running display shorter than the session you meant to track. Fastly lets you edit the current start without ending and creating a second record.
Stop and save a session
Stopping is the action that turns a running session into a completed history record. Reaching the goal on the display does not perform this action for you.
What happens at goal reached
Goal reached means elapsed time is at least the session's chosen goal.
Change a goal during a session
A change of plan does not require discarding the active timer.
Understand the 16:8 preset label
Fastly maps the 16:8 label to a sixteen-hour goal in its timer. The label identifies a preset; it does not create a personalised eating plan or assess whether that plan suits you.
Understand the 14:10 preset label
The 14:10 option corresponds to a fourteen-hour timer goal in Fastly. Its practical role is to save you from typing a duration when that is the setting you intend to record.
Understand the 18:6 preset label
Fastly uses an eighteen-hour goal for the 18:6 preset.
What the OMAD label means in this timer
In Fastly's preset map, OMAD corresponds to a twenty-three-hour timer goal. That is a specific software mapping, not a meal instruction or a claim about what someone should do.
Set a custom timer goal
A custom goal is useful when a named preset does not describe the duration you want to log. Fastly's interface supports goals from one through twenty-four hours.
Why only one timer runs at a time
Fastly's state contains a single current session. Starting again while one exists does not create another running session, which helps keep the local ledger understandable.
Use Fastly with the screen closed
The running record stores a start timestamp. Elapsed time is derived from the clock, so keeping a brightly lit timer on screen is unnecessary for the record to progress.
Resume after a phone restart
A restarted phone should not require reconstructing a session from memory if Fastly's local record is still present. The app calculates elapsed time from the persisted start.
Record an overnight session accurately
An overnight session spans two calendar dates, but it is still one start-and-end record. Most mistakes come from correcting the clock time without correcting the date.
Keep a factual record on a busy day
A busy day can make exact tapping times easy to miss. A useful record distinguishes the time an event happened from the time you remembered to open the app.
Prepare the timer before travel
Travel adds changing clocks and interrupted routines to a simple timer. A little preparation can make the record easier to interpret when you open it in another place.
Return after a break from tracking
Returning to Fastly does not require filling every day you were away. Begin by understanding what remains on the device rather than trying to manufacture an uninterrupted calendar.
Separate an intention from a timestamp
The goal records an intended duration; the start and end record events. Keeping those concepts separate prevents planning choices from being mistaken for measurements.
A quick pre-session check
A short check before starting can prevent several common corrections later. Focus on the settings that will be copied into the new record, rather than inspecting every page.
A quick post-session check
A post-session check is a chance to catch a missed stop or an incorrect date while the details are fresh. It can be done from the newest item in the Journal tab.
When the timer seems too far ahead
An unexpectedly large elapsed value usually calls for checking the stored start before changing other settings.
When a shorter goal fills the ring instantly
A ring that jumps after a protocol change can be working correctly. Progress is elapsed time divided by the current goal, capped at a full ring.
Find a completed session in the Journal tab
History contains stopped sessions rather than every time you opened Fastly.
Edit a completed start and end
The Edit times action repairs a completed record without replacing its journal or protocol.
Archive a session without losing its note
Archiving removes a completed session from the main history while retaining the record and its journal in Archived sessions.
Restore an archived session
Restoring brings an archived record back into main history. You do not need to recreate the timer or copy its note into a new session to make it visible again.
Archive or delete a record
Archive and delete both remove an item from the main list, but their data consequences differ. Choose based on whether you might want the session and its journal again.
Understand the history ordering
Fastly orders main history with the newest completed sessions first.
Why the session count changed after archiving
The Sessions summary counts main-history records.
Correct a mistaken end date
A session assigned to an unexpected day often has an end date that differs from what you intended. Because history groups by completion, the date matters as much as the hour.
Correct a forgotten stop
A timer left running after the session actually ended overstates the duration you meant to record. Stop the active timer first so there is a completed record to edit.
Keep a test session out of your main view
Exploring an app can create a short test record that you do not want mixed into a personal log. Decide whether that sample has any continuing value before removing it.
Review several sessions from the same day
A calendar day can contain more than one completed record. Fastly does not assume one entry per day, and the weekly chart sums the durations of records ending on that date.
Clear a day filter in Month view
Selecting a day narrows the list beneath the calendar to that date. It can make other sessions look absent even when they remain in main history.
Find an older month
The Month view lets you browse earlier records without scrolling through the entire list. Its arrows change the displayed month and clear any selected day.
Understand an empty history screen
An empty history can have several ordinary explanations: no session has been stopped yet, all visible records were archived, or a calendar selection contains no records.
Why an edited session moved in the list
Editing a completed end changes the value Fastly uses to order history. The record can move even when you only intended to repair a small timing mistake.
Keep notes attached to the right session
A useful note belongs to the session it describes. When several records have similar durations, take a moment to identify the correct entry before opening the journal.
Delete one session carefully
Deleting a session permanently removes that local record and its journal. The confirmation is a useful final opportunity to verify that the selected entry is the one you mean.
Main history and the archive explained
Fastly separates the main history from archived sessions. Both collections can remain on the device, but only main history feeds the standard session summaries and weekly display.
Check a record before exporting
A backup captures the local ledger as it exists at export time. Reviewing recent corrections first can save you from carrying an obvious mistake into the copy you plan to keep.
Recognize a duplicate-looking record
Two similar durations are not enough to prove a duplicate. Repeated routines can produce entries with the same goal, mood, or rounded duration while describing different events.
Record uncertainty in a historical correction
A retrospective correction often comes with imperfect memory. The note can preserve that limitation so a precise-looking timestamp does not imply more certainty than you had.
Review a long record before deleting it
An unusually long record can be a forgotten stop, a timing error, or an accurately recorded event. Its unusual size is a reason to inspect it, not an automatic reason to erase it.
What remains with an archived journal
A session's note, mood, and optional weight belong to the record. Moving that record to the archive does not deliberately create a stripped-down copy containing only its duration.
Review your ledger before a fresh start
A fresh start can mean changing today's settings, reorganizing history, or erasing data.
Trace a missing session step by step
A missing session is easiest to investigate by narrowing the possibilities. Start with view state, then record placement, and only then consider data replacement or deletion.
Write a useful one-sentence session note
A useful session note gives future you one piece of context that the timer cannot store on its own. It need not be a full diary or an explanation for every decision.
Choose a mood label with context
Fastly offers Calm, Good, Tired, Hungry, or no mood selected. These are simple journal labels, so choose the closest useful description without treating the menu as an assessment.
Leave the mood field blank intentionally
No mood selected is a valid choice. You may not remember a useful label, may prefer words in a note, or may simply want to record timestamps alone.
Separate an observation from an explanation
A note is easier to interpret when it distinguishes what you noticed from what you think may explain it. A personal record alone cannot establish a cause.
Use the optional weight field carefully
Fastly's journal has an optional weight field labeled in kilograms. It stores the value with that session; it does not create a medical interpretation from the number.
Remove an optional weight entry
An optional measurement can be removed without deleting the entire session.
Fix an invalid weight message
The journal requires a positive finite numeric weight when the field is not blank. A validation message does not mean the rest of your session has disappeared.
Keep a note under the character limit
Fastly allows notes up to 5,000 characters. A focused entry usually needs much less, but the limit matters when pasting a long reflection or importing a backup.
Build a simple context vocabulary
A few consistent words can make notes easier for you to scan. They remain ordinary text in Fastly; they do not create automatic tags, filters, or analysis.
Write a travel context note
Travel notes are most useful when they describe the particular disruption: a changed local time, a missed reminder, or an estimated start.
Save a daily check-in without a session
Your daily journal can hold a mood and a private thought even when you are not running a fasting timer.
Note water without setting a target
The optional water counter records glasses you choose to note, without prescribing an amount for your day.
Use a retrospective note without rewriting history
Writing about a session days later can be useful, but memory and contemporaneous recording are different sources of information. Make that distinction visible in the wording.
Use a two-line reflection format
A compact reflection can separate the event from the next practical question. Two lines are often enough: one for what happened, one for what you want to consider next time.
Keep a journal without recording weight
The note, mood, and weight fields are independent choices. You can keep a rich contextual journal while leaving the optional measurement empty on every session.
Keep a timer log without journaling
A timer-only log is a valid use of Fastly. Start and end timestamps can be useful even when you do not want to record a mood, reflection, or optional measurement.
Review notes without judging their tone
A journal written during a difficult or hurried moment may sound different from one written calmly.
Review a week of notes manually
A weekly review can begin with notes rather than totals.
Protect other people's details in notes
A personal session journal may accidentally accumulate names, locations, or conversations that are unnecessary to understand the timer.
Understand what mood labels cannot tell you
A selected mood is a subjective label attached to one record. The app offers a small menu, so the available word may only approximate what you meant.
Edit a journal without changing the timer
Journal editing changes descriptive fields while preserving the session's timing information. You do not need to alter start or end merely to correct a typo or add context.
When a journal will not save
A failed journal save can result from invalid optional weight text or a device-storage problem. Read the actual message before changing a note that may already be valid.
Record a changed goal in your note
Changing a goal during a session updates the stored goal, but it does not add a narrative explaining your decision. A short note can retain that missing context.
Choose what not to journal
A deliberate journal can leave some information out.
Prepare a note for sharing with a professional
If you choose to discuss a log with a qualified professional, clarity matters more than elaborate interpretation.
Read the last seven days chart
The week chart shows time tracked per day across the last seven local dates. Each bar comes from completed main-history sessions whose end falls on that date.
Why overnight time appears on one day
Fastly uses a session-based daily chart rather than splitting elapsed time at midnight. A completed record belongs to its local end day, including the portion before midnight.
Understand rounded hour labels
The small hour label above a weekly bar is rounded for compact display. Individual session durations use hours and minutes, so the two views can show different levels of detail.
Why bar heights change from week to week
The week chart scales bars relative to the largest value in the displayed seven days, with a minimum scale.
An empty bar is not a complete account of a day
A zero or dash in the chart means no completed main-history duration was counted for that date. It does not explain what happened outside the app.
Read the Sessions summary
The Sessions summary counts completed records in main history. It is a count of entries, which differs from the number of calendar days with entries or the number of goals reached.
Read the Time tracked summary
Time tracked adds the durations of completed main-history records.
Understand Current rhythm
Current rhythm counts consecutive local end dates with at least one main-history session that met its own goal. The run must end today or yesterday to remain current.
Why the current rhythm can change after an edit
A timing correction can change whether a record meets its saved goal or which local date contains its end. Either change can affect the consecutive-day calculation.
Compare two sessions with different goals
Two durations can be compared as time values even when their completion markers differ.
Compare a quiet week and a busy week
A week with fewer entries may reflect changed circumstances, less tracking, or a deliberate break.
Use the month calendar as an index
The calendar is a way to locate sessions by completion date. A marked day indicates that main history contains a session there; the marker is not a graded result.
What a goal marker does and does not mean
A goal marker tells you that elapsed time met the goal stored with that record. It is a comparison between two app values, not a separate sensor measurement.
Review a chart after restoring an archive
Restoring a session adds it back to the main-history dataset. If its end date is in the visible week, the corresponding bar can increase immediately.
Distinguish a rolling week from a calendar week
History's last-seven-days chart covers today and the six previous local dates. It is a rolling window, so it does not always begin on Monday or coincide with a calendar week.
Read one unusually tall bar
A tall bar is an invitation to inspect the records behind it.
Use chart values instead of visual estimates
A bar's height is useful for a quick impression, but it is an imprecise way to compare durations. Compact labels and changing scales add another layer of approximation.
Spot a recording issue through notes and charts
Charts can help you locate an unexpected duration; notes can explain whether it reflects an actual event or a recording problem. The two views are most useful when read together.
When the weekly total seems too high
A high total can come from more than one completed session per day, a forgotten stop, or an end date you did not expect. Begin with records rather than the bar's appearance.
When a completed session is not in today's bar
A completed session belongs to its local end date, which may differ from the date you expected. It may also have been archived or ended outside the chart's rolling window.
Set a question before reviewing statistics
Statistics become more useful when you decide what you want to learn from them.
Compare records before and after a routine change
A routine change often alters goals, recording frequency, and daily context at the same time. Those differences matter when you compare older and newer sessions.
Why totals change when you delete a record
Deleting removes a session from the local collections rather than merely hiding its row. Any main-history summary that included the record can therefore change along with the list.
Use a chart screenshot with enough context
A screenshot preserves a view at a moment, but it may omit the definitions needed to interpret it.
Keep statistics proportional to your purpose
Fastly's statistics summarize a small set of recorded fields.
Turn on goal reminders deliberately
Goal reminders are opt-in in Fastly.
Turn on a start reminder
Time to start is a local nudge for the next session. The controller schedules it when no session is running, using the chosen Start time setting.
Set quiet hours across midnight
Quiet hours can span midnight, such as an evening From time and a morning Until time. An alert inside that interval is moved to the next end of quiet hours.
Set a daytime quiet interval
Quiet hours need not represent nighttime. They can cover a daytime period when you want Fastly's locally scheduled reminders held until the interval ends.
Why a goal alert arrived after the ring filled
A filled ring and a delivered notification use related but different processes.
Check all reminder controls together
A reminder depends on more than its individual switch. Fastly has an All reminders control, separate goal and start choices, a chosen start time, and optional quiet hours.
Use the app without notifications
Notifications are optional. Fastly's timer and local history can still serve as a manual record when you prefer to open the app on your own terms.
Distinguish goal alerts from automatic stops
The Goal reached notification announces a time marker. It does not call the stop action, write a completed end, or create a History record by itself.
Refresh reminders after a time-zone change
Changing time zones can change the local clock context around reminders. Fastly's reminder page advises reopening the app after the change so alarms can be refreshed.
When notification permission is denied
If the operating system denies notification permission, Fastly cannot reliably present its local reminder through that permission gate.
When an enabled reminder is silent
A visible notification can be silent by design. Fastly's goal chime is optional and off by default, while device sound and focus settings can impose additional behavior.
Turn off all reminders for a while
The All reminders switch is a convenient way to pause Fastly's scheduled cues while keeping your timer and journal workflow available.
Choose a start time that fits your calendar
Start time is a reminder preference, not an appointment the app can enforce. Choose it as a convenience for the occasions when a nudge is useful.
Keep a reminder from becoming a rule
A notification can feel more authoritative than the setting behind it. In Fastly it is simply a locally scheduled message based on your chosen time or goal.
Why no start alert appears during a session
Fastly schedules the start reminder only when there is no current session. During an active session, the relevant optional reminder is Goal reached instead.
Why changing the start moves the goal alert
The goal instant is calculated from the active start plus the selected goal duration.
Why changing a goal moves its reminder
An active goal reminder follows the current selected duration.
Understand equal quiet-hour times
The controller treats identical From and Until values as no quiet-hour shift. Equal clock times are not implemented as an all-day silence interval.
Test reminder settings without distorting history
Checking notification controls does not require creating misleading session records.
Investigate a reminder after battery restrictions
Operating-system battery rules can delay notification delivery even when Fastly has scheduled a local reminder. The in-app reminder page explicitly notes this limit.
Separate Fastly quiet hours from system focus
Fastly's Do not disturb setting moves its own scheduled alerts to the end of a chosen interval.
Adjust reminders after a routine change
A changed schedule can leave reminder preferences out of step with your intentions. Review cues as practical settings rather than carrying them forward automatically.
Recover from an accidental reminder change
An accidental reminder switch changes future scheduling preferences, not the events already saved in the Journal tab. Correct the preference without editing completed session times.
Choose quiet feedback for a shared space
In a shared office, bedroom, or public setting, sound and vibration choices may matter more than the timer's appearance. Fastly lets you review those controls separately.
Use reminders as part of a flexible routine
A flexible routine can include cues without treating every cue as a commitment. The useful question is whether a reminder helps you make a deliberate recording choice.
What local-only means in Fastly
Fastly stores sessions, journal fields, and settings on the device. This release does not require an account and does not keep a custom-server copy of your fasting records.
Export your first JSON backup
A JSON backup is the restorable copy of your Fastly records. It includes the current session if present, main history, archived sessions, journals, and supported settings.
Import replaces rather than merges
Fastly's import is a replacement operation. It loads the backup dataset as the local state instead of adding those records alongside the ones currently on the device.
Move your ledger to a new phone
Moving Fastly data is a manual file transfer, because there is no account or automatic server copy. Keep the old device's records until the new device is verified.
Back up before reinstalling
Reinstalling can remove local app records. A reinstall is therefore a poor first step for troubleshooting unless you have already preserved the data you want to keep.
Back up before erasing local data
Erase local data removes sessions, journals, and settings from this device. Exported files are separate copies and are not removed by that in-app action.
Understand readable backup data
A Fastly backup is JSON text rather than an encrypted vault format. It can contain session timestamps, notes, mood labels, optional weight, and supported preferences.
Choose a backup destination
The system share sheet offers destinations, but the choice remains yours. A useful destination is one where you can find the file later and understand who has access.
Keep more than one dated backup
A small set of dated backups can preserve different points in your ledger. It helps distinguish a recent complete copy from an older file made before important corrections.
Validate a backup before replacing records
Fastly checks the file format and supported fields before accepting an import. You can also reduce mistakes by checking that you selected the expected file from the expected date.
Why an import may be rejected
A rejected backup may have the wrong structure, an unsupported version, invalid record fields, or excessive size.
Recover after selecting the wrong backup
If you have not confirmed replacement, cancel and choose the intended file. If replacement already completed, the next step depends on which other exported copies you kept.
Why a share image is not a backup
A progress image is a PNG designed for a chosen visual summary. A JSON backup contains structured session records and settings that the importer can read.
Understand the backup's current session
A JSON export can include an active session as well as completed history. The active record has a start and no end, which lets the restored state represent a still-running timer.
Which settings travel in a backup
Fastly includes supported appearance, accessibility, reminder, feedback, and marker preferences in its backup.
What SQLite storage means for your ledger
The active app opens a private local SQLite database and stores the fasting ledger as a snapshot.
A privacy check before exporting
Exporting changes the boundary of the data: information that normally stays in the app becomes a file sent to a chosen destination.
Understand the boundary of local erasure
The in-app erase action targets local sessions, journal, and settings. It does not know every location where you may have saved or shared an exported copy.
Use Fastly without an account
This release's active workflow goes from onboarding to the home screens without requiring an account.
Understand external help and store links
Opening a help or store link leaves the app's local record workflow and visits a third-party service. The destination has its own privacy policy and request behavior.
Restore after local data was cleared
After local records are removed, Fastly cannot fetch a hidden server copy. Recovery depends on a JSON backup you exported before the clearing occurred.
Why backups do not synchronize devices
A backup is a snapshot made at one moment.
Check a restore without erasing the source
The safest moment to verify a device transfer is while the original records and exported file are still available.
Keep backup filenames meaningful
A meaningful filename helps you choose the right dataset before an import replaces local records. The default export name includes a date, which is a useful starting point.
A local-data checklist for a lost phone
A lost phone puts the local ledger and any files on that device out of reach. Focus on copies you deliberately exported, rather than expecting a sign-in to recreate the records.
Choose a light or dark theme
Fastly offers Light, Dark, and System appearance choices. Light is labeled Paper Studio and Dark is Quiet Orbit; System follows the device's current appearance.
Use System appearance intentionally
System mode links the app's light-or-dark presentation to the device.
Try the Minimal orbit style
Minimal orbit changes the timer ring to a finer visual line. It is an appearance preference, separate from the duration being recorded and the goal comparison.
Increase the timer numerals
Larger timer numerals is a focused accessibility preference for the main time display.
Use the high contrast ring preference
The High contrast ring preference adjusts the timer's visual contrast.
Reduce navigation motion
Reduce motion lets Fastly skip navigation fades and reduce animated presentation. It can be used independently of the timer goal, journal, or reminder choices.
Follow device motion preferences
Accessibility's Follow system setting lets Fastly honor device motion and bold-text preferences.
Use bold text where it helps
Bold text is a display preference for readers who find heavier lettering useful. Fastly can honor the device's bold-text request and offers its own switch in Accessibility.
Adjust device text size with Fastly
Fastly follows device text size, so broader text scaling is controlled at the operating-system level. The app's Larger timer numerals option provides an additional targeted choice.
Read timer status in words
Fastly's timer includes a semantic description of elapsed time and goal, and its accessibility page states that status does not depend on color alone.
Check a screen-reader timer workflow
A screen-reader workflow should make the main action and current state understandable together.
Choose feedback without vibration
Vibration feedback is optional in Sound & haptics. You can turn it off while continuing to use the timer, journal, and history normally.
Distinguish feedback sounds and goal chimes
Sound & haptics contains separate choices for general sound effects, the goal chime, and the milestone chime. One switch should not be assumed to control every kind of sound.
Create a calm display setup
A calm interface setup can combine a readable theme, suitable text, less motion, and optional feedback.
When a theme changes unexpectedly
If Fastly switches between light and dark, check whether Appearance is set to System.
When a setting will not stay saved
Fastly reports a setting-save problem if the device preference cannot be written.
Review accessibility after importing settings
A backup can restore accessibility preferences from another device or an earlier setup.
Use a fixed theme for predictable screenshots
System appearance can change a screenshot's palette based on the device state. If you need a consistent visual reference, a fixed theme makes the presentation easier to reproduce.
Combine minimal style and readable status
A minimal ring can reduce visual detail, while a high-contrast preference and larger numerals can emphasize key information. These controls serve different aspects of readability.
Make History easier to scan
History offers List, Week, and Month because different tasks benefit from different views.
Separate text size from image export width
Larger app text and a higher-resolution shared image are different settings. Device text scaling affects the interface, while the sharing screen lets you choose a PNG width.
Use a smaller set of settings changes
When several preferences change at once, it can be hard to know which one helped. A small, deliberate adjustment makes the app easier to tune to your needs.
Know which preferences do not change records
Theme, ring style, text, motion, and optional feedback choices affect how Fastly presents information. They do not rewrite the stored start and end of existing sessions.
Check the app in your usual environment
A settings preview is useful, but the everyday environment determines whether you can comfortably read and operate the app. Review your actual screens where you normally use them.
Keep a comfortable setup after a device change
A new device can change screen size, system text scaling, motion requests, sound behavior, and notification permission. A restored settings file is only one part of that setup.
Add a Fastly Home Screen widget on iPhone
Fastly's mobile widget can put the local timer on the Home Screen. The app's widget guide specifies iOS 17 or later and offers Small or Medium Home Screen sizes.
Add the circular Lock Screen timer
The iOS Lock Screen option gives the timer a compact circular presentation. Fastly's guide lists this alongside its Home Screen widgets for supported mobile devices.
Add the Android timer widget
Android's Fastly Timer widget offers a Home Screen view of the local timer. It reads this device's session state rather than retrieving an account-based record.
Why widget refresh is not instant
Widgets are rendered and refreshed under operating-system rules.
Choose Small or Medium on iOS
Small and Medium Home Screen widgets are layout choices in the supported iOS widget guide. The useful choice depends on available space and how easily you can read the timer.
Resize an Android widget thoughtfully
Android widget sizing depends on the launcher. Fastly's guide suggests dragging Fastly Timer onto the Home Screen and resizing it, so inspect the result in your own setup.
When a widget shows an old session state
An old-looking widget can result from delayed system refresh rather than an incorrect local record.
Why desktop has a different widget guide
Fastly's desktop widget page recommends keeping its resizable window nearby.
Keep widgets and backups conceptually separate
A widget is a presentation of the local timer.
Choose what to share from Fastly
The Share screen offers Session, Rhythm, and This week. These select different quantities for the visual, so choose the one that matches what you intend to show.
Share the current session as an image
A Session image uses the active record when a timer is running. The displayed value is elapsed time at the preview moment, not a final completed duration.
Share the latest completed session
When no session is currently active, Session uses the newest completed main-history record.
Share a rhythm summary with context
Rhythm creates an image from the Current rhythm day count.
Understand the This week sharing total
This week on the Share screen sums completed main-history sessions ending within the recent seven-day interval. It displays total duration and the number of included sessions.
Choose Square, Story, or Landscape
Share formats change the image's aspect ratio: Square is 1:1, Story is 9:16, and Landscape is 16:9. The content choice remains Session, Rhythm, or This week.
Choose 1080 px or 2160 px
Fastly lets you export the progress image at a selected width of 1080 or 2160 pixels. This affects image dimensions, while the format determines its proportions.
Preview personal information before sharing
Fastly excludes the journal from its progress image, but the visible summary can still be personal.
When image export fails
The Share screen renders its preview to a PNG before handing it to the system share sheet.
Cancel a share without changing your record
Opening the system share sheet is not a requirement to send a file. You can cancel if the destination, preview, or amount of information is not what you intended.
Understand the Ready share preview
If there is no current session and main history is empty, Session shows a Ready-style preview rather than an invented completed duration.
Share a visual without sharing the journal
The built-in PNG deliberately excludes journal fields.
Use a widget as an entry point
A widget can reduce the effort of finding Fastly without needing to become a constant display you monitor. Its useful role may simply be opening the current timer quickly.
Review widget privacy on a shared device
A widget can make timer information visible to someone looking at the Home or Lock Screen. Consider that display choice separately from the fact that records are stored locally.
Check a share after correcting a record
A newly exported progress image reflects the current eligible record or summary. An image you exported before a correction remains an older static copy.
A quick mobile widget troubleshooting path
Widget troubleshooting is easiest when you separate installation, placement, refresh, and actual timer data. Each problem points to a different part of the workflow.
No notes here just yet.
Try another category or a shorter search.
Save an article with its bookmark button to find it here later.
Clarity, without the promises.
These notes explain Fastly's tools and offer reflection prompts. They do not diagnose, prescribe a fasting schedule, or promise a health outcome.