Some good tips and a good reminder not to overload the user with information, especially on mobile.
However, trying to give this pattern a new name feels a bit disingenuous - it comes across as self promotional (even if unintended).
This is a well established pattern already and it's known as a Wizard - guiding users, chunking information, etc -- IBM talked about this back in 2001 [0]
And they wrote a 400 page book about this called Designing Effective Wizards [1]
I see this quite often in our industry, people trying to coin a new name for something when one already exists.
Please don't.
Give credit where credit is due or at least acknowledge people who researched it before.
However, trying to give this pattern a new name feels a bit disingenuous - it comes across as self promotional (even if unintended).
This is a well established pattern already and it's known as a Wizard - guiding users, chunking information, etc -- IBM talked about this back in 2001 [0]
And they wrote a 400 page book about this called Designing Effective Wizards [1]
I see this quite often in our industry, people trying to coin a new name for something when one already exists.
Please don't.
Give credit where credit is due or at least acknowledge people who researched it before.
/rant over
[0] https://www.ibm.com/developerworks/library/us-wizard/
[1] https://www.amazon.com/Designing-Effective-Wizards-IBM-books...