# KeyNest Password Manager — Task Input Brief

**Purpose:** Give every learner the same fictional product context for the onboarding design task. This is a practice brief only; KeyNest is not a real service.

## Product

KeyNest is a fictional mobile password manager. It stores a user's saved passwords in an encrypted vault protected by a **master password**. The master password is not stored in a form that KeyNest support can read or reset.

## User problem

People who are new to password managers may not understand what a vault is, why the master password matters, or what happens if they lose access. They need a calm, clear setup experience that explains the choices before asking them to continue.

## Product rules to represent accurately

1. The master password unlocks the user's vault.
2. KeyNest support cannot view or reset a forgotten master password.
3. During setup, users can create a **recovery kit** for restoring access. The prototype should explain what the kit is and tell users to store it somewhere safe.
4. Users may skip recovery setup. Before they skip, show a clear warning: if they later lose the master password and have no recovery kit, the vault cannot be restored.
5. Do not imply that KeyNest can recover, email, or reveal a forgotten master password.

## Design assignment

Create a mobile-first onboarding flow of **4–6 screens** in Figma. Cover:

- Welcome and a plain-language explanation of the vault.
- Master-password setup, using placeholder UI only.
- Recovery-kit setup or a clearly explained skip choice.
- A completion screen that confirms the next step.

Use fictional placeholder values. Never ask for or display a real password, recovery phrase, email address, or other personal information.

## Usability and accessibility expectations

- Use short, everyday language and explain unfamiliar terms when they first appear.
- Show the user's progress through setup.
- Make the primary action, back action, and skip option easy to distinguish.
- Include visible labels, readable contrast, and clear validation or help states.
- Keep warnings specific and close to the decision they describe; avoid frightening or misleading copy.

## Edge cases to consider

- The user tries to continue without entering a master password.
- The two password entries do not match.
- The user chooses to skip recovery setup.
- The user does not understand what the recovery kit is for.
- The user reaches the end and needs a clear confirmation of what is set up.

## Submission expected from the learner

1. A shareable Figma prototype link with view access enabled.
2. The 4–6 onboarding screens, connected into a clickable flow.
3. A short design note (about 150–300 words) explaining the wording, recovery choice, and one accessibility decision.
4. A brief note identifying any assumption made beyond this brief.

## Review focus

The reviewer will check that the flow follows the product rules, explains recovery and the skip consequence accurately, handles the listed edge cases, and is understandable and accessible. This is a design-practice task, not a security audit or assessment of a real password manager.
