A lot of applications have a happy path which is ideal if you are more familiar with it, and over-optimizing for brand new users might be problematic if it's repeat users who use it most.
So one way to anticipate the unique needs of new users without over-optimizing the whole application for new confused users is to design a state which is special for new users, but gets replaced once they are through the starter period.
I think this has to be done thoughtfully from a product/engineering perspective, to not create a hairy mess of different application paths, but there is a good happy place which can anticipate some varied needs and account for them.
Anyway, that's what comes to mind for me.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Depending on what we mean...
A lot of applications have a happy path which is ideal if you are more familiar with it, and over-optimizing for brand new users might be problematic if it's repeat users who use it most.
So one way to anticipate the unique needs of new users without over-optimizing the whole application for new confused users is to design a state which is special for new users, but gets replaced once they are through the starter period.
I think this has to be done thoughtfully from a product/engineering perspective, to not create a hairy mess of different application paths, but there is a good happy place which can anticipate some varied needs and account for them.
Anyway, that's what comes to mind for me.