Use Case

MVS - My Verizon Service

Mobile Application soon be available on Google Play Store

Duration: Nov. 2019 - Jan. 2020

Role: Lead UX Designer

Contribution: UX Design;

                           Graphic Design;

                       

Status: Coming up on Google Play

               Store soon

Feature Walkthrough

MVS provides carrier services such as eSIM download, RCS Chat, Vo-WiFi, and support EAP Authentication which is a requirement to support all the above-mentioned services. This application has required authorization to talk to the USIM on the SIM Card directly to perform successful authentication with Verizon backend systems to turn on Verizon services.

My contribution to this project is UX design and Graphic design. The duration of the design process is 2 weeks.

Target User

If users are using a Verizon concession phone or a smartphone under a Verizon contract, an SDK of MVS would be available for Service Enablers to include as part of their onboarding application. But if users are a Verizon Internet users with their own devices (so-called BYOD), then MVS requires a manual download from the Google Play Store.

The process shall be - when a VZ SIM is detected on the device, a notification (text message) shall be displayed on the phone asking the user to install the My Verizon Carrier Services application.

Use Case

With MVS, Verizon users can receive phone calls via their smart accessories. 

User Flow

As discussed with devs, we came up with two options with different installation and permission-granting method.

 

Option01: Show the application on Google Playstore

Once the application download occurs and the user clicks on "OPEN Application", it shall prompt the user for all the permissions this application requires.

OPTION 2: Trigger an automatic download of the app through Verizon Edgecast Server

The partner application will need to include the BYOD application SDK included as part of the package. Once the app is open, the app has to figure out a way to display a notification to download the app.

if the partner application already has to install permissions. This option will provide a seamless installation of the app from the parent application.

After granting permission, MVS will list out its features hosted in accordions. After growing those features, users are done setting up MVS. That's pretty much it! So I would rather consider MVS as a plug-in rather than an app because of its minimal functions and interactions.

Below are the user flow made for both options:

Hi-Fi Mockups

Other Assets

Google Play Store feature graphics