Current State
Bold is currently in progress
- Define problem, jobs, and design goals
- Outline system and UX exploration
- UI & production
- Design complete
Discussions/Meetings
- Previously, discussions have been with Adam Grandy from Jan-March 2018. Not tracked on Confluence.
- Product Requirements Doc by Leland
- 10/4/2018 - Rona Sheen & John Solaro chat
- John is okay with Kim's direction of leaving Profiles on the device after a user signs out of OneID as long as the user gets the choice to delete all the Profiles or leave them local.
- #1 thing is that the user has to feel that they're in control.
- John is okay with Kim's direction of leaving Profiles on the device after a user signs out of OneID as long as the user gets the choice to delete all the Profiles or leave them local.
- 10/4/2018 - Rona Sheen & Leland weeks
- Leland to finish drafting requirements and we'll review soon to talk flow.
- After we feel good about the feature, we'll share with broader stakeholders.
- Research Meeting for One ID research in January
- Design to supply wires as stimulus for study
- 2018.11.01 - One ID Sync with PM
Context
Ability for a user to sync their profile across any DisneyNOW device.
- Cross platform sync allows users with a profile on one device to setup that profile on another device. Profiles can be synced to any device with DisneyNOW installed regardless of if that device is a different form factor (phone vs. tablet vs. TV) or platform (iOS vs. Roku, etc.).
- DisneyNOW profiles store profile name, profile emoji, favorite shows, channel mode and viewing history.
- Presently profiles do not persist when a user uninstalls and installs the app or when a user upgrades their device.
- Certain features like Continue Watching and the coming Rewards program provide more value if users can access these features on multiples devices.
Goals
- Provide a consistent user experience across devices.
- Allow users to have the same profile on multiple devices at the same time.
- Allow users to earn and access rewards on multiple devices.
Problems
- Presently profiles do not persist when a user uninstalls and installs the app or when a user upgrades their device.
- Certain features like Continue Watching and the coming Rewards program provide more value if users can access these features on multiples devices.
Jobs
Jobs help you understand the situations, motivations, and expected outcomes for users who'd encounter your solutions to the problem.
- Kid
- When I have earned rewards on one of my devices, I want to be able to pick up my family's other device to also continue earning rewards with the same profiles.
- When I finishing watching VOD on my TV device, I want to be able to pick up where I left off on-the-go on my mobile phone.
- Parent
- When I help my child sign into another device, their progress on videos and Rewards points stay consistent across both.
Design Goals
- Help the user discover and be able to sign into One ID or create an account
- Help the user understand that when they sign out of their OneID account, their Profiles (TBD - remain on the device or app reverts to default/guest state)
- Indicate to user that they’ve successfully earned rewards for VOD
Context Scenarios
| Title | Context Scenario | Outcomes | |
|---|---|---|---|
| 1 | Single or multi-device user that does not sign into OneID |
| User uses local profiles. |
| 2 | Fresh install user (no local profiles) that signs into OneID with no server profiles |
| After sign-in, the Pick Your Disney Emoji screen displays and the user creates a profile |
| 3 | Fresh install user (no local profiles) that signs into OneID with 1 or more server profiles |
| After sign-in, the server profiles download and the profile picker displays. |
| 4 | Existing install user with 1 or more local profiles that signs into OneID with no server profiles |
| After sign-in, merge rules process the local and server profiles, server profiles are downloaded and a sign-in confirmation screen displays. |
| 5 | Existing install user with 1 or more local profiles that signs into OneID with 1 or more server profiles |
| |
| 6 | Existing install user that is signed into OneID who then signs out and then signs in again with their own OneID. |
| |
| 7 | Existing install user that is signed into OneID who then signs out and then signs in with another person's OneID. Users choose to remove their Profiles when they sign out. |
| |
| 8 | Existing install user that is signed into OneID who then signs out and then signs in with another person's OneID. Users choose to keep local Profiles when they sign out. |
| Can a user choose not to merge local profiles when they sign into their One ID account? In that case if they say no to linking local Profiles, are those Profiles deleted? |
Design Requirements
How might we:
- Create new OneID as a fresh install user
- Sign Into existing OneID with server profiles on a fresh install device
- How might merging local and server profiles be communicated to the user?
- Sign In or Create OneID from Settings
- Sign Out from OneID through Settings
- If a user isn't signed in for X amount of days, prompt them to save their progress.
- Help the user understand that when they sign out of their OneID account, their Profiles (TBD - remain on the device or app reverts to default/guest state)
Current system
Analytics
Open Questions
Future Ideas
Not Doing
Explore
Execute
—— Insert content ——
Design Complete
Links to engineering, Zeplin, final screens, etc.
—— Insert content ——
