Renaming my app days after launch

My health app went live on the App Store as Tether. It cleared review in sixteen minutes, zero rejections. I should have been celebrating.

Instead I searched “Tether” on the App Store and found my app — nowhere.

The name was invisible

“Tether” felt right when I picked it: the app tethers your Apple Health data to your AI agent, end-to-end encrypted. Poetic. Accurate. Completely unsearchable.

The word belongs to a crypto giant (USDT), a hotspot feature, and a pile of existing apps. My listing was buried under all of them. A name that describes your product means nothing if nobody scrolling the results can find it — or worse, if they find someone else.

The lesson crystallized fast: name for search, not for meaning. Meaning you can add later, in the subtitle, in the screenshots. Findability you either have or you don’t.

Picking a new name like an engineer

I didn’t want to trade one buried name for another, so every candidate had to survive five checks before I’d consider it:

1. App Store search — does anything rank for this exact word? Ideal answer: zero results.
2. Domain — is the .app domain actually registrable at a normal price, not parked at $3,000?
3. GitHub — is the org/repo name free?
4. PyPI — is the package name free? (The app ships with an MCP server installed via uvx, so the package name is user-facing.)
5. Trademark — any obvious conflicts?

I generated a long list of candidates, argued against each one, and ran the survivors through all five checks with real lookups — not vibes. One name came through completely clean on every axis: Vaultbeat. A vault for your health data; a heartbeat inside it. Zero App Store collisions, domain registrable at cost, GitHub and PyPI both empty.

Migrating everything in one day

Renaming three weeks into a product’s life is annoying. Renaming three years in would be catastrophic. That asymmetry is the whole argument for doing it immediately once you know.

The migration checklist, all in one push:

• GitHub: renamed the repos — old URLs 301-redirect automatically, so nothing published breaks.
• PyPI: published the MCP server under the new package name, verified uvx vaultbeat-mcp installs clean.
• MCP Registry: registered the server under the new identity.
• Domain: bought vaultbeat.app, moved the whole site over, kept the old domain as a permanent 301 with paths preserved.
• Search Console: verified the new property, resubmitted the sitemap.

The one thing I could not do in a day: the App Store display name, which rides along with the next app update and review cycle. Fine. Everything else pointing at the new name first means the App Store change lands into a world that’s already consistent.

What I’d tell past me

Run the five checks before you fall in love with a name. It costs an afternoon. The alternative costs a rename — or worse, it costs you every user who searched for your app and found a cryptocurrency instead.

Vaultbeat lives at vaultbeat.app.