Skip to content
Interface language: English
Design / Signal

A 3D website on a less powerful phone: design a useful route without the scene

Preserve product information, variant selection and the path to the offer when a 3D scene fails or someone chooses to turn it off.

Article language: English

A woman watches a glass sphere on a red cord beside water channels in a coastal garden.
In this article

A chair model rotates smoothly on a designer's computer. On a customer's phone there is a dark rectangle and a spinner doing its job diligently: spinning. The chair does nothing. That is when you learn whether the page was designed to help someone choose a product or to demonstrate the studio computer's capabilities.

A good route without the 3D scene is not an apology hidden beneath the animation. It should let someone see the object, understand its important features and continue. It may be less spectacular, but it still needs to answer the visitor's question. If the 3D view shows how a table folds, replacing it with a photograph of a logo does not solve that problem. It only fills an empty rectangle.

First establish what the scene needs to show

Write one sentence describing its job. “Creates a premium impression” is too broad to design a substitute. “Lets someone see how the back joins the seat” gives a concrete direction: a view of the back of the chair and a close-up of the attachment. “Shows how the table changes width” points to two states and their dimensions. For the same reason, organise the product model viewing interface (in Polish) around questions, not merely rotation gestures.

Imagine a lamp offer where the visitor wants to check three things: the shape of the shade, the direction of light and how the lamp is attached. A model can conveniently combine those views. An alternative could use three photographs, short captions and an installation diagram. Both routes serve the same information need, although they use different tools. They do not have to look identical, just as a manual does not have to pretend to be a television remote.

Separate product content from decorative surroundings. If the scene depicts an abstract brand world, removing it must not take away the heading, offer description or button. If it contains the only visible product measurement, that measurement must also appear in ordinary content. People should not need working 3D graphics to find out what they are buying.

Map the functions before producing assets. A photographer can then prepare the missing view and a content editor can name the difference between states. Leaving the alternative until the end often means choosing the only image already in the folder. A folder rarely has a considered communication strategy.

One image, several views or a plain description?

A static image is sufficient when 3D mainly shows the shape. Choose a readable angle, the correct variant and a background that reveals the edges. The opening image should work on its own. A beautiful backlit silhouette may suit a campaign but do little to show which side of a cabinet has the handle.

Several views help when people compare parts or states. Instead of imitating rotation with dozens of almost identical photographs, show the front, back and a significant detail. A caption such as “View from the connection side” gives better orientation than “Photo 4”. Keep an order that makes sense without remembering a previous camera movement.

A description or simple diagram may be more useful than a photo. If a cable's position affects where the product can be placed, describe which side it exits. If a product changes length when extended, give both dimensions. The image supports visualisation; the text removes guesswork. Do not add a claim about measurement accuracy merely because an illustration looks technical.

The model-viewer loading documentation shows a poster image while a model loads and an example where the image remains after an invalid model file. That is a specific component capability. Whether the chosen image explains the offer remains a content design decision.

Agree on the image with the person responsible for the catalogue. If the fallback still shows the previous colour after the product colour changes, it creates a contradiction smoother animation cannot fix. Maintain a shared variant identifier for the model, photographs and adjacent name. The alternative should age with the product rather than separately.

Not every scene needs a video. A short recording can show the sequence of movement, but the visitor loses free choice of angle and moment. Pause, description and file weight also need consideration. Compare the format against guidance for embedding video on a service page (in Polish) rather than assuming that video is automatically a lighter version of every interaction.

Prepare a small working table: visitor's question, answer in the scene, answer without the scene. It does not have to appear on the site. Its job is to reveal gaps before anyone calls one image a complete substitute. Three rows can save three meetings about whether “the fallback is done”.

Loading, failure and choosing not to use 3D are different moments

Before starting the scene, show a useful image and a clearly named button, such as “View the lamp in 3D”. The person sees the product immediately and chooses the additional presentation deliberately. A short alternative can sit beside it: “Prefer photos? See three views.” There is no need to explain graphics processors or treat the phone as a suspect in the case of the missing chair.

During loading, keep the description and next step accessible. If an overlay covers the whole card, a small scene fault also blocks content that already worked. The waiting state needs an exit. Its message should describe what is happening, not promise the process will take exactly one more second.

Aeneia conceptual photography

Failure can also happen after viewing begins. MDN describes the webglcontextlost event as a signal that the buffer associated with a WebGL context has been lost. For design, that means handling an interrupted session as well as the initial load. The message can remain simple: “The 3D view was interrupted. You can return to the photos.”

Keep the selected product. If a customer was viewing a green lamp, the photos should still show the green lamp. Do not make them select the colour and size again. The exact camera angle may matter less than preserving the variant and position on the page. Set requirements according to what the person had actually done.

Manually closing the scene is a separate case. Someone may simply prefer photographs or want to read the description quietly. Offer that choice even when everything works technically. When they change variants, do not immediately force the model they just closed back on them.

Do not equate rotating a model on a page with launching an augmented reality view. If the project also has an AR feature that requires a separate step and camera access, handle refusal in that specific path. The person can still view the product on the page. “No camera access, so we will not show you the chair” would be a rather peculiar shop policy.

A good alternative does not ask people to diagnose the problem. Do not ask whether they have WebGL, lost a context or use a “supported” device. Offer a result: photos, a description of the movement or another attempt. Technical diagnosis may go to the team without occupying the main place in the conversation with the buyer.

Plan the retry as well. Clicking “Try again” should not remove the photos before a working scene appears. Decide whether the person waits in place or returns to the beginning. Someone comparing two products may value an open description more than replaying a dramatic camera entrance. Specify and accept that behaviour: a retry keeps the description open and, when the model starts, shows the variant already selected.

Separate two design jobs. Website speed work (in Polish) should reduce the cost of waiting. Designing the route without a scene should preserve the page's meaning when the expected view never appears. Both decisions matter: even a fast first screen does not guarantee that a later interaction can be completed.

Within the Aeneia Design scope, a spatial presentation can support an offer. Add to the brief what content the visitor receives when it is turned off and who will prepare the required images.

Accept two complete routes through the same offer

Acceptance is not just disabling the model file and checking whether an image appears. Complete the whole task: find the product, check an important feature, select a variant and take the next step. Repeat with the scene running and with the alternative. Record differences in information, not only appearance.

Prepare several test situations: the model is still loading, loading fails, the view is interrupted and the user chooses photographs. Check phone orientation changes and returning from another tab. The purpose is not to collect spectacular failures, but to establish whether after each one a person recognises the product and knows what to do.

Check the keyboard, control labels and content order too. Business website accessibility (in Polish) also applies to experiences added for visual effect. A photo does not help if the button to reach it is inaccessible or the description has disappeared under an interactive layer.

Include the product owner and the person preparing assets in acceptance. The first checks the information: do both views show the same construction, and does a caption promise a component belonging to another variant? The second assesses whether files and captions are complete. A joint trial helps distinguish a technical failure from a missing asset, which need different fixes.

In tests with people, ask about the feature the scene was meant to teach. “Where does the cable connect?” is more useful than “Is the alternative sufficient?” Let the participant answer using their chosen route. If they must return to 3D for one basic fact, that identifies content missing from the alternative. When device and surroundings affect use, supplement the session with observation of the website in the actual workplace (in Polish).

Apply a similar principle to an interactive product demo (in Polish): the extra interaction should improve understanding, and skipping it should still lead to a meaningful offer. A person choosing the simpler route is still an interested customer. They do not need to pass a special-effects operating test.

Finally, assign an owner for both versions in the update process. A change in construction, colour or installation should trigger a review of the model and alternative material. A short catalogue record helps: model, opening image, detail views, captions and the date of the joint review. If only the price changes, images may remain current. If the connection points change, revisit the relevant views. The person publishing an update should not have to guess these dependencies from file names. Otherwise two stories emerge about one product and customer service has to translate between them. Designing consistency before it needs explaining is easier.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear