Skip to main content

Topic hubs

Screenshot & mobile UI resources by launch problem

Follow focused paths for App Store listings, Play Store graphics, ASO creative, and AI mobile UI handoff.

Choose the hub by the asset you have

Have real product screens? Start with the App Store hub or Play Store hub. Learn supported dimensions, slide order, and export checks. Do not treat a phone screenshot as a Play feature graphic: the 1080×1920 phone set and the 1024×500 banner are separate assets, and StoreShots currently generates the phone set, not that banner.

Have an idea but no shipped screens? Start with Mobile UI to shape a connected flow and export HTML, React, React Native, and PNG renders for engineering review. Need a character for onboarding or empty states? The Mascot hub covers variants, transparency, motion, and handoff. Need conversion craft after the sizes are clear? Use the ASO hub for benefit-led headlines, localization checklists, and AI-versus-designer workflows.

Use the guides as a launch sequence

  1. Understand product truth: define the user, the job, and the screen or state that proves the value. If the app does not have real screens yet, use Mobile UI to explore the connected flow before engineering commits to it.

  2. Make the story scannable: use the App Store or Play hub for native dimensions, slide order, headlines, and feature-graphic distinctions. AI can accelerate the draft, but the visible UI and claims still need human review.

  3. Review the handoff: open exported files on a phone, verify accessibility and policy constraints, and upload manually after the pack is correct. StoreShots creates assets; it does not replace engineering, accessibility review, store policy checks, or manual submission.

What StoreShots does and does not do

StoreShots composes marketing frames around your uploaded app UI for App Store 1290×2796 and Play phone 1080×1920; generates multi-screen Mobile UI with code exports; generates mascot bases, variants, and GIF loops; and uses credit packs that never expire.

It does not redraw or invent product UI that is not in your captures, ship a production-ready app from Mobile UI alone, generate Play 1024×500 feature graphics yet, submit listings to Apple or Google, or run closed testing. Use related product TestMyApps when managed Play testing is needed. Policy, accessibility, and engineering review remain part of the launch.

Start with samples, then choose credits

Review sample outputs for hierarchy, legibility, and set consistency. Samples show the kind of output the workflow can create; they are not customer case studies or guaranteed conversion lifts. When you are ready, open pricing: Starter is $10 / 50 credits and Studio is $18 / 100 credits. The same wallet covers store slides, Mobile UI screens, and mascot work; one credit covers a base or variant and two credits cover a mascot GIF.

How the five hubs work together

Treat the hubs as a map, not five isolated articles. A typical dual-store launch moves from product truth to App Store pack to Play phone pack to an ASO localization pass, with optional mascot polish for in-app moments. A pre-build startup might reverse the order: Mobile UI exploration first, then store packs once captures exist.

Keep links contextual. From App Store, link Play when discussing dual-store export. From Play, link feature-graphic education so shoppers understand the gap StoreShots does not fill yet. From Mobile UI, link App Store and Play only after explaining that generated UI is a handoff artifact, not a listing PNG. From Mascot, link pricing so teams budget GIF credits correctly. From ASO, link the comparison posts without inventing competitor claims.

Quality bar before publishing a pack

Whether you generated slides in StoreShots or elsewhere, confirm that dimensions match the store, headlines match the visible UI, no unverified social proof appears in the frame, localization strings fit without crushed type, and the ZIP opens cleanly on a phone. The pre-submit checklist covers the last mile.

If an Android launch also needs twelve opted-in testers for closed testing, finish listing visuals first, then use TestMyApps as a related ClyroLabs product, not a StoreShots feature. Keep the CTAs and expectations separate in launch documents.

Frequently asked questions

Which hub should I open first?

If you have production screens, open App Store or Play Store. If you are still designing the product, open Mobile UI. If you need a brand character, open Mascot. Use ASO when the sizes are clear and you want conversion craft.

Are StoreShots AI and storeshots.org the same?

No. StoreShots AI at storeshotsai.com is a ClyroLabs product. The open-source project at storeshots.org is unrelated.

Does StoreShots create Play feature graphics?

Not yet. StoreShots exports 1080×1920 phone screenshots; 1024×500 feature graphics are a separate asset created elsewhere until support ships.

How do credits work across hubs?

One credit covers a store slide, UI screen, or mascot base/variant. A mascot GIF uses two credits. Approved re-exports are free and packs never expire.