decoderHealth reads connected health records from Health Connect on Android or Apple Health on iOS. These services provide a shared source for measurements written by compatible apps and devices. decoderHealth presents the records you permit alongside its own local trackers.
The challenge of separate health records
Different apps can record different parts of a day. A scale may supply weight, another app may supply nutrition, and a wearable may supply sleep or activity. A connected-health service makes those records available in one permission-controlled place.
decoderHealth does not guarantee that every source records every metric. The charts reflect records the platform supplies and the permissions you have granted.
One connection, several metric views
The app covers weight, steps, activity, energy intake, nutrients, sleep, water, glucose, and cycle. Nutrition supplies both energy and nutrient fields. Sleep stages appear when available. Activity can include exercise sessions and calorie information.
Fasting and Check-In are different: they are created and stored inside decoderHealth. They do not become Health Connect or Apple Health records.
How the connection works
- Review the source: check that your other app has written the expected records to Health Connect or Apple Health.
- Choose permissions: grant decoderHealth read access for the metrics you want to display.
- Refresh the view: open Metrics or pull to refresh in the affected metric.
- Inspect the history: check timestamps and available source information when a measurement looks unfamiliar.
Read and write permissions have separate purposes. Granting write access alone does not authorize decoderHealth to read a chart's source data.
Supported manual entry and write-back
decoderHealth lets you add supported measurements and sessions manually. These manual records can be sent to the connected health service when the required write permission is granted. Imported records are not sent back as new decoderHealth entries.
Some series are read-only. Available calorie aggregates, for example, are viewed as platform data rather than edited as manual totals. Entry forms follow the supported type for each metric.
Refresh and data coverage
The app refreshes on opening or resuming and offers pull-to-refresh in metric views. Background refresh is best effort: operating-system scheduling and battery controls can delay it. A background schedule is not a promise that every source record will appear immediately.
On Android, daily step totals use Health Connect's aggregate rather than adding every source's individual count. This helps avoid counting the same activity repeatedly across connected sources. Other metrics use their supported record and time-window handling.
Example: a measurement is missing
If a weight point is absent, first check whether it is present in your connected health service. Then review decoderHealth's read permission and refresh. If no source record exists, you can use supported manual entry for the measurement you actually observed.
Do not interpret an empty sleep, nutrition, or activity view as proof that none occurred. A permission, source, timing, or logging gap can produce an empty chart.
Review permissions when your setup changes
If you change phones or source apps, check which records are available and which permissions remain granted. Local fasting and Check-In history is separate from connected-health records and is not rebuilt from that source. Read the user guide for the remaining app features.