BubBasic support.

BubBasic is a care log, not an emergency or medical service. For urgent health concerns, contact an appropriate health professional or emergency service.

Logging and timers

What can I track?

BubBasic records sleep, nursing, bottle feeds, nappies, pumping, solids, medicine, temperature, growth and baths.

Choose a child on Today, then use the quick-add tiles or More menu. Tap an existing entry to review or edit it.

Can I log something from yesterday or correct its time?

Yes. Every log sheet includes date and time controls. A start or end cannot be in the future, and an end cannot be earlier than its start. A valid session may cross midnight. Editing keeps the same entry identifier and child.

If the time is invalid, BubBasic shows an inline explanation and does not save until you correct it.

How does the nursing timer work?

Start on the left or right side, switch sides as needed, pause and resume, then finish. BubBasic stores each transition so the timer can survive the sheet closing, backgrounding and a force-quit. Manual nursing entries remain available for historical logs.

Only one nursing session can be active for each child.

How do I stop pumping or sleep?

When pumping is active, the Pump tile becomes a one-tap Stop action. BubBasic keeps the recorded duration and leaves volume fields editable. Only one pumping session can be active at a time.

Use the active Sleep control in the app or a configured widget to stop an ongoing sleep.

How do I delete one entry?

On Today, swipe the entry, choose Delete, then confirm. From Today or Day Report, you can instead open the entry and use its delete action.

An unsynced entry is removed locally immediately. An entry that has synced is also queued for safe deletion from iCloud. BubBasic keeps no care payload in the deletion marker.

Why does sleep appear on two days?

A sleep that crosses midnight contributes only the intersecting time to each day. Day Report shows the continued segment on both days, while CSV export preserves the original full session.

Home Screen widgets and Shortcuts

How do I add and configure a widget?

1. Long-press an empty area of the Home Screen and choose the control to add a widget.
2. Search for BubBasic and add Status or Quick Log.
3. Long-press the installed widget, choose Edit Widget, then select the child it should display and log against.

Different BubBasic widgets can use different children. If a selected child is archived or deleted, the widget asks you to choose another child rather than logging against someone else.

Will the displayed time keep updating while the app is closed?

Completed events use iOS relative-date text and an active sleep uses an iOS timer, so visible time can advance without continuously running BubBasic. The widget reloads after real changes and requests a sparse safety refresh.

iOS controls widget budgets and exact refresh timing, so an occasional delay is expected.

Why is a widget empty or stale?

Open BubBasic once to refresh shared state and confirm that the widget still has a child selected. Missing or unreadable live data produces an empty state that asks you to open the app instead of showing fictional or stale care information.

If an action reports failure, open BubBasic and resolve the displayed storage or account error before trying again.

What does the Nappy action log?

The Nappy tile opens the type-choice sheet. Choose Wet, Dirty, Both or Dry before saving. BubBasic Shortcuts expose the same four choices.

Reports, children and growth

Can I track more than one child?

Yes. Add and manage children in Settings > Children, switch the active child on Today, and configure widgets independently. Archiving removes a child from everyday selection without deleting the history.

How do Day Report and Trends work?

Day Report shows the selected day's entries and clipped daily totals. You can edit entries or share a plain-text summary.

Trends gives neutral facts such as date range, sleep averages, feed counts, bottle volume and nappy counts. Last Feed and Last Nappy look across the full history rather than resetting at midnight.

What do the growth curves mean?

BubBasic uses bundled official World Health Organization female or male reference tables for weight, length and head circumference from birth through 24 months. The Growth reference setting selects the comparison curve only; it does not define a child's identity.

Choose Not Set to keep raw measurements without percentiles. After 24 months, BubBasic shows raw measurements.

Growth references are for context only and are not medical advice. A percentile does not diagnose a health issue.

Import, export and sharing a report

How do I bring history from Huckleberry?

1. Request a CSV export in Huckleberry and save it to Files.
2. In BubBasic Settings, choose the Huckleberry import action and select the file.
3. Review the preview before confirming the import.

The file is processed on the iPhone. Re-importing does not deliberately duplicate the same records, and an entry previously deleted in BubBasic is not restored under its old identifier.

How do I export my data?

Use Export in Settings to create a portable CSV for a selected child. BubBasic presents the standard iOS share sheet so you choose where it goes. Export is not capped. A Day Report can also be shared as a readable text summary.

Open the exported file and check it before relying on it as a backup.

