An app rename is not finished when the new wordmark appears in a design file. Existing users have to recognize the product they already use, while new customers have to understand the listing they are about to download. Treat the App Store rename as a release handoff, not as an isolated naming decision.
Identify the listing fields you can edit, and when
Apple’s App Store Connect reference describes the display name as localized, with a length of two to 30 characters. It can be edited before initial App Review submission. Apple says later changes can be made when you create a new version or when the version’s status permits editing. The name is not the bundle ID; Apple says the bundle ID cannot change after a build has been uploaded. Ask engineering and the release owner to confirm the current version status and app record before the creative team schedules the announcement.
The subtitle sits under the app name on the product page. Use it to communicate something the name no longer conveys, such as the core job the app helps the customer do, rather than repeating the new name in longer form. Start with the same buyer expectation in each market, but check that the actual wording sits comfortably within the locale’s field and reads naturally.
Update the story in the listing, not just its heading
Apple’s properties reference is the starting point for understanding which material can be localized and which fields are version-specific. In your handoff, separate App Store copy from any in-app artwork that must ship with the build. Review screenshots for old names embedded in UI and captions. Review help copy for instructions that tell existing customers to search for the old product name. A later crop, screenshot or language edit should still point to the same experience.
- Give the release owner the old and new names, approved subtitle and screenshot text by locale.
- Give support a plain-language notice that says what actually stays the same, such as access to an account where confirmed.
- Preview the new product page next to the version you plan to ship; call out mismatches before the public campaign.
- Check the store page after release on an actual device, with at least one reviewer who did not work on the rename.
Do not make the campaign depend on an unchecked release
Write a go/no-go rule for the transition. If your listing or customer help still uses the old name, decide who can postpone paid announcements, and which neutral wording should go live instead. That decision is easier while the naming project is still on the calendar than when buyers are already clicking through.
Discuss your product rebrand with Benjamin Branding if you need a naming and release brief that design, engineering and support can use together.