store-optimize

To improve ASO elements and maximize app CVR, an automated optimization cycle analyzes evaluation results, identifies low-scoring areas across screenshots and metadata, and generates targeted improvements. This process updates your configuration files and produces a Before/After comparison report visualizing the score differences.

An ASO optimization cycle handles updates by analyzing evaluation scores, generating improvement proposals ranked by CVR impact, and applying changes directly to your fastlane/metadata directory and store-craft.config.json configuration file for reproducible execution.

Prerequisites for running ASO optimization workflows on fastlane metadata include having an existing store-craft.config.json file, a populated fastlane/metadata directory with locale-specific files, and a previously executed ASO evaluation step to provide the baseline scores for identifying improvement areas.

Yes, you can generate a Before/After comparison report for ASO changes automatically. The optimization cycle produces this report after applying improvements to your screenshots, metadata, and keywords, visualizing the score comparison and differences to demonstrate the CVR impact.

The best way to prioritize ASO metadata improvements for higher conversion rates is to rank proposals by their estimated CVR impact. The optimization cycle targets the lowest-scoring elements first, ensuring changes with the highest potential impact on app CVR are applied to your metadata.

ASO optimization requires a prior evaluation step because it needs baseline scores to identify which specific elements have the lowest performance. Without these evaluation results, the system cannot determine which screenshots, metadata, or keywords require improvements to effectively maximize app CVR.