I told somebody I know who knew about Reddit’s API changes about Lemmy. He has a master’s degree in Computer Science and works as a software engineer. But then, he told me that it’s too confusing to get into, even for someone like him. This is great feedback and I hope that these issues will be fixed in the coming months. [https://vlemmy.net/pictrs/image/957bd891-e0b2-4056-b09b-71b80b3d3c94.png] [https://vlemmy.net/pictrs/image/c093063b-b793-44f2-96aa-368347aec676.png]
Lemmy's UX is a bit rough around the edges, but it's not bad. I've implemented bad UX. From a post I made a while ago on my Lemmygrad account, this is bad UX:
There was a list of bank transactions that you could scroll through, and you could expand a transaction and change some of its details. If you change its category, a list of checkboxes will show up for applying the category change to other transactions that are similar. This list also was scrollable. There was a scrollable list inside a scrollable list. Neither of these scrollable lists had a scrollbar.
The button on the expanded transaction for saving the changes triggered not one, not two, but three API calls. Everything’s peachy if all the calls succeed or they all fail, but what do you show the user if it some fail and some succeed? Who the fuck knows.
Lemmy's UX is a bit rough around the edges, but it's not bad. I've implemented bad UX. From a post I made a while ago on my Lemmygrad account, this is bad UX: