4 ms·
I'll suggest over reliance on dependencies on the frontend. <BOX type="soap"> The thing about a dependency frontend module, is that it often brings in some re
by ChrisMarshallNY 5y ago
I'll suggest over reliance on dependencies on the frontend.
<BOX type="soap">
The thing about a dependency frontend module, is that it often brings in some really cool stuff, like animations and attractive design elements, but also introduces inflexibility. You have to use the supplied design elements, and you can't modify the animations.
This gets compounded, when you aggregate dependencies.
Dependencies aren't bad. They are how we get big stuff done, with small teams. Done right, they can also enforce UI consistency, and improve quality.
Done wrong ... well ... not so much.
It's possible to have UI suites that provide a lot of customization options, but the customization comes at the expense of increased implementation complexity. There's usually a fairly significant learning curve, which isn't popular, when your boss is breathing down your neck, so many developers opt for the defaults (which isn’t necessarily a bad thing, as that can enforce consistency). It means that they are often using standard tools for specialized tasks (think using an English wrench on a metric bolt).
Also, developers and designers tend to hate (I mean sticking-pins-in-voodoo-doll-hate) usability folks, like Jakob Nielsen and Don Norman; which is too bad, because they have some great suggestions.
The backend can be a byzantine nightmare. Maybe it needs to be, but the frontend should be consistent, simple, and user-task-oriented.
That "user-task-oriented" is important. The deal is helping users to get stuff done. It isn't to impress them with eye-candy chrome, pretty design and fancy interaction. Good UI helps the user to get done what needs doing, and gets the hell out of the way.
The best user interface is the one you don't notice. That can be damn difficult to achieve.
This is often accomplished by doing rote, "cliché" UI. I write about that, here: https://littlegreenviper.com/miscellany/the-road-most-traveled-by/ https://littlegreenviper.com/miscellany/the-road-most-travel...
I am a fan of good interpretive SDKs (ones that don't just present the raw substrate to the programmer), and native coding.
</BOX>
- mrweasel 5y agoWe used to present our designer with a particular webshop, when he asked what sites we frequently used and enjoyed. That site had made one change to their layout in 12 years, they added round corners. That site was easy to navigate, everything was a simple as you can imaging, no weird icons, just text that said: "In stock/out of stock". The thing is, the site looked old, and dated, so everything good was dismissed along with the styling.
- ChrisMarshallNY 5y agoPart of consistency, is being consistent with current standards. That generally means working on the code to keep it looking current. But custom problems require custom solutions (for example, a Web shop for a customizable widget, that maybe also needs to have restrictions imposed by industry licensing standards), and that can be difficult to do, with standard stuff (I have had to do almost exactly that, and have the scars to prove it).