KasyKasy

App name

Start with a placeholder name and change it later with a single command.

Don't have a name yet? Create the project with any placeholder name and start building. Once you decide, one command changes the name everywhere Kasy wrote it.

Implementation

With MCP (recommended): ask the assistant "rename the app to Corner Diner". It shows a preview, asks whether the app was already sent to the stores, and only applies after your yes (rename_app). See Kasy MCP.

  1. See what will change (nothing is written):

    kasy rename "Corner Diner" --dry-run

  2. Apply it:

    kasy rename "Corner Diner"

    In the terminal it asks what to do with the app ID (see below). To run without questions:

    kasy rename "Corner Diner" --bundle-id auto           # changes the ID to com.cornerdiner.app
kasy rename "Corner Diner" --bundle-id com.yourcompany.app
kasy rename "Corner Diner" --keep-bundle-id          # keeps the current ID

  3. Stop the app and run kasy run again. The home-screen name and the ID are native: r/R is not enough.

The app ID can only change before publishing. After the first upload to the App Store or Google Play (TestFlight and internal testing count), the ID is tied to that app forever. Changing it creates a different store app, without users, reviews or subscriptions. Pick the final ID before the first upload. The visible name can change whenever you want.

Information

Visible name vs app ID

ExampleWho sees itCan change after publishing?
Visible nameCorner DinerUsers: under the icon, in the browser tab, inside the appYes, always
App ID (Bundle ID on iOS, applicationId on Android)com.cornerdiner.appOnly the stores and services (Firebase, social login, RevenueCat)No

On the store page, the name shown is the one you set in App Store Connect and Play Console. When you rename a published app, update it there too.

What the command changes

  • Always: name under the icon (Android and iOS, in every language), browser tab and installed web app (PWA) title, app title, onboarding notification mockup, kit_setup.json and README.
  • Also always (technical): the Dart package (package:... in imports) and the Android notification channel. They derive from the name and Kasy keeps them in sync, so kasy add and kasy update keep working.
  • Only if you change the ID: Android (applicationId, namespace and Kotlin folder), iOS (Bundle ID of the app and its extensions, widget App Group), codemagic.yaml and the app registration in Firebase, done automatically.

The project folder is not renamed. If it still has the placeholder name, rename it with the editor closed.

After changing the ID

  • Firebase: the command registers the new ID on its own. If you were offline, run kasy rename again later: it notices and finishes. The old registration stays in the Firebase console, harmless.
  • Phone or simulator: the old app stays installed as a separate app. You can uninstall it.
  • Anything you set up with the old ID: social login (kasy google, kasy apple-web, kasy facebook), iOS signing (kasy ios), Codemagic (kasy codemagic) and RevenueCat need the new ID. The command itself lists what applies to your project.

Renaming an app that is already published

Use kasy rename "New Name" --keep-bundle-id. The name changes and the ID stays. Android creates a new notification category with the new name; settings the user changed on the old category do not carry over. On the Firebase backend, run kasy deploy afterwards so push notifications use the new category.

Last updated on 11/03/2026

Splash Screen

Change the logo shown when the app opens. Light mode, dark mode, and web.

On this page

ImplementationInformationVisible name vs app IDWhat the command changesAfter changing the IDRenaming an app that is already published