Daily UX Sketches

These are all notes from my notebooks, in no particular order.

In the last years I collected many sketches and notes, but you know how it goes, you start sketching something quickly just to take a note on a solution you have in mind, and after some months you sketch it again because you forgot that you actually already did. :)

SIGN a VERY LONG document DIVIDED IN SECTIONS

• Focus on the needs of 80% of your users

• Get as much info as possible from other sources

• Delay a login requirement for as long as possible

• Onboarding is not a substitute for good app design

• Give users only the info they need to get started

• Use animation & interactivity to engage users

• Make it easy to dismiss or skip the onboarding UX

1 - BENEFIT ORIENTED

• What does the app do?

• How can user integrate this into their life?

• What value will this integration provide?

Present max 3 key benefits on-the-slide, one concept, prioritize, use consistent vocabulary, onboard before registration, keep it brief —> focus on the absolute essential.

2 - FUNCTION ORIENTED

• What is the key functionality?

• When to use this functionality?

• How to user this functionality?

Don’t explain the obvious 3 functionalities. Help the users get started.

3 - PROGRESSIVE ONBOARDING

Most popular, people learn by trying.
Save for complex workflows, user for hidden functionality, ideal for gesture driven-apps.

PUSH AND MARKETING NOTIFICATIONS

“We need permission for GPS!” “But we also have to send push notifications!” “We ABSOLUTELY need it!” and it ends with 5 super annoying pop-ups one after the other, and those users never opening your app again.

Imho, we should have divided the flow in 2 moments (Solution 2).