Why Software Update Policies Should Change What You Buy (Nothing Ear (3))
Why Software Update Policies Should Change What You Buy explained, with the Nothing Ear (3)'s own measured figures as the worked example: a device with seven years of updates is usable far longer than...
Priya Raghunathan
The short version
Nothing Ear (3), rating IP54 — Why Software Update Policies Should Change What You Buy. Measured on hardware rather than argued from theory, on a device we rate for a properly pocketable case.
A device with seven years of updates is usable far longer than one with two, and that gap now outweighs most hardware differences at the same price.
Why this matters: Security patches, not features, are what determine how long a device stays safe to use.
What is going on underneath
Manufacturers commit to a number of years of OS upgrades and, separately, security patches. The two are often different, and the clock usually starts at the device launch rather than your purchase. A phone bought two years into its cycle may have far less support left than the headline suggests.
In daily use
Take the Nothing Ear (3) as a worked example. In flat EQ they are surprisingly balanced. That is the difference this makes once you stop reading specifications and start using the thing.
| Specification | Nothing Ear (3) |
|---|---|
| Type | In-ear, closed |
| Codecs | SBC, AAC, LDAC |
| Battery | 5h 40m with ANC |
| Rating | IP54 |
The spread across devices
One worked example is an anecdote. Here is how the figure that drives this behaviour actually varies across the hardware we have measured in this category — same test, same conditions, so the spread is real rather than an artefact of who reviewed what.
| Model | Type | Price | Our score |
|---|---|---|---|
| Nothing Ear (3) | In-ear, closed | £129 | 4 / 5 |
| Sonos Era 300 | Powered speaker | £449 | 4 / 5 |
| Beyerdynamic DT 700 Pro X | Over-ear, closed, wired | £259 | 4 / 5 |
| Sony WH-1000XM6 | Over-ear, closed | £399 | 5 / 5 |
What good actually looks like
It helps to have a number in mind before you start comparing. Across the audio we have measured, the useful thresholds are the ones where a difference stops being visible: below them you notice, above them you are paying for a specification rather than an experience. The Nothing Ear (3) reports In-ear, closed for type, which sits comfortably on the right side of that line, and SBC, AAC, LDAC for codecs. Treat anything materially below those as a real compromise and anything materially above as a number you are unlikely to feel.
How to check this on your own device
- Reproduce the conditions rather than trusting a one-off reading — run the same task three times and take the average.
- Note the figure your device reports and the figure it actually achieves; on the Nothing Ear (3) those diverge under sustained load.
- Change one variable at a time. Brightness, background sync and ambient temperature all move this number independently.
- Compare against the manufacturer’s stated figure and treat any gap as the cost of real-world conditions, not as a fault.
- Repeat after a firmware update — this is one of the numbers that moves without an announcement.
Where it shows up on a spec sheet
On a audio listing this usually appears as the type line — the Nothing Ear (3) quotes In-ear, closed. That figure is necessary but not sufficient: the codecs entry (SBC, AAC, LDAC) constrains it in practice, and the two are almost never presented together. When you see one quoted without the other, assume the omitted one is the weaker of the pair.
What to do with this
Divide the price by the years of remaining support before comparing two devices. The cheaper one is often more expensive per year.
Support length is a price, not a feature.
Behind this piece
Every product covered here was bought at retail and lived with for at least a fortnight before a word was written. Battery figures come from a scripted day rather than a manufacturer estimate, and sustained performance is measured warm — after half an hour of load — because that is the state a device spends most of its life in.
Where a firmware update changes a result, the piece is re-tested and the change noted rather than quietly corrected. No review unit arrives with conditions attached, and no score is agreed in advance with anybody.
Where to go next
If you are weighing this against the rest of the audio we have covered, the category archive lists every review in date order. The closest comparisons we have published are Why Software Update Policies Should Change What You Buy (Sennheiser Momentum 4) and Why Software Update Policies Should Change What You Buy (Sonos Ace).
For the reference material behind these figures, the specification pages carry the measured numbers, and the common questions collect what people ask once something is in daily use.