Does BubBasic upload an imported or exported CSV?

No. Import uses the iOS document picker and processes the selected file locally. Export creates a file locally and gives it to the destination you choose through the share sheet. The BubBasic app has no developer server to receive either file.

Files, Mail, AirDrop and other destinations apply their own privacy practices after you choose them.

iCloud sync and co-parent sharing

Is iCloud sync required?

No. Sync is off by default and BubBasic works locally without it. Turning sync on uses the Apple Account already signed into the iPhone; there is no BubBasic account.

Accepting a sharing invitation is the only other path that turns sync on. BubBasic explains before acceptance that the invitation turns on iCloud sync for the shared child.

Who can see a shared child?

Only the owner and people invited through Apple's private CloudKit sharing can access that child. Accepted participants can see and change the shared care history. The developer cannot inspect the records or sharing URL.

How quickly should a co-parent see a change?

Changes are usually delivered promptly, but iCloud, network state, power conditions and background scheduling can introduce a delay.

BubBasic shows Synced only after a successful fetch and application with no failed durable changes. Opening the app and allowing a moment online can help after a device has been offline.

How do I stop sharing?

An owner can revoke a participant from the child's sharing controls. A participant opens the child in Settings > Children and uses Leave shared child. Leaving or revoking removes access; it does not transfer ownership.

Deleting the complete iCloud copy also exits shares owned by other people and deletes every child zone and share you own.

What happens if I sign out of iCloud or change Apple Accounts?

Whenever BubBasic opens or returns to the foreground, it closes widget and iCloud routes before checking the Apple Account. If the check is temporarily inconclusive, shared children remain hidden and widget actions and iCloud changes remain blocked until Retry succeeds.

After a confirmed sign-out or Apple Account change, BubBasic removes known shared-in caches from that iPhone and keeps known owned history as a detached local copy. It does not upload detached history unless you separately choose Upload This Local Copy for the verified Apple Account.

Why are some v1.1 histories hidden?

BubBasic v1.1 did not save enough local account information to classify every child history safely during the v2 upgrade. BubBasic removes known shared-in caches from that iPhone, keeps known owned history as detached local copies, and hides histories it cannot classify.

Settings > Sharing shows only the number hidden, without showing names. Choose Keep on This iPhone to reveal and retain them as detached local data. This does not turn on sync or upload anything. To sync or share that history later, separately choose Upload This Local Copy for the verified Apple Account.

What if BubBasic cannot read its iCloud account metadata?

This is separate from an unreadable care-history file. If both copies of the iCloud account metadata are unreadable, BubBasic makes no ownership assumption: all child histories remain hidden, widgets stay empty and iCloud actions are blocked.

Use Retry first. If no readable copy can be recovered, review Data Management. Erase Data on This iPhone permanently removes the local app data and backup, widget snapshot, sync metadata and pending changes, then returns BubBasic to onboarding. It does not delete the iCloud copy.

What if iCloud encrypted keys are reset?

BubBasic treats an encrypted-key reset differently from an intentional deletion. An owner can choose Keep Local Only or Rebuild iCloud from This iPhone. A participant needs a new invitation from the owner. BubBasic does not silently recreate a deleted zone.

Storage and recovery

Where is local history stored?

BubBasic keeps a versioned JSON snapshot in private App Group storage shared only with its widget extension. It coordinates changes, validates the new snapshot and rotates a valid local backup before replacement.

What happens if the local file cannot be read?

If the primary file is unreadable and its backup is valid, BubBasic restores the backup and warns that recent changes may be missing.

If neither can be read, BubBasic blocks writes so it cannot overwrite recovery evidence. The recovery screen offers Retry, Share Recovery Files, Restore from iCloud when eligible, or an explicit Start Fresh action.

Save recovery files somewhere you control before choosing Start Fresh. Do not email a recovery file as an ordinary support attachment.

Complete data and deletion guide

Local data, owned iCloud data, access to a child shared by someone else, device backups and exported files are separate copies. Removing one does not silently remove the others.

There is no BubBasic account to delete. Optional sync uses the Apple Account already signed into the iPhone. The developer cannot look up or erase private CloudKit records for you.

Before deleting anything

1. Export a CSV for each child whose history you may need.
2. Save each file somewhere you control.
3. Open each exported file and check it before continuing.

An iCloud deletion acknowledgement is not an archive.

Delete one entry

1. Find the entry on Today or Day Report.
2. Swipe on Today and choose Delete, or open the entry and use its delete action.
3. Confirm the destructive action.

An unsynced entry is removed locally immediately. If it has synced, BubBasic removes the local care payload and keeps a payload-free deletion operation until iCloud acknowledges it. A minimal server marker prevents an old device from restoring the care record.

Delete a child

Open Settings > Children, choose the child and read the confirmation:

• Local-only child: removes the child and entries from this local data set.
• Owned synced child: records a marker without a child name, date of birth or care payload, then deletes the child's iCloud zone and share after acknowledgement.
• Child shared by someone else: use Leave shared child instead of deleting the owner's records.

Delete every owned iCloud copy

1. Make sure the iPhone is online and signed into the intended Apple Account.
2. Open Settings > Data Management.
3. Choose Delete iCloud copy.
4. Read the confirmation, which explains that owned history stays on this iPhone, then confirm.
5. Keep BubBasic open, or return when prompted, until it reports completion.

This action confirms a private reset marker, deletes every child zone and share you own, exits every share owned by someone else, removes those shared-in cached children and turns sync off. Completion appears only after all server deletions succeed. Owned local history remains automatically as a detached local copy.

Erase data on this iPhone

Use Settings > Data Management > Erase Data on This iPhone to remove BubBasic's local app data and backup, widget snapshot, sync metadata and pending journal from that iPhone. The app then returns to onboarding.

This action does not delete anything from iCloud. If you want both copies removed, complete Delete iCloud copy while online, verify its completion, then erase data on the iPhone.

Removing the app alone is not a reliable request to delete CloudKit records or copies retained in an Apple-managed device backup. Use the in-app controls before uninstalling.

Stop sharing without deleting every owned iCloud copy

• Owner: revoke a participant in the child's sharing controls. The owner's records remain.
• Participant: use Leave shared child. The owner's records remain.

A participant may still have a file, report or screenshot previously exported or shared elsewhere. BubBasic cannot delete files from another person's destinations.

Backups, exports and shared files

iPhone backups are managed through Apple device and Apple Account settings. CSV exports, recovery files, text reports and screenshots are ordinary files after you share them.

Delete those files from every destination where you saved or sent them. Apple's backup controls are explained in Apple's iCloud support.

If deletion cannot complete

Confirm network access and the intended Apple Account, then retry. Do not switch accounts or choose Start Fresh while an iCloud deletion is pending.

If BubBasic reports an encrypted-key reset, an owner can keep local data only or rebuild iCloud from that iPhone. A participant must ask the owner for a new invitation.

For help, send the exact non-sensitive error message, app version and build, iOS version and iPhone model to sjmeehan9@gmail.com. Do not attach a CSV, recovery file, child name, record identifier, sharing URL or screenshot containing private data.

Support can explain the on-device steps but cannot perform deletion remotely.

Accessibility

Larger Text

Core screens, timers, sheets, reports, charts and child controls use semantic text and adaptive layouts designed to remain usable through the AX5 accessibility size.

VoiceOver

Interactive controls and visual summaries use meaningful labels, values and actions. Timers announce their purpose and state instead of relying only on colour or an icon.

Light and dark appearance

BubBasic follows the system appearance or the in-app appearance choice. Text and controls are designed for sufficient contrast in both.

Tap targets, gestures and charts

Primary controls use practical minimum tap areas. Swipe-to-delete has an explicit confirmation, and the same entry can be opened to reach its delete action without relying on the gesture.

Growth and trend information includes text, labels and values so colour is not the only way to understand it.

Get support in an accessible format

Send a request to sjmeehan9@gmail.com and ask for the relevant instructions in plain text.

To report an accessibility problem, include:

• BubBasic version and build from About & Privacy.
• iPhone model and iOS version.
• The accessibility setting or assistive technology in use.
• The screen, control and task that did not work.
• What happened and what you expected.

Do not include a child's name, care history, CSV, sharing URL or unredacted screenshot.

Apple controls parts of the experience outside BubBasic, including the Home Screen widget editor, share sheet, document picker and some CloudKit messages. Report the problem even when it appears in one of those flows; support can help identify whether it belongs to BubBasic or an Apple service.

Contact

Send support questions to sjmeehan9@gmail.com. Include the BubBasic version and build, iPhone model, iOS version, what you expected and what happened.

Do not send a child's name, care records, CSV, recovery files, record identifiers, sharing URLs or screenshots containing private data.

Read BubBasic privacy and the BubBasic terms of use.