The differences between a for Parents and a for 

In this post I’m going to take a look at how I designed my with two different audiences in mind; children aged 8–12 and parents.

Onboarding

Signar has two users; kids and parents. When the parents sign up, they go through an onboarding process which follows the same structure as many other UIs, swiping right to move on to the next screen. However in my research for kids apps, this might not be an obvious move for the youngest of users. The parents UI doesn’t have arrows or next buttons, but depends on our instinct to know to swipe to move on to the next one based on the progress circles at the bottom:

I’ve decided to change up this process in the kids section of the app and use a straightforward ‘next’ button. It’s important to design for the youngest of users, so going by my target audience, this would be 9 years old. But the reality is the users could be a good bit younger than this if they have older siblings who use the app. Also, sign language education works best when the learner starts young, so I don’t want to discriminate here.

It’s a case of familiarity for the parents, and ease of use for the kids. By catering for the youngest of users everyone can use this app.



Source link https://blog..io/-my-app-ui-for-kids-668a26d2e585?source=rss—-eb297ea1161a—4

LEAVE A REPLY

Please enter your comment!
Please enter your name here