Notices tagged with ux, page 7

@js @haiku user-friendly, sure, but good #UX is not 'decide everything for the user'. It's more like 'set sane defaults, but give the user information and choices'. Especially when it comes to install procedures they only have to deal with once (per install).

> But I still think you should just not buy hardware that needs blobs in the first place.

Ideally, sure. But this is still vanishingly rare, and you're assuming that people are buying their hardware, rather than making do with cast-offs.

@spongefile @bob @catonano I'm CLI literate, but far from being a wizard. That said, I have had a few experiences where command have helped me solve problems a GUI couldn't (at least not on my ancient laptop). The problem is, the more arcane tech skills I acquire, the further I drift from the experience of the newbie user, and the more useless my informal #UX consulting methods become. Thus the desire to learn formal UX methods.

Add to that the fact that most of the email clients I've used on #GNU-Linux are buggy, crashy messes, with a #UX that makes GIMP looks user-friendly. Nobody who depends on email for mission-critical communication (and storage of same) wants to risk a badly maintained app losing or shredding their correspondence. Nobody who doesn't would be bothered to go to the effort. And all these before we even start talking about adding encryption to the mix.

@spongefile @catonano @bob ae, I imagine presenting your argument with data being less likely to be dismissed without consideration. I'm keen to learn more about formal #UX practices. What would you recommend as the best method(s) for performing A/B testing for apps and websites?

@aadilayub to be fair, both of those guys have/ do work for Big Tech, and it was their goal with #TimeWellSpent to influence their former/ current employers' #UX design habits.

Les fourberies du Dark UX
https://framablog.org/2018/08/18/les-fourberies-du-dark-ux/
#a11y #Accessibilite #Amazon #DarkUX #Facebook #Utilisabilité #UX #Web

Les fourberies du Dark UX
https://framablog.org/2018/08/18/les-fourberies-du-dark-ux/
#a11y #Accessibilite #Amazon #DarkUX #Facebook #Utilisabilité #UX #Web

@LWFlouisa try logging in using pinafore.social instead of the social.coop interface. I find it much less confusing, and I'm guessing it would be better #UX on a mobile

@ignitionigel it really depends on what your priorities are. At a guess, you can probably have any 2 of complete software freedom, smooth #UX (including full cross-platform support), and reliably implemented #E2EE (*not* roll-your-own!). There's also #GNU #Ring, which has the advantage of being serverless, but with the potential downsides on mobiles of using more power / bandwidth than server-based apps. I haven't tried it yet though. HN thread on Ring from a year ago:
https://news.ycombinator.com/item?id=14873083

@ajroach42 they're also distributing #PublicDomain video and may be very interested in anything you develop, and have some ideas to share on #UX

@trwnh @pixelfed it could be a way of collecting #UX data on whether the app is helping people find the content they want or not? The number of "I'm not interested" reports per user could be graphed, and correlated with UI tweaks and other changes, to see if they make the app more or less useful to the user

@sir @Wolf480pl @Michcioperz GitPub is a working title coz everything has to be called something. AP seemed like the obvious thing to use because of network effect. If there are good arguments for other protocol choices that achieve the same #UX more efficiently (not just the same *output*, the same effortless click-and-go workflow), why not make them? Even if the GitPub drafters ignore you (and that's far from certain), others may find it useful.

#UX designer: user testing suggests users find a UI more intuitive, and gets their work done quicker, if it works like this
Engineer: if I can conceptualize this problem out of existence, I don't have to solve it, and as a bonus, I can sneer down my nose at anyone who tries to tell me that my mental gymnastics doesn't help users get their work done!
*facepalm*

@bob @Wolf480pl @Michcioperz @sir
> I bet that IRC will still work with ultra slow internet connections too.

That is a valid #UX concern, and if #IRC does work better with dial-up or patchy mobile than #XMPP or #Matrix in the same UI, that's a good argument for using IRC. What it's not is a convincing argument to use a 1990s IRC UI as a replacement for #Slack, instead of one of the many free code apps with a more #Slack-a-like UX
https://www.coactivate.org/projects/disintermedia/slacking-off

@Wolf480pl @sir @bob @Michcioperz OK, I can see why it seemed like I was criticizing IRC as a *protocol*. We could indeed have a discussion about how XMPP does things better in same ways, or how Matrix s better than both for web-based chat. But here I'm talking about the #UX of Slack vs. the UX of *actually-existing* IRC as it is now, as an analogy for the UX of GH/ GL vs. Git+email as it is now.

@sir @Wolf480pl @Michcioperz I know that. I'm not sure how else to explain this, so please don't take it personally, but I think the problem here is we're thinking in totally different conceptual primitives. Yours is GH as a web icing on a Git cake, which is a totally natural way for an engineer to think. Mine is Git as a database for a web UI for collaborative editing, which is a natural way for a #UX designer to think. Consequently we are talking past each other a lot ;)

@sir @Wolf480pl @Michcioperz @Karneolius
> most people who use git are engineers

I don't think this is true, for a number of reasons. The main one being that engineers are only one of the specialists involved in post-CLI software dev, especially for net software. Other specialities include graphics, #UI, and #UX designers, doc writers, beta testers.

> I do not feel the need to make tools which are accessible to noobs.

I'm not saying you must, but that's the use case GH and #GitPub are for

@Wolf480pl @Michcioperz @Karneolius
You could "use a bike" to achieve roughly the same goal as a high-speed train, but there are some pretty obvious differences in the #UX. Reasons the "use Git and email" argument falls flat
1) in @sir 's own words from the blog you linked:
> "Given that most popular email clients these days are awful and can’t handle basic tasks like “sending email” properly"
2) most people who use Git are not engineers and do not and *will never* live on the command line

@Michcioperz @Karneolius @Wolf480pl #GitPub is about federating together instances of #GitLab, #Gogs, #Gitea etc, to create a similar #UX to GH (everything is connected, low barrier to drive-by contributions), without forcing everyone to develop free code on a proprietary platform now owned by one of software freedom's oldest enemies
http://www.ecis.eu/documents/Finalversion_Consumerchoicepaper.pdf