What Not To Do In A Flutter Dev Folio Website

So why am I spending two months design a flutter dev folio website? Let me show you an UX research report that just came out on emerging UX trends by Nielsen Norman Group, titled, Support Recall Instead of Recognition In UI Design:

Support Recall Instead of Recognition in UI Design

The main takeaways are:

-Switch from Recognition to Recall

-Both Websites and Applications need discovery audience aids.

While Material Design 3, which was started as a developing iteration of Material Design 2 4 years ago, has somewhat missed the trend of switching from recognition to recall in UI design. So I have to do some refining of some specific Material Design 3 concepts and implementations. And some Material Design 3 stuff as implemented I have to throw out completely and mark as never ever use this as it represents bad UX implementation.

What Part Of Material Design 3 To Discard

So what from Material Design 3 implementations do I have to throw out? This pertains to the first-time visitor cognitive load concerning…