TL;DR: To give an app a different name and icon, change the display name in Xcode, replace the icon in the asset catalog, rebuild, and check that the home screen, Settings and App Store Connect all match. Before you submit, review the brand and make sure the binary and the store listing tell the same story.
Decide which name and icon you can change
The name users see and the icon on the home screen both come from the app bundle. Platform and brand limits still apply, so first check that the new name is clear and legally usable. If you want to do that first, read how to legally choose an app name, which separates the legal side from the visual side before you touch any assets.
On iPhone and iPad the visible name comes from the display name in the project. The icon comes from the asset catalog. If you change one and leave the other, the result looks half finished.
Change the app name in Xcode
In Xcode, the text under the icon is controlled by the target's display name or, depending on the project, by the CFBundleDisplayName key. Check both, because that value is what users normally see on their device.
If the change does not show up, check these:
- You edited the right target, not the test target.
- A per-platform or per-build setting is not overriding the name.
- You rebuilt and reinstalled the app on the device or simulator.
- The name also makes sense on the App Store listing if you plan to change it there.
If you localize the name, check the language files too. A change can work in English while the system keeps another local value.
Change the icon in the asset catalog
Replace the app icon in the asset catalog, inside the app icon set. It needs every size iOS requires, not just one nice image. Xcode expects a consistent set of images for each required size, based on the project setup.
The set usually includes several resolutions and uses. If a piece is missing, the compiler or the validation step can complain. To avoid surprises:
- Replace each size in the icon set with its matching version.
- Use sharp, square images.
- Check that the background, crop and margin still look good at small sizes.
- Export at the right resolution instead of stretching a small image.
A rushed or low-resolution icon shows on the home screen, in Settings and in other places across the system.
Check that the name and icon match everywhere
Before you send anything to review, check that the change looks the same wherever users see it. A new name with the old icon, or the other way round, makes the app look unfinished.
Quick checklist:
- Home screen: the name under the icon and the icon itself
- Settings, if the app appears in system lists
- The install or update screen, if your flow shows one
- App Store Connect metadata, so the listing matches the binary
How to evaluate an app before submission is a good pass for catching mismatches before review. App Store Promotional Text vs Description: What Goes Where helps keep the name, listing and visible messages aligned.
Example: renaming a utility app and giving it a new icon
Say an app called "Task Log" now wants to be "Daily Log". The new name sounds more like a daily record than a to-do list, and the new icon should stop looking like a generic notebook.
What changes in the project:
- Update the target display name or the
CFBundleDisplayNamevalue. - Replace the icon in the app icon set of the asset catalog.
- Check any localized names.
- Check whether the App Store Connect listing also uses the new name.
What you rebuild:
- Build the app again to produce a new binary with the updated name and icon.
- Reinstall it on a simulator or device and check the real result.
What to check before sending to App Store Connect:
- "Daily Log" shows correctly under the icon.
- The new icon is clear at small sizes.
- The listing, screenshots and description no longer talk about "Task Log".
- The binary and the metadata agree.
Check for rejection risks before review
The usual problems are ordinary:
- A name that promises something the app does not do
- An icon that suggests a different feature
- Differences between the installed binary and the store listing
- A rename that hurts clarity or brand consistency
Final short list:
- Visible name updated in the project
- Icon replaced in the asset catalog
- Tested on a device or simulator
- App Store Connect aligned with the binary
- Quick brand and clarity check before submitting
When everything matches, the app stops looking like a draft and looks like a finished version.