The public product is EveryBand. The iPhone app and its App Store and TestFlight listing still use Boop.
That distinction is part of the recent website work. A new public name does not change an installed app, a purchase label, or an older screenshot. The website needs to help someone move between those surfaces without suggesting that a separate native release has happened.
Start with the destination
EveryBand is the public product site. Its compatibility, support, and methodology pages belong to the same identity. The portfolio's EveryBand case study uses that name too, while the older work route redirects to the existing detail page.
Keeping an old address useful matters more than replacing its label in a menu. Someone can arrive through a saved link, an earlier article, or a search result. A route should carry them to the relevant page rather than leave them at an unrelated homepage.
The migration record distinguishes working legacy aliases from a deprecated domain. A historical address in an old document is not an instruction to restore it. That is why the route inventory and the visible copy need to agree.
Preserve the evidence inside the image
The existing native captures still show Boop and illustrative app data. Those pixels describe the app that was captured. Replacing the surrounding website identity does not justify editing a release name into the screenshot.
The same applies to older articles. A dated brand note can point to EveryBand while the article retains its original build context. That keeps a useful history without making the archive look like a description of today's release.
The earlier motion article follows that approach: real product screens anchor the explanation, and a creative revision stays separate from verification of the software.
One website cannot prove every product claim
Compatibility, local processing, purchase availability, and App Store review have different evidence requirements. A working website establishes none of those on its own.
The current compatibility page describes the hardware boundary. The methodology pages explain the local estimates and their limits. The install path points to TestFlight without treating it as an App Store release announcement.
The rename also does not establish a ranking improvement. Canonical URLs, redirects, and a search-service migration are operational steps. Search visibility is a separate outcome that needs to be measured later.
Keep the public story connected
A product identity is easier to understand when the website, portfolio entry, support links, and historical notes lead to the same current destination.
The useful result of this work is that continuity. EveryBand can have its own public presentation while the native app's existing name, screenshots, and release history remain accurate.