hhushhas Mobile Screenshots
Capture natively at an accepted size instead of resizing: pick a simulator or emulator whose screen already matches a store-accepted dimension, clean the status bar, screenshot with the device tool (never a window capture), and the file is upload-ready. The specs are nitpicky — exact pixel pairs on Apple, aspect and alpha rules on Google — but all machine-checkable, so validate locally before uploading. Commands and device mappings: references/ios.md, references/android.md.
The requirement floor is smaller than most write-ups claim: Apple needs one iPhone 6.9" set (1–10 shots) plus one 13" iPad set if the app runs on iPad — it scales those to every other size. Play needs at least two screenshots, a 512×512 icon, and a 1024×500 feature graphic before a listing can publish.
What reviewers reject is mostly honesty, not pixels: screenshots that don't show the real app in use (no splash, login, or title cards), status-bar clutter (Play outright bans carrier names and notifications), promo text overwhelming the image, and frames or composites that misrepresent the app. Capture from the build you're submitting, not an older one — stale screenshots undercut even a metadata-only resubmission.
Branded sets
Branded composition with short truthful headlines, backgrounds, motifs, and device framing is allowed on both stores. Start with one concept and use Imagegen to create the complete marketing composition, including the exact headline or copy, visual art direction, and framing, while providing the real capture as locked product-truth reference. Treat any generated product panel or app UI as a placeholder: replace that region programmatically with the untouched validated capture. Keep deterministic code limited to capture insertion, cropping, masking, scaling, color conversion, and final technical formatting; do not manually add or patch the primary marketing copy after generation. If Imagegen renders incorrect copy, regenerate with the exact corrected wording. Vary color and composition across the set while retaining one recognizable visual system, inspect the full contact sheet, and re-validate every final asset. Use ImageMagick for capture replacement and final formatting, not for typesetting the primary marketing copy. Pass an explicit -font for contact sheets or any unavoidable technical annotation, because the unset default errors on any annotation, even implicit labels.
Uploaded but not showing
Apple's store icon isn't an upload at all — it ships inside the binary's asset catalog, so changing it means a new build, a new version, and a full review pass. On Play, listing-graphic changes only go live after being sent for review and approved (hours to days), and with managed publishing on, approved changes sit parked until someone publishes them. When art "won't update", check what was actually submitted before suspecting a caching bug.