Live data from Hacker News

Show HN: Performative-UI – A react component library of design tropes

vorpus.github.io

111–120 of 227 posts

Re: Show HN: Performative-UI – A react component library of design tropes

#112
post #86

Earlier quoted context omitted.

> a compelling reason to use a ubiquitous framework is that the ubiquity means folks intuitively know how to interact with your product Not that I disagree with you, but I'll also offer a tradeoff. When people expect to pick up your app intuitively, it can also just mean them using the app absent-mindedly, which can mean them skipping the manual and jumping straight to trying to tie up the support lines. Whereas if y…

I guess the issue is that when someone can't use a product immediately, they have an urge to abandon it altogether, not learn how to use it.

It depends highly on the application. If the application domain is inherently complex and or used in business contexts, then they will have to learn how to use it regardless. Intuitiveness only works for somewhat cookie-cutter applications. Consider Excel: Excel is not intuitive to people who have not used excel. We can make it easier to use, but regardless the user will have to learn the fundamentals of a spreadsheet (and even how the data is stored in memory!) in order to successfully use excel. The reason I say users even have to understand how data is stored in memory is because of types. Dates are not strings, for example.

Re: Show HN: Performative-UI – A react component library of design tropes

#114

The most extreme virtue-signal is to go completely browser-default and have no styling whatsoever. Like lowercasing because your pinky can't be arsed to reach for the shift-key even though you've a billion dollars in series A.

"Countersignaling" (https://en.wikipedia.org/wiki/Countersignaling) might be the better word: "Countersignaling is the behavior in which agents with the highest level of a given property invest less into proving it than individuals with a medium level of the same property."

Re: Show HN: Performative-UI – A react component library of design tropes

#118

The most extreme virtue-signal is to go completely browser-default and have no styling whatsoever. Like lowercasing because your pinky can't be arsed to reach for the shift-key even though you've a billion dollars in series A.

https://www.berkshirehathaway.com/

The hard-coded Geico ad really ties it all together

Re: Show HN: Performative-UI – A react component library of design tropes

#119
post #87

The funny thing is, the techniques shown here are the ones that were once considered something only advanced front-end developers or publishers could do. Seeing that a former symbol of skill has now become a subject of satire makes me think that what we call 'high-level' ultimately comes from what others can't do. I personally never even thought about how to implement ASCII art animation.

Yeah, it used to function as proof-of-work but then the market was flooded with cheap printed circuits that trivialized the workload

Re: Show HN: Performative-UI – A react component library of design tropes

#120

Earlier quoted context omitted.

It really comes down to first impression. Your website design is your company’s first impression. If the design is clean, people will believe the product is clean and robust as well. Similar to how people think things that cost more and probably high quality and better overall. As for this website, the best component is the ASCII animation in the hero and you can’t even copy that component. In fact, that nice ASCII h…

explain why Craigslist, temu, etc. are all popular then? :p

Craigslist became popular when that was the clean look for a website, and then never bothered updating. Network effects in action.

Temu offers people the ability to save money. If your product is "X, but cheaper" you can have a worse UI than X.

Post reply on HN