Publishly

Guide

Publishly, tool by tool

How to use every tool, step by step — and each one running live on its page with a sample app, so you can try it as you read. Nothing you do in a live sample is saved, and your own work isn't touched.

A release, in order

The tools in the order a release goes. Each one remembers your app for the next, and the release checklist keeps count.

  1. Release checklistEvery step between a finished build and a published Google Play listing, in order: check the build, screenshots, promo video, listing text, translations — then download it all. Live sample
  2. Check appDrop an APK or app bundle and see what Google Play will object to — target SDK, permissions, 16 KB pages, signing, leaked keys — with the fix to paste. In your browser. Live sample
  3. ScreenshotsTurn a screen recording or your screenshots into store screenshots: pick the screens, choose a template, edit on a canvas, and export every Play and App Store size. Live sample
  4. VideoMake a Google Play promo video, an App Store preview, a launch post or a GIF from your screenshots: motion templates, keyframes, music and a voice-over, in your browser. Live sample
  5. ListingWrite the app title, short description and full description within Google Play's and the App Store's limits, checked against their metadata rules, translated and exported. Live sample
  6. TranslateBring strings.xml, a res zip, an APK or an app bundle and take translated values-xx/strings.xml back out, with placeholders, markup and plurals checked. Live sample

Around the release

Tools for one job each: an icon, a mockup, files made elsewhere, a review on a real device.

  1. App iconMake or fix your Android app icon the way Android builds it — background, logo and themed layer — with Google's safe zone checked, and download the Play icon and every size. Live sample
  2. Device mockupPut one screenshot in a 3D phone, tablet, laptop, watch or TV, turn it to any angle, keep the background see-through or not, and download a PNG — free, in your browser. Live sample
  3. Store filesDrop screenshots, icons, feature graphics or videos made anywhere and see what Google Play or the App Store would turn down — then save fixed copies, checked again. Live sample
  4. Design reviewRun your app on an emulator, a phone or Firebase Test Lab and get every screen checked: tap targets, contrast, screen-reader labels, text size, layout and ads. Live sample

In your Android app and Android Studio

Past the store: a library that puts update prompts and What's new inside your app, and Publishly's checks inside your IDE.

  1. In-appPublishly Kit, a free Android library, adds update prompts, a review ask, a More apps screen and What's new to your app. Publishly writes the update.json and release notes it reads.
  2. Android StudioLet Gemini in Android Studio check your APK or app bundle for Google Play problems and render your store screenshots, through Publishly's MCP server on your own computer.

From the terminal

The same engine for CI and AI agents.

  1. Command lineCheck an APK or app bundle, render every store screenshot, make videos and let AI agents use Publishly, with npx @publishly/cli — in a terminal, a CI job or an MCP client.

Reference