All articles · 5 min read

Why do apps show a "what's new" screen — and should you read it?

A "what's new" screen isn't an advert — it's the shortest route to discovering a feature that solves something you've already been fighting. Here's how to tell a good changelog from an annoying one.

What is a "what\'s new" screen

It\'s a short overview an app shows when it has gained new features since you last opened it — typically a list of two to five points, each with a heading and a brief explanation. The purpose is to save you from having to hunt for what\'s new yourself, or worse: never discovering it exists at all.

Why apps update quietly in the background

Most apps on a phone update automatically without any notice. That\'s convenient for bug fixes and security patches, which nobody needs to know about. But it also means a brand-new feature can land on your phone without a single message — and if you don\'t go looking for it in the menus yourself, you might never find it.

Good design: only show it when there really is something new

The most important difference between a good and a bad changelog is timing. A well-designed "what\'s new" screen only appears when the content has actually changed — not on every single build or every minor fix. That requires the app to keep track of what you last saw and compare it to what\'s genuinely new since then, rather than simply showing the screen every time a version number ticks up.

It sounds like a detail, but it\'s the one that decides whether the screen gets read or dismissed on autopilot. Show it too often, and the user learns to ignore it — including the times there actually was something important to know.

Bad design: a screen on every single build

The opposite mistake is just as common: an app that shows an update screen every time it has been updated — even when the update was only a bug fix nobody would notice. The result is "changelog fatigue": the user starts dismissing the screen without reading it, because experience has taught them it rarely contains anything relevant. It\'s the same mechanism as a fire alarm that goes off too often for no reason — eventually nobody reacts, not even when it\'s real.

Why it matters more for an app you use for a project

In an ordinary entertainment app, a missed feature is rarely any real loss. In an app that follows a housing project over weeks or months — takeoffs, budget, drawing — a missed feature can cost you real time: an export format you didn\'t know existed, a shortcut that would have saved half an hour, or a fix for a bug you\'d gotten used to working around. The longer a project stretches on, the greater the chance the app has gained something new since you last looked closely.

Should you update right away, or wait?

For most apps, the answer is: update whenever, unless you\'re in the middle of something critical. The exception is when an update changes a file format or a workflow you depend on — here it can pay to read the changelog first, before updating in the middle of a project you\'re deep into. If you\'re exporting a drawing for a contractor that same day, that\'s not the moment to update an app you depend on without knowing what the update changes.

How to find out what\'s new if the app doesn\'t show it itself

• The App Store listing typically has a "What\'s New" section with the latest versions\' changes, even if the app doesn\'t show them internally.
• The app\'s settings often keep a shortcut to revisit the introduction or the changelog, even after you\'ve dismissed it once.
• The developer\'s website or blog, if the app has one, often describes new features more fully than the short text in the App Store.

A sign of good maintenance, not just marketing

An app that regularly has something real to show in its "what\'s new" screen tells you something about how actively it\'s being developed. That\'s not the same as a promise that the app will get better specifically for your needs — but an app that never has anything new to show, year after year, is either finished or has stopped being maintained. Both are worth knowing before you hand it a long project.

The difference between a build number and a content version

There\'s an important technical distinction most users never see but do feel the effect of: a build number goes up with every new version sent to the app store — including the versions that only fix a single bug nobody notices. A content version, by contrast, only goes up when there\'s actually something new to report. Tie an app\'s "what\'s new" screen to the build number, and you get the message on every single fix. Tie the screen to a separate content version instead, and you only get the message when there\'s genuinely something to read. It\'s a small architectural decision with a big effect on whether users trust the screen.

What a good changelog line looks like

There\'s a big difference between a line that helps and one that just takes up space. "Improvements and bug fixes" tells you nothing — you don\'t know if it\'s relevant to you, and you can\'t act on it. A good line names the feature and says what it solves: "Now export in DXF format for the architect" or "Correct a measurement directly on the drawing, without re-scanning the room". That kind of line you can judge in two seconds — either it\'s relevant to you right now, or it isn\'t, and you move on.

What HouseSense does

HouseSense shows "What\'s New" only when the content has actually changed since you last saw it — not on every single rebuild or minor fix. The screen can always be revisited from the bottom bar on the front page, if you skipped it or want to see it again later.

Checklist: is a changelog screen worth reading

1. Does it appear when there\'s genuinely new content, or on every single update regardless of size?
2. Can you revisit it later if you skipped past it in a hurry?
3. Are the points concrete — "export to DXF" — or vague like "improvements and bug fixes"?
4. Does the app have something real to show at regular intervals? That says something about how active the development is.