UC1 - VR Designer Backoffice App

Latest update about the Backoffice app

Based on ADR-0031, the VR Designer app will load alembic files. Each alembic file contains a combination of avatar, garment and animation, thus making the files comparatively large in size. Also using alembic files aligns with the preferred export method of fashion designers because they use Browzwear’s VStitcher 3D Apparel Design Software that supports them. Alembic files also have superior texture quality as opposed to other formats. Also, in importing said alembic files in Unity in order for the VR Designer to access them, there is a series of manual actions needed to be performed from the development side that currently cannot be automated.

All of the above requirements made the case for using an administrative tool like the VR Designer Backoffice app very weak, thus we decided not to proceed with implementation. We retain the Usage Scenarios for future reference.


Sign Up View

Sign In View

Garments View

Add New Garment View

Avatars View

Add New Avatar View

Animations View

Add New Animation View


Usage Scenario 1.0

Use Case id: 4.1.0

Primary Actor: Designer

Description

The user must sign up or sign in to use the app.

Pre-Conditions:

None.

Task Sequence:

In order to upload Garments, Animations or Avatars, the user must first login so that the files uploaded have a creator.

The user can Sign Up providing a Full Name, e-mail and password.

Alternatively the user can Sign In using the credentials of an existing account.


Usage Scenario 2.0: Garments View Interactions

Use Case id: 4.2.0

Primary Actor: Designer

Description

The user can see all the uploaded garments and perform various actions in the Garments View.

Pre-Conditions:

None.

Task Sequence:

After successfully logging in, the user is shown a Dashboard featuring three columns. The first column features the navigation of the Dashboard, so the user can easily switch between the different types of items. There is also a Sign Out button. The second column features a list of the uploaded garment items. The user can perform the following actions:

  • Search for a garment item by name, using the search icon in the top right of the column.

  • View all available garments in the form of a list.

  • Delete a garment item.

  • Add a new garment item by clicking on the FAB button floating in the bottom right.

  • Select a garment item by clicking on it, where the third column is populated with editable garment item details.

By clicking on a garment item in the list, the third column of the Dashboard is populated with the editable details of the garment item. More specifically the user can:

  • Change the Title of the garment item.

  • Add or remove a Garment. Three things must be selected, an FBX file a zip containing the textures and a json file with the texture metadata.

  • Add or remove a garment photo.

  • Specify Categories.

  • Specify the Collection(s) a Garment is part of.

  • Add / Remove Market Segmentation data.

After all edits have been made, the user can click on the UPDATE button to update the garment item with the new information.


Usage Scenario 2.1: Add New Garment Item

Use Case id: 4.2.1

Primary Actor: Designer

Description

The user can upload a new garment item.

Pre-Conditions:

  1. 4.2.0

Task Sequence:

While being on the Garments View the user can click on the FAB in the bottom right of the Garment List in order to launch the Add New Garment view.

In this view the user has to input the following information in order to add a new garment item to the system:

  • Garment Name (Title).

  • Select a Collection(s).

  • Add a Garment. Three things must be selected, an FBX file a zip containing the textures and a json file with the texture metadata.

  • Add a Garment photo.

  • Select Categories.

  • Specify Market Segmentation entries.


Usage Scenario 3.0: Avatars View Interactions

Use Case id: 4.3.0

Primary Actor: Designer

Description

The user can see all the uploaded avatars and perform various actions in the Avatars View.

Pre-Conditions:

None.

Task Sequence:

This view features a list of the uploaded avatars. The user can perform the following actions:

  • Search for an avatar by name, using the search icon in the top right of the column.

  • View all available avatars in the form of a list.

  • Delete an avatar.

  • Add a new avatar by clicking on the FAB button floating in the bottom right.

  • Select an avatar by clicking on it, where the third column is populated with editable avatar details.

By clicking on an avatar item in the list, the third column of the Dashboard is populated with its editable details. More specifically the user can:

  • Change the avatar title.

  • Add or remove the FBX file of the avatar.

The user can click on the SAVE button to update the avatar.


Usage Scenario 3.1: Add New Avatar

Use Case id: 4.3.1

Primary Actor: Designer

Description

The user can upload a new avatar.

Pre-Conditions:

  1. 4.3.0

Task Sequence:

While being on the Avatars View the user can click on the FAB in the bottom right of the Avatars List in order to launch the Add New Avatar view.

In this view the user has to input the following information in order to add a new avatar to the system:

  • Avatar Name (Title).

  • FBX File


Usage Scenario 4.0: Animations View Interactions

Use Case id: 4.4.0

Primary Actor: Designer

Description

The user can see all the uploaded animations and perform various actions in the Animations View.

Pre-Conditions:

None.

Task Sequence:

This view features a list of the uploaded animations. The user can perform the following actions:

  • Search for an animation by name, using the search icon in the top right of the column.

  • View all available animations in the form of a list.

  • Delete an animation.

  • Add a new animaton by clicking on the FAB button floating in the bottom right.

  • Select an animation by clicking on it, where the third column is populated with editable animation details.

By clicking on an animation item in the list, the third column of the Dashboard is populated with its editable details. More specifically the user can:

  • Change the animation title.

  • Add or remove the FBX file of the animation.

The user can click on the SAVE button to update the animation.


Usage Scenario 4.1: Add New Animation

Use Case id: 4.4.1

Primary Actor: Designer

Description

The user can upload a new animation.

Pre-Conditions:

  1. 4.4.0

Task Sequence:

While being on the Animations View the user can click on the FAB in the bottom right of the Animations List in order to launch the Add New Animation view.

In this view the user has to input the following information in order to add a new animation to the system:

  • Animation Name (Title).

  • FBX File


Usage Scenario 5.0: Manage Market Segmentation

Use Case id: 4.5.0

Primary Actor: Designer

Description

The user can create, delete and set a default Market Segmentation.

Pre-Conditions:

None.

Task Sequence:

  • While being on the Market Segmentation View the user can see a list of the available Market Segmentation entries. By clicking on the star icon, a Market Segment can be set as default. By clicking on the trash bin icon the entry can be deleted.

  • To create a new entry, the user can click on the FAB in the bottom right, and a new entry will appear in the list.

  • When a Market Segment is selected, its details are populated in the third column. There the user can change the Market Segment properties and save the entry.