Choose the real product state
Avoid placeholder-like screens; show the action users will actually take.
Use the selected device treatment and background to add context, while keeping the Android UI large enough to inspect.

Use the selected device treatment and background to add context, while keeping the Android UI large enough to inspect.
Avoid placeholder-like screens; show the action users will actually take.
Let the headline explain why the interface matters instead of naming a menu.
Save the editable project so release messaging can change without redesigning the set.
Use the selected device treatment and background to add context, while keeping the Android UI large enough to inspect.
Avoid placeholder-like screens; show the action users will actually take.
Let the headline explain why the interface matters instead of naming a menu.
Save the editable project so release messaging can change without redesigning the set.
Use simple, intentional composition to make the next product moment easier to notice and understand.

Lead with the main product idea

Focus on the important screen

Support the product story

Finish with a clear benefit
Use the selected device treatment and background to add context, while keeping the Android UI large enough to inspect.
Avoid placeholder-like screens; show the action users will actually take.
Let the headline explain why the interface matters instead of naming a menu.
Save the editable project so release messaging can change without redesigning the set.
Use these page-specific notes when preparing your screenshots, templates, mockups or listing assets.
Use the selected device treatment and background to add context, while keeping the Android UI large enough to inspect. The strongest version of this work begins with the real user problem your product solves, rather than a generic visual trend or a keyword placed for search engines.
Avoid placeholder-like screens; show the action users will actually take. Let the headline explain why the interface matters instead of naming a menu. Together, those choices help the page show useful evidence instead of relying on decorative claims.
Save the editable project so release messaging can change without redesigning the set. Before publishing, review the page on a phone-sized screen and make sure every visible claim can be supported by the product experience.
Move between tools, templates, platform resources and guides without starting the research again.
The essentials for using RenderDuck for android screenshot templates.
Use the selected device treatment and background to add context, while keeping the Android UI large enough to inspect.
Avoid placeholder-like screens; show the action users will actually take.
Avoid copying another product’s creative or making unsupported claims. Build the page around your own app, users and verifiable product value.
Save the editable project so release messaging can change without redesigning the set.
Open the editor and turn your product screens into focused, polished app marketing creative.
Start creating