Questions

The questions app teams ask about changing images without a release.

Straight answers to the questions developers and designers post in forums and issue trackers, with the alternatives named and the trade-offs stated. Where Assetlib fits, the page says so; where it does not, it says that too.

• How do I change an image in my app without users updating the app?

  Four ways to change an image in a shipped mobile app without a new build or store review: same-URL hosting, a URL in remote config, EAS Update, and a placement-based release workflow. What each one breaks, and what to check.

• What can EAS Update change, and why didn't my image update?

  What EAS Update can and cannot change in an Expo app, the reported reasons an image does not update after an OTA update, and when a separate image release workflow is the better fit.

• How do I stop exporting 1x, 2x, 3x and Android densities from Figma for every image?

  Why designers end up exporting every image at 1x, 2x, 3x and mdpi through xxxhdpi for developers, what the app actually needs, and how to export one source once and let tooling produce the sizes.

• Are remote images and over-the-air artwork changes allowed by the App Store and Google Play?

  What Apple's and Google's review guidelines restrict about content an app downloads after review, why images are treated differently from code, and what to keep in mind when artwork changes without a new build.

• How do I find unused images in my app?

  How to inventory the images shipped in a React Native, iOS, or Android app, find exact duplicates and oversized files, and why 'no reference found' is a review candidate rather than proof that an image is unused.