Welcome the user to their system and guide them around.
The first time someone uses their new system is an important moment to establish a relationship between them and the OS. It's important to offer a warm welcome, and to reinforce brand characteristics. It shouldn't feel like a let down.
The first run situation is also a good time to provide essential information about how to use the system. This has previously been achieved through the getting started documentation. However, there are issues with this approach: Help doesn't look good and isn't an effective mechanism for branding. The getting started docs can be a lot of work to maintain.
- Positively reinforce the brand/product identity:
- Look good
- Be welcoming, establish a relationship with the user
- Convey positive brand/product identity characteristics
- Provide basic information about how to use the system
- Do this in a way that's consistent with the branding and product identity - as we explain, we should also communicate positive characteristics
- Don't provide too much content, don't be a chore
- Since the desktop is blank on first run, the greeter is a way to make sure that the first session isn't empty
- Simple to implement
- Content that's easy to maintain
All the onboarding experiences
The greeter needs to be aligned with initial setup, so we don't repeat branding elements and so we emphasise specific moments in the first run experience.