People may use the same device with different text sizes, input methods, or motion preferences. A shared arrangement that assumes one ideal setting can make an ordinary task harder for someone else.
Learn which preferences can be stored by profile and which affect the whole device. Keep important controls easy to find, and avoid treating an accessibility setting as an exceptional inconvenience. It may be the person’s normal way of using the tool.
Check the task after a preference changes. The content and actions should remain understandable. A shared device is more useful when it can accommodate the people who use it without requiring everyone to adopt the same presentation.
A small working example.
Imagine a shared application with separate display preferences. The distinction helps the interface follow the reader rather than the last person who touched the screen.
A note to keep beside it.
Look at the agreement behind a shared space. A simple explanation of ownership and next steps can prevent a small ambiguity from becoming repeated work.
- Identify profile-specific and device-wide settings.
- Keep relevant controls discoverable.
- Check the task with another presentation or input method.
Follow a related question
Use one easy landing place.
An inbox for informationConnect each field to a current purpose.
Collect only what has a purposeKeep learning
Related background to continue exploring this subject.
MDN: privacy on the web Mozilla: backing up and restoring browser data
