gplay-migrate-fastlane

To migrate Android app metadata from Fastlane to gplay CLI, you can automate the conversion of Fastlane's directory structure into gplay's `listing.json` format while preserving text files, images, and changelogs. This streamlines the transition for Play Store release management.

Yes, you can preview Fastlane to gplay metadata conversion before writing files by using the dry-run option. This allows you to verify the generated `listing.json` structure and ensure assets map correctly without modifying your actual file system.

Yes, the gplay migration supports converting specific locales from Fastlane. You can selectively migrate individual locale directories instead of migrating the entire metadata set at once, providing flexibility during the transition.

Fastlane metadata files like `title.txt` and `short_description.txt` are converted into gplay's `listing.json` format. The migration also preserves your existing image assets and changelog structures to maintain your Play Store listing integrity.

You should use a migration tool to switch from Fastlane to gplay when you have a mature Android app with established Play Store metadata and want to leverage gplay CLI features without manually recreating your directory structures and assets.