61–70 of 245 posts
my current rule is to ask ChatGPT to do it for me
Are you memeing or are you serious? Because I'm curious how you'd have a language model design a page for you. Just ask it for the HTML and CSS for a nice looking page?
$100 for a book is steep, especially when it's a pdf.
A pdf that seems to contain "high quality" examples like "use fewer borders" where the example made several commenters, including myself, say "That's worse." Not sure why I'd pay $100 for a PDF anyway but I'm sure as heck not doing it when the kind of advice breeds less usable pages.
> [design courses] focus so much on high level principles like color theory and typography which, while important, never helped me make instant improvements Strange, making the very low contrast text more visible on this site is an instant improvement, and it's right there in the "color theory"
The contrast ratio for the body text is 7.57:1 (or 7.25:1 if the text is on the light grey background), which meets AAA accessibility standards (which is 7:1).
My only complaint is that they don't offer a physical book.
Design is how it works, not how it looks. This article seems to mainly be talking about the "polish" of a design. There are more important principles which don't have anything to do with polish, such as not putting the Cancel button next to the Ok button. More like this: https://lawsofux.com https://asktog.com/atc/principles-of-interaction-design/ https://www.nngroup.com/articles I recommend prototyping the flow/feel…
No, it is not. If you're Steve Jobs then yes, but otherwise how it looks and how it works are usually two different job functions. People who are good at visual design are not usually knowledgeable enough to do functional design, and people who are good at functional design are not necessarily good at visual design.
Design is how it works, not how it looks. This article seems to mainly be talking about the "polish" of a design. There are more important principles which don't have anything to do with polish, such as not putting the Cancel button next to the Ok button. More like this: https://lawsofux.com https://asktog.com/atc/principles-of-interaction-design/ https://www.nngroup.com/articles I recommend prototyping the flow/feel…
This could perhaps come off as excessively brutal, but it really is just my true experience in the industry - the worst UIs I have seen (both in terms of UX quality and internal code quality) have been made by that particular kind of developer has has never bothered to go a single inch outside of their little Java/C# box that they were given by their CS undergraduate course, and then, due to some reason like the comp…
I definitely agree with this and I think it partly comes down to the fact that product design is always a negotiation between many concerns – all the interface pieces on the view, patterns across views, user expectations, user research, dev LOE, etc. etc. In many ways it's the art of the possible; I say UX is harm reduction b/c there's never a perfect solution for any problem. Work like this is very subjective and always a lot about "feel".
The one with borders looks better to me than the one without, it's subjective.
Also the whole post is literally an advertisement to sell some book.
Earlier quoted context omitted.
It's also important to contrast the information density. Both the "bad" and "good" examples are quite readable but the one on the left is going to be more useful for larger lists of things.
To be fair, the course is about designing beautiful UIs, not necessarily useful ones. Wether that is actually desirable is up to you.