Device mockups and the legal questions people skip

Nothing here is legal advice, and rules differ by jurisdiction and by manufacturer programme. But there is a set of practical distinctions that determines whether a mockup is a routine marketing asset or a problem, and they are worth understanding before you ship a listing in eleven countries.

Three separate things get confused

The device's industrial design and trademarks belong to the manufacturer. A photograph of a device is separately copyrighted by whoever took it, and stock licences carry their own terms. A 3D model of a device is a third work with its own licence. "I found it on the internet" resolves none of these. Most disputes in practice come from the second category — using a photo or model without a licence — rather than from the trademark itself.

What manufacturers generally object to

Broadly: implying endorsement, using logos and product names as if they were yours, altering marks, and presenting your product as an official one. Showing your own app running on a recognisable device in marketing is common and usually addressed by manufacturer guidelines, which typically require current hardware, unmodified appearance, and no manufacturer branding in your own logo or name. If you are going to depict a specific device, read the relevant guidelines rather than guessing.

Why a neutral rendered device sidesteps most of it

A generic, stylised body — correct proportions, no maker's marks, no distinctive camera arrangement, no product name — communicates "phone" or "laptop" perfectly while not being anyone's design. It also does not age out when new hardware ships, works across both stores from one render, and avoids the licence question for photos and models entirely. That is the main reason mockup tools increasingly ship abstract devices rather than replicas.