RELEASE
MANAGEMENT
FOR VIVEPORT DEVELOPER CONSOLE
project overview
Viveport is a Virtual Reality content store and subscription service operating in more than 60 countries globally. On this platform, users can explore a wide range of immersive experiences across 2000+ apps, games, and videos. For developers, Viveport offers the most ways to distribute and monetize content to a brand new audience. Viveport Developer Console is a place to help developers publish their content and continuously track the following monetization.
Release Management (RM) is a set of product features to enable and support the typical software development lifecycle (SDLC), whereas a Content goes through stages from Alpha, Beta, Release Candidate, and Published, is the new feature we’d like to provide for developers.
In addition to RM supporting SDLC, this design also describes the specifications of Branch Management (BM), a set of features enabling Content with multiple builds, allowing each build to be specialized and optimized whereas each support a specific range of HMD.
my role
Being the only UX designer in this project, I worked closely with PO, PM, Engineering Lead, and Technical Architect to discuss and narrow down our design requirements/scope. From the concept to wireframe, I designed and prototyped each proposals to help the discussion, iterated the product structure, and refined several versions of the design.
design challenge
The original title submission design/implementation only supports two content types (beta/production), whereas the submission process cannot fulfill the new requirement, which includes 4 types.
In the old process, developers do the choice to decide beta or production at the very last step of the submission. However, it’s lack of flexibility to additionally include alpha and RC in the development cycle. Further, it’s also complicated for developers to maintain their titles once the titles are published to the store. The main challenge was to make the overall submission process more instinctive and optimize the new release experience.
Also, there were too many required features for Release Management, developers were hard to focus on which action they want to do. The solution made the actions simplified in the initial stage, which only shows one button for the developer to start the build management.
sitemap
user flow
use cases
Below are some parts of use cases for Release Management. Since the overall upload/rollout process is the same in different development stage, I take beta channel as the example to represent the experience.
1. Upload a build to test channel in release management.
2. Rollout the test build after uploaded.
3. Create a new test build release after the first test version rollout.
During the testing cycle, developers can migrate the uploaded builds to other test channels based on the testing result. If the results is good, they can accordingly migrate the build to next development stage, and vice versa.
Migrate the beta test build to alpha channel.
During the development cycle, developers can revoke every test build, they can also revoke all build relationship in active testing stages by one click at production phase.
Revoke a build in one of the test channel.
Developers are able to review their binaries for development summary, and adjust binaries to be made available.
View binary build details.