Earlier quoted context omitted.
Oh, sure, those are indeed major fails in all of the OSes - no guides and no easy way to find anything about fundamental operations (it should be easier than googling). But these are separate issues. For example, even with the scrollbars there can be a change between two behaviors: click on the empty bar jumps to that % or jumps by 1 page. And one can be a click and another a Shift-Click - where in the OS would you d…
But with a visible scrollbar you would have a visible indication which behavior you triggered. If the scrollbar is invisible you get a changed viewport in both cases but you have to infer which gesture triggers which behavior.
Rules for creating good-looking user interfaces
171–180 of 183 posts
Re: Rules for creating good-looking user interfaces
#172Earlier quoted context omitted.
I second this, it’s like people live in completely different worlds when it comes to getting stuff out the door. Of course, that’s still better than a 1 pizza team of full stack devs attempting to create their custom UI component library from scratch, now that’s a total mess.
Grandparent here. Alright, I totally believe you and everyone else, and would probably also be much happier in a less wasteful environment that you mention. In which industry/company size are you? Maybe I’m looking in the wrong places.
Think along the lines of companies with either Of course, it's also possible for companies without the actual means to delude themselves into thinking that they must do everything Google or other big orgs do - that's how you get bad bespoke components and frameworks without the mettle to make them good, as well as stuff like architectures based on microservices without a good reason to do so and so on.
Re: Rules for creating good-looking user interfaces
#173As a designer first turned developers in the early 2000, I beg of you to learn the gestalt. Frameworks, languages, computers, come and go, but the human body doesn't change and the knowledge I have in design, I carry every day and have barely changed over the years. Sure there are new patterns now... "hamburger buttons" and swiping, but the logic remains the same. Human's don't change quickly. They discover things th…
Re: Rules for creating good-looking user interfaces
#174As a designer first turned developers in the early 2000, I beg of you to learn the gestalt. Frameworks, languages, computers, come and go, but the human body doesn't change and the knowledge I have in design, I carry every day and have barely changed over the years. Sure there are new patterns now... "hamburger buttons" and swiping, but the logic remains the same. Human's don't change quickly. They discover things th…
Designers who remove scroll bars and window borders so you can’t click and drag are computing’s version of a terrorist. It’s an active assault on performance.
Re: Rules for creating good-looking user interfaces
#175It's such an irony that for such a topic, website content is actually overflowing on a mobile safari and gets out of the container so the website appears broken.
Re: Rules for creating good-looking user interfaces
#176As a designer first turned developers in the early 2000, I beg of you to learn the gestalt. Frameworks, languages, computers, come and go, but the human body doesn't change and the knowledge I have in design, I carry every day and have barely changed over the years. Sure there are new patterns now... "hamburger buttons" and swiping, but the logic remains the same. Human's don't change quickly. They discover things th…
Re: Rules for creating good-looking user interfaces
#177As a designer first turned developers in the early 2000, I beg of you to learn the gestalt. Frameworks, languages, computers, come and go, but the human body doesn't change and the knowledge I have in design, I carry every day and have barely changed over the years. Sure there are new patterns now... "hamburger buttons" and swiping, but the logic remains the same. Human's don't change quickly. They discover things th…
Or do you mean: simply understand all of human psychology and design UIs that work for everyone? That seems to be what you're saying, but both are impossible. Nobody really understands human psychology, especially those who think they do. Show me a psychology finding that is applicable to UI design and I'll show you a study of 30 college freshman that doesn't replicate. And you cannot design a UI that is intuitive for everyone; people are too different, and the "average person" literally doesn't exist.
So what exactly is your advice? Know everything and apply that knowledge appropriately for your specific situation? React and Kubernetes have clear documentation, tutorials, and canonical ways of doing things. UX design has a couple of clever books. The analogue of "just learn good UX design" is not "just learn React", it's "just learn how to write readable, maintainable, clear, performant code everywhere." It takes decades.
Re: Rules for creating good-looking user interfaces
#178Earlier quoted context omitted.
Here's the funny thing though (as a developer which worked for various companies that didn't have designers): It looks custom designed because... it's not designed at all :D At this point I'm not even sure if what you said is an insult or a compliment. Almost all projects I worked in looked more or less like the following: - a BA meets with the client and creates unstyled wireframes with all of the requested features…
And on the rare occasions where there is a designer on the team, they just throw their fantasy user interfaces over the fence to be interpreted by developers as well as blamed for any complaints. What we really need is developers with solid design skills, that should have been part of fullstack from the start.
And the number is *two* if I count the ones who also understand technical nuances, accessibility and proper usability.
Re: Rules for creating good-looking user interfaces
#179Saw a lot of words here. Not a lot of examples. "Dark mode was one of the most requested features for Lighthouse. I refrained a long time from adding it because it adds additional work to every UI task." This reveals a lot about the regression in OSes. Way back in the early '90s, Windows provided a color-scheme editor. Users could set up any color scheme they liked, and all properly-written apps would inherit it and…
It's still there on KDE
Re: Rules for creating good-looking user interfaces
#180Earlier quoted context omitted.
Personally, I immediately don’t trust this book because the example on the page of the list UI puts a big red X over the version I prefer and find easier to read.
Half agree. The left version I feel has too many sharp lines and bold distinguishing features, so you don't know where to look, where the version on the right has too few so you don't know where to look.