How LifeWell Keeps Your Data Synced Across All Your Devices

Cross-device sync means one account holding one record, so that a glass of water logged on a phone is already there on the laptop you open that evening. LifeWell writes an entry to the device and to its Supabase backend, and any other device signed in to the same account reads the same rows rather than reconciling two copies. Modern life happens across several screens, and this post is about the machinery under that. It is worth saying what the machinery is not, as well: health entries are not pushed live to a screen that is already open, and only a small set of them survives being written with no connection. Water, mood and steps.

One Account, Every Device

Modern life happens across multiple screens. You might log a glass of water on your phone, check your baby's feeding schedule on your tablet, and review weekly health trends on your laptop. LifeWell ensures that every piece of data is available wherever you need it, instantly and reliably.

How Sync Works

Cloud-First Architecture

When you log any health data in LifeWell, it is saved to two places simultaneously:

Locally on your device using strata-storage for instant access
In the cloud via LifeWell's Supabase backend for cross-device availability

This dual-write approach means your data appears instantly on the device you are using, while also becoming available on all your other devices within seconds.

Real-Time Updates

Supabase Realtime uses live subscriptions that push changes to connected devices as they happen. If you log a medication dose on your phone, your tablet and web browser update automatically without manual refresh.

Conflict Handling

What happens when you edit data on two devices while one is offline? LifeWell uses timestamp-based conflict resolution:

Each change is tagged with a precise timestamp
When the offline device reconnects, changes are merged
The most recent edit for each field wins
No data is silently lost in the process

Supported Platforms

Platform	How to Access
Web	lifewell.aoneahsan.com in any modern browser
Android	Google Play Store app
Browser Extension	Not available. One was built and never published to a store

All platforms use the same Supabase backend, so your data is always consistent.

What Syncs

Everything in your LifeWell account syncs across devices:

Health tracking: Water, medication, exercise, vitals, mood
Baby tracker: Feedings, sleep, diapers, milestones, growth
Diet plans: Meals, macros, nutrition data
Notes and journals: All text content and tags
Settings and preferences: Theme, language, notification preferences
People and family tree: Contact information and relationships

Offline Resilience

Lost your internet connection? LifeWell continues working seamlessly:

All features remain fully functional using local data
Changes are queued for sync when connectivity returns
A subtle indicator shows your sync status
No action required from you when you go back online

Security During Sync

Data in transit is protected by TLS 1.3 encryption. Stored data sits behind row-level security, so a record can only be read by the account that owns it. Your Supabase session token is what proves that ownership on every request.

Tips for Best Experience

Sign in with the same account on all devices
Keep apps updated to the latest version for best compatibility
Check sync status if data seems missing (usually resolves within seconds)
Use Google Drive backup as an additional safety net for memories and photos

Cross-device sync is one of the quiet features that makes LifeWell feel effortless. Your health data follows you, not the other way around.

Elsewhere on LifeWell

Privacy — What LifeWell stores, where it sits, and who can read it back.
Plans — What the free plan includes, and what each paid one adds.
Export everything — Your whole record leaves in one file, on any plan, without giving a reason.

What people use it for

Logging on the phone and reading it on the laptop

One account, both devices, one record. Sign in with the same account on each and the entry made in a kitchen is there in the browser tab that evening, because both are reading the same rows rather than merging two versions of the same day.

Writing an entry in a tunnel

Water, mood and steps are queued on the device and sent when the connection returns. A tunnel is not a reason to lose a day. The queue is not silent about itself either: when something is waiting, a notice says how many and lists them, and when nothing is waiting there is no notice at all.

Correcting a reading without leaving a stale copy behind

A once-a-day reading is stored one row per day, so correcting this morning's weight replaces this morning's weight. Nothing is stored twice. BMI is worked out from that weight every time the page opens rather than stored anywhere, which means a correction reaches everything derived from it.

Knowing which settings travel and which do not

Units, height, display name and plan sit on your profile and follow you. You, not the phone. Theme, text size, cursor, quiet hours and the day your week starts on are kept on the device holding them, and the panel says "Kept on this device." in as many words, because a preference that silently fails to follow you is a bug you discover on the second device.

Reading what is protected, and how

Data in transit is protected by TLS. Stored rows sit behind row-level security, so a row can be read only by the account that owns it, and your session token is what proves that ownership on every request. That is the claim, at that size, because a larger one would not be true.

Questions

How does sync work?

An entry is written to the device and to LifeWell's Supabase backend. Any device signed in to the same account reads those same rows, so there are never two copies to reconcile. Reads are cached, which is what makes a second device feel immediate. The write is the part that needs a connection, unless it is water, mood or steps.

Which entries work offline?

Water, mood and steps. Those three are queued on the device and replayed when a connection returns; everything else needs connectivity and shows an honest banner rather than accepting a write it cannot keep. The narrowness is deliberate — queueing every write means a conflict rule for every table, and a person whose saved changes quietly vanish a day later.

Do changes appear on my other device instantly?

Not on their own. A health entry is read when a page asks for it rather than pushed to a screen that is already open, so a second device shows it the next time that page loads. Live updates do exist in LifeWell, in the community threads and in chats, where a message arriving while you are looking at it is the whole point.

What happens if two devices disagree?

Each entry carries an id generated on the device before the row is sent, so a replay collides with itself rather than inserting a second reading. A once-a-day reading overwrites its own day. A duplicate arriving on replay counts as success, because the row is already in the state the entry was asking for — and a queue that replayed twice would double somebody's water intake without anybody noticing, since the number would look perfectly ordinary.

Do my settings and my theme follow me?

Only the ones about you. Units, height, display name and plan live on your profile and travel between devices. Theme, text size, cursor, quiet hours and the day your week starts on are device settings, kept where you set them, and the settings page states that per section rather than leaving you to find out on the second device.

Which platforms is LifeWell on?

The web app and Android. There is no iOS app and no date for one. There is no browser extension either. LifeWell 3 ships none, and the row the post's platform table carries belongs to the previous version. So the record follows you between a phone, a tablet and a browser signed in to the same account, and there is nowhere else it needs to reach.

Does my language setting sync?

LifeWell is in English only. The mechanism for a second language is built and every string in the app goes through it, but no second catalogue exists and none is planned, so there is no language choice to carry between devices. If that changes, it changes as one new file rather than as a rewrite of the app.

What if I lose my phone?

Your record is not on the phone. It is in your account, so signing in on another device brings it back, and the photographs are in your own Google Drive rather than in either device's storage. What does not come back is the device settings — theme, quiet hours, week start — because those were never anywhere except that phone.

By Ahsan Mahmood · updated 2026-07-31

Open How LifeWell Keeps Your Data Synced Across All Your Devices on LifeWell