Package selection guidance compiled from public package information, community data, and project usage.
package_rename_plus is a high-performance tool designed to streamline the process of configuring Flutter projects for production. It enables rapid renaming of package identifiers, app names, and related assets across multiple platforms including Android, iOS, macOS, Windows, and Linux. By automating configuration updates, it reduces manual errors and accelerates deployment readiness. Ideal for developers aiming to maintain clean, consistent project structures during scaling or rebranding.
Use cases
Renaming Flutter apps for rebranding
Preparing apps for production deployment
Automating package identifier changes
Cross-platform configuration updates
Streamlining CI/CD pipelines
Key features
Blazing fast execution
Multi-platform support
Automated asset updates
Safe configuration handling
Command-line integration
Suitable for
Flutter developers
App rebranding teams
CI/CD automation engineers
Large-scale project maintainers
DevOps engineers
Considerations
Requires careful backup before use
May conflict with custom configurations
Not suitable for one-off changes
Limited to package-level renaming
Depends on correct project structure
Original README
Original README snapshot from the linked source repository. Visit the repository for the latest content.
Package Rename Plus
This a fork repository from official package_rename using different approach to replace the configuration.
Fixed ios issue about replace bundle identifier with or without extension targets.
Removed logger dependency that can be solved using debugPrint only to minimize dependency to others packages/plugins.
A Blazingly Fast way to configure your Bleeding Edge flutter project to be production ready.
Package Rename handles changing 37 fields across 19 files on 6 platforms so you can focus on your awesome project.
You can create configurations by adding package_rename_config key in:
Root pubspec.yaml file
package_rename_config.yaml file at root of your project or a custom folder in the project
Usage
Adding Platform Specific Configurations
package_rename_config:android:app_name:# (String) The display name of the android apppackage_name:# (String) The package name of the android appoverride_old_package:# (Optional) (String) Use this to delete the old folder structure of MainActivity or to use the existing code with the new package namelang:# (Optional) (String) The android development language {kotlin(default) or java}ios:app_name:# (String) The display name of the ios appbundle_name:# (String) The bundle name of the ios appoverride_old_package:# (String) Use this to replace the old bundle identifier with the new bundle identifierpackage_name:# (String) The product bundle identifier of the ios applinux:app_name:# (String) The window title of the linux apppackage_name:# (String) The application id of the linux appexe_name:# (String) The executable name (binary name) of the linux appmacos:app_name:# (String) The product name of the macos apppackage_name:# (String) The product bundle identifier of the macos appcopyright_notice:# (String) The product copyright of the macos appweb:app_name:# (String) The title of the web app and PWAshort_app_name:# (String) The short display name of the PWA (Optional, defaults to app_name if not set)description:# (String) The description of the web app and PWAwindows:app_name:# (String) The window title & software name of the windows apporganization:# (String) The organization name (company name) of the windows appcopyright_notice:# (String) The legal copyright of the windows appexe_name:# (String) The executable name (binary name) of the windows app
dart run package_rename_plus --flavour=flavour_name
or
dart run package_rename_plus -f flavour_name
With custom config file location:
dart run package_rename_plus --flavour=flavour_name --path="path/to/package_rename_config.yaml"
Known Issues
iOS and macOS issues with PRODUCT_BUNDLE_IDENTIFIER:
The PRODUCT_BUNDLE_IDENTIFIER's in ios/Runner.xcodeproj/project.pbxproj and macos/Runner.xcodeproj/project.pbxproj have different values for different targets. Like, in my case:
Hence, to properly change the PRODUCT_BUNDLE_IDENTIFIER without removing the Extension name, make sure all PRODUCT_BUNDLE_IDENTIFIER's except the DEFAULT ones are enclosed in double quotes ("").