# Did your trend change when the software changed?

Draft • Research checked 4 October 2026 • AI-assisted DomDNA editorial content. No independent clinical review or publication is claimed. General education, not individual medical advice.

A wearable can stay on the same finger or wrist while its measurement process changes. Firmware, app software and algorithms may be updated without any change to your routine. A continuous-looking chart can therefore span more than one version of the system producing its numbers.

That is not a reason to distrust every update. It is a reason to keep version changes in view when interpreting a sudden shift.

## The device is more than its shell

Sensors collect signals, software processes them and an app presents an output. Changes at different points can affect what appears in a chart. A new feature might change the label or presentation without changing the underlying measurement; another update might change the calculation.

[FDA's final guidance for digital health technologies in clinical investigations](https://www.fda.gov/media/155022/download) specifically addresses updates and possible measurement inconsistencies. It recommends that trial sponsors record the timing and nature of changes and consider whether measurements remain fit for purpose.

Those recommendations concern research investigations. They do not certify a consumer device, require a personal regulatory audit or prove that a particular update altered your data.

## An invented weekly chart

Imagine a hypothetical activity app whose weekly score rises on the same day a software update arrives. The person also begins walking a different route that week. There are at least two possible contributors, and the chart does not separate them by itself.

Now imagine the update changed only the colour of the graph. The timing coincidence would not establish a measurement change. Reading the release note can help distinguish a described calculation change from a presentation change, although notes may not explain every detail.

If the update introduced a new score, comparing its values directly with a retired score would create a different problem: the same-looking number may no longer name the same measure.

These are invented scenarios. They provide no claim about the magnitude or direction of a real wearable update.

## Use the release note for what it establishes

[Oura's official firmware page](https://support.ouraring.com/hc/en-us/articles/34036777934227-Oura-Device-Firmware-Versions) provides release-version context. Its rollout language should not be read as proof of when a specific member's device received an update. This research pass did not inspect a member account or a physical ring.

The company's [May 2025 activity announcement](https://ouraring.com/blog/activity-improvements/) also illustrates that feature and algorithm changes can be announced separately from hardware. Manufacturer claims of improved accuracy are not independent validation, and this article does not adopt them as a measured effect.

For any device, distinguish the firmware version from the app version and from a server-side change if the available documentation identifies one. Do not invent a version history when the provider does not expose it.

## Preserve context without inventing a correction

A useful personal record can include the date you observed an update, the version displayed and the release-note link. If the exact installation date is unknown, label it unknown rather than substituting a published rollout date.

You may choose to mark a boundary in the chart and describe values before and after it separately. That preserves the uncertainty. Applying an improvised conversion factor to make the two periods match would create numbers the device did not report.

Also retain original exports where available. A screenshot can preserve how a chart looked at a moment, but it may not preserve all metadata or prevent the provider from later recalculating historical values. Check the actual export rather than assuming what it contains.

## One practical next step

Before attributing a sharp trend shift to a new habit, check whether a documented device or software change occurred nearby. Write a short annotation: “App updated here; measurement impact not established.”

If the release note describes a relevant change, keep that description beside the trend. If it provides no answer, retain both possibilities: a real change in behaviour or physiology, and a change in measurement or presentation. They can occur together.

For research using wearable outcomes, look for how the report handled version continuity. The device's brand name alone does not tell you which implementation generated the data.

Updates can make a system more useful. Honest interpretation still needs to know which system produced which observations. A tiny version annotation can be more valuable than a confident explanation attached to an unexplained jump.

For an educational starting point, the [DomDNA lifestyle quiz](https://domdna.com/quiz) records lifestyle answers, not DNA analysis or a clinical diagnosis.