Websites and Signed-In Applications: VAD and UAD
The same design principles in two settings, explained through a visitor choice and a saved account task.
On this page — choose a section
The difference is mainly what relevant information is already available. A public website may know little about the person visiting. A signed-in application may have an account, a chosen role or an unfinished task. Both still need clear explanations and appropriate limits.
Visitor-Aware Design (VAD)
This is our term for applying Aware Design to websites where a person may not be signed in. A useful page should not depend on identifying them.
For example, a workshop page can ask which question the visitor wants answered first: what they will learn, the time and cost, or the available date. The answer changes the order of the same information. It need not be saved or sent anywhere.
An observation such as opening a pricing page is different from an explicit answer. It may suggest a need, but it does not establish a job title, budget or intention to buy.
User-Aware Design (UAD)
This applies the same ideas to applications with account context. Authenticated simply means that someone has signed in and the system has checked their access.
For example, an application may offer to resume a draft the account holder saved. It should explain which draft, let the person start fresh and continue enforcing permissions. A suggested document must not become accessible merely because it seems relevant.
An account can make continuity easier, but it does not make every assumption correct. Do not infer expertise, preferences or permission for a new use simply because someone has signed in.
Key Differences at a Glance
Scroll sideways if needed to read the whole table.
| Question | Public website | Signed-in application |
|---|---|---|
| What might help now? | A stated task or selected option. | A stated task plus relevant, permitted account information. |
| What if information is missing? | A complete ordinary page. | Clear defaults and a way to supply or correct the missing detail. |
| Does it need memory? | Not for a simple current-page choice. | Sometimes, for a saved task or preference; scope and controls still matter. |
| What must remain clear? | What a choice changes and how to undo it. | The same, plus who may access or change account information. |
Why Both Matter
A company may have a public website and a customer application. The person should not lose their place between them—but carrying context forward must be a deliberate, explained choice.
For example: “Would you like to copy this selected comparison into your new account?” Show what will be copied and allow a fresh start. Do not silently attach earlier browsing to an identified account.
These names describe settings, not a ladder of sophistication. Choose the simplest approach that helps the task.
Inspect a small website example or read the practical principles.