The Document Foundation is the small non-profit entity behind LibreOffice. It oversees the project and community, and is now expanding with new developer roles. So let’s say hello to Dan Williams, who joins the team to work on design and user interface (UI) improvements, with an initial focus on macOS: Tell us a bit about […]
excited to see what this means for the project, the poor UI/UX of libreoffice is easily its most glaring flaw imo
UX is also about code : think about behavior, you may want to prevent any action before one is finished. This is UX and need to be coded.
An other example : I hate how kde’s file explorer “dolphin” freezes completely while loading a remote storage. There is no change to be made as UI but a big one to do for the UX.
All you executives letting the developer do the designer’s job to cost saving is why we end users often get bad user experience in the first place.
Before you guys down vote on me or make more comments like this, know that there are lots of full-time user experience designers out there, who don’t know anything about programming. They don’t get paid for doing nothing.
You’re venting your anger on the wrong target mate. I am a developer with no diploma, never have been in any managing role (so not higher either) and always refuse to participate in any big evil corp (so say goodbye to high salary).
Other than this I am contributing to different FOSS project and specifically more interested in GPL than business-oriented MIT.
I don’t need nor feel like downvoting you, you are totally missing the spot : the majority of my work was done be a team of 1, me, and sometimes up to 5, I have worked with designer here and there and it was so much better for me who interact way differently than 99% of the people (emacs user here).
In general don’t think any executives would waste their time on Lemmy, they’re busy enough with their Nazi Twitter.
You design the UI while considering the UX. You only develop the UI, but you need to Design the UX and then design the UI considering UX before developing it.
In the same way that you are implementing the UI, you sometimes also need to implement the UX. Animations are part of the UX, preloading is part of the UX… That sort of things.
Uuuuhhh… Semantics. Preloading is an optimisation technique and animations I would consider part of the interface, not the experience. You design an experience with animations on the interface.
It’s whatever, I don’t have a strong opinion on it so if you feel like my interpretation is wrong go at it, not gonna defend it.
Why do people keep saying “UI/UX”?
UI is user interface.
UX is user experience.
One is to be developed (with code), and the other is to be designed (in Figma for instance). They have very little overlap!
UX is also about code : think about behavior, you may want to prevent any action before one is finished. This is UX and need to be coded.
An other example : I hate how kde’s file explorer “dolphin” freezes completely while loading a remote storage. There is no change to be made as UI but a big one to do for the UX.
All you executives letting the developer do the designer’s job to cost saving is why we end users often get bad user experience in the first place.
Before you guys down vote on me or make more comments like this, know that there are lots of full-time user experience designers out there, who don’t know anything about programming. They don’t get paid for doing nothing.
You’re venting your anger on the wrong target mate. I am a developer with no diploma, never have been in any managing role (so not higher either) and always refuse to participate in any big evil corp (so say goodbye to high salary).
Other than this I am contributing to different FOSS project and specifically more interested in GPL than business-oriented MIT.
I don’t need nor feel like downvoting you, you are totally missing the spot : the majority of my work was done be a team of 1, me, and sometimes up to 5, I have worked with designer here and there and it was so much better for me who interact way differently than 99% of the people (emacs user here).
In general don’t think any executives would waste their time on Lemmy, they’re busy enough with their Nazi Twitter.
Both are to be designed then developed.
You design the UI while considering the UX. You only develop the UI, but you need to Design the UX and then design the UI considering UX before developing it.
In the same way that you are implementing the UI, you sometimes also need to implement the UX. Animations are part of the UX, preloading is part of the UX… That sort of things.
Uuuuhhh… Semantics. Preloading is an optimisation technique and animations I would consider part of the interface, not the experience. You design an experience with animations on the interface.
It’s whatever, I don’t have a strong opinion on it so if you feel like my interpretation is wrong go at it, not gonna defend it.