Use generated imagery for mood, framing, and a clearly fictional screen, but do not present invented interface details as proof that a product supports an app or feature. Capture or obtain an authorized real screen separately, then composite it in an external editor with the correct perspective. Inspect the edges, reflections, readable claims, and final crop before listing.
Define What the Image Claims
First decide whether the screen is decorative or evidentiary. A blank dashboard, abstract chart, or fictional message can be acceptable when the caption makes its illustrative role clear. A recognizable app name, settings panel, compatibility badge, measurement, or notification implies that the pictured product really produced that result.
The critical checkpoint is this: if a buyer could reasonably use the screen to decide whether the product works with a particular service, use real source material or remove that implication. Do not rely on an AI-generated imitation of a supported UI, even when it looks plausible at thumbnail size.
Imagild's current Skills catalog can help with the surrounding product scene and compositing direction. Check the available controls and source/result examples before planning a workflow. Exact typography, interface layout, and final format conversion belong in an external editor.
Build From Authorized Screen Material
For a fictional planning example, imagine LumenFrame Mini, a digital photo frame advertised with support for an imaginary app called “Gallery Relay.” The listing team plans a hero image showing a family photo on the frame and a small settings screen visible at an angle.
Use this sequence:
- Obtain an authorized screenshot or photograph of the actual supported interface, with private accounts, names, and unrelated notifications removed.
- Photograph or create the product scene separately, keeping the frame plane, bezel, glare, and viewing angle observable.
- In an external editor, crop the real screen to the display boundary, apply perspective transformation, and match its exposure to the photographed product.
- Preserve enough interface detail for the claim to remain truthful, while avoiding a crop that makes an unrelated screen appear to belong to the product.
- Export the listing version only after checking the final size and compression for accidental unreadable or altered text.
Inspect The Composite
The LumenFrame planning example passes an observable check only if the screen's four corners remain inside the display opening, text follows the same perspective as the glass, and the bezel does not mysteriously cover or reveal interface elements. Compare the final image with the original authorized screen at 100 percent and at the intended listing thumbnail size.
The second checkpoint is semantic: verify that every visible app name, status, button, and measurement is supported by the product's actual documentation. If the real product only mirrors photos but does not display an app's control panel, do not show that panel as though it came from the frame.
Look for common compositing failures: duplicated icons in reflections, warped text near corners, a screen glow spilling over the bezel, impossible finger reflections, and a UI that changes between alternate listing images. These are acceptance checks, not evidence that an AI tool generated a usable result.
Label Fictional Demonstrations Clearly
A generated placeholder may still be useful for a concept board, internal pitch, or clearly labeled “illustrative interface” panel. Keep fictional branding generic, avoid invented partner marks, and place the explanation where viewers will see it rather than hiding it in production notes.
If the product has no real screen, do not generate one merely to suggest operation. A physical mockup or a separate diagram can explain the idea without making a compatibility claim. External editing remains necessary for exact labels, legal copy, metadata review, and final listing assembly.
Can Imagild reproduce a real app screen exactly?
Treat generated UI as a visual placeholder, not an exact or verified reproduction. Use an authorized real screenshot for claims about compatibility, controls, or results, then edit it externally.
Is a fictional screen always misleading?
No. It can support a concept or clearly labeled demonstration. It becomes misleading when its details imply a supported app, measured result, or product behavior that has not been established.
What should I check before publishing?
Check authorization, product-to-screen relationship, perspective, readable claims, reflections, and consistency across images. Remove or label any detail that the real product cannot produce.