Web Apps

It's what the user sees where no data is available to the user yet. A “Good empty” state turns a moment of nothing into something.



Empty states:

* Encourage users to engage with our product

* Help them get comfortable by setting expectations for what’ll happen.

* Provide an obvious way to move forward.



For example, the first page that users see after signing up for Instagram is empty. Other profiles have photos, likes, and comments, but a first-time user’s account doesn’t have any information— 0 posts, 0 followers, 0 following.



To make the activation easier, Instagram has turned this “empty state” into learning  & encouraging opportunity: where you would normally see your photos, it says “No Posts Yet — Tap on the camera to share your first photo or video” with an arrow pointing to the camera option.

An amazing walkthrough is: 

Clear – telling users exactly how each feature works

Concise – covering all bases without dragging on

Engaging – giving users the option to interact rather than just watch

Skippable – to accommodate faster learners

Offers additional support – a speak-to-a-coach feature in our case, for example, for users that are struggling to follow

A walkthrough is a meticulous way of onboarding users. It ensures that no stone is left unturned and gives new users a great understanding of how the product works. 



But not all walkthroughs are made equal. 



A walkthrough, if done the wrong way, can have too much emphasis on hand-holding and not enough focus on engagement. This could frustrate new users and actually send them packing before they’ve even finished onboarding.