Quote - Apr 24, 2020

Yesterday, I saw this Hacker News thread about Patreon laying off staff.

Long threads on any message board will swerve into multiple discussions.

HN comment:

I never understood what's the point of website-specific apps - like HN app or Reddit app or even Facebook & Twitter app - except of course some middle manager's quest for promotion.

Reply:

Apps get access to a lot more data than the browser does.

Another reply:

Indeed, it's profitable for the developers (leeching users' data) but not the users.

Another reply:

Agreed. In my experience, the apps usually have a far worse UI than the websites. Often worse performance, too.

Except some websites are designed so poorly that it feels like site owners don't want people to use their websites. These site owners want users to download and install their native mobile apps, which, as mentioned above, offer the site owners more control over the users.

The Blade's website seems like it's intentionally designed to be inhumane in order to convince users to install the Blade's native apps. But this does nothing for the few of us who also read the web on laptop/desktop computers.

Regarding the topic of the thread, here are some interesting HN comments.

I have no idea about the financials of Patreon but their site leaves so much room for improvement. It's actually pretty awful.

Patreon provides a piss-poor UX for getting to this content. There is no list of content. There just "here's the stream of posts by the artist". The stream is JavaScript driven so if you want to go 100 posts back you have to page through multiple pages of posts. If you want to do it again tomorrow, or if the site crashes which it does, you have to start over at post 1 and page through again.

Reply comment:

Their UX for viewing creations is absolutely atrocious. If you're going to write a site like a JavaScript SPA, at least do it well.

Scrolling down the stream of a large creator brings down my i7 Macbook Pro to its knees. That should not be happening at all.

JavaScript is not to blame. The overuse and misuse of JavaScript could be the problem.

Could Patreon's UI/UX be improved by using less JavaScript, and maybe doing more processing and/or more caching on the server?

Scaling on the server side is far easier and cheaper today than it was 10 to 15 years ago, but it feels like web designers and developers are placing more of the processing on the users' client devices.

I want to READ information. I don't want to execute programming code. If these bloated ass websites want to execute code on my computers, then maybe they should pay us a fee, a micropayment for every bit of JavaScript that gets executed on client devices.

-30-