Contexts of use

Edition and Visualization are the 2 main macro contexts of use of 3DCS Web 3D viewer.

• An authoring phase of the experience itself (adjusting light, choosing a color background, deciding to expose technical elements...).
  • e.g., A 3D artist publishing his/her 3D work on a Marketplace.
  • e.g., A Marketing persona creating the digital catalog of a company products line.
• A visualization (or consumption) phase for the recipient of the experience
  • e.g., The end user who will search for a 3D assets on a Marketplace, for inspiration or to buy it.
  • e.g., The consummer of a ecommerce website who will visualize a product in 3D.

They both imply a dedicated technical layer (Web components and Iframe, respectively).

Authoring

For authoring experiences, the adapted technical stacks are the Web components. Web components will allow each team to chose features to build taylor-made experiences.

To ensure a consistency, the 3DCS Design Guidelines provide teams with :

• A zoning where Web components are organized on there usage and possible number (scalability optimization).
• A 3D&I validated default design for major Web components.

For any question or support need on design, Eva Gutin (gutin@adobe.com) will be your contact point.

Visualization

For visualization experiences, the adapted technical stack is the Iframe.

Contrary to the Authoring experience, the Iframe is very limited in terms of UI/UX customization.

The Design choices made on the Iframe are aligned with Design choices made on the Authoring Design Guideline. This will allow teams who need both authoring and visualization workflows to have a constistent experience all along there product/service.

For any question or support need on design, Eva Gutin (gutin@adobe.com) will be your contact point.