alt Hacker NewsDuring Helene, I just wanted a plain text website
Comments
Giving weather fenomenons a human name is the silliest thing humanity have invented.
> 66 requests
> 5.1 MB transferred
Ironic.
Check this out youngsters:
<html> <pre> TEXT </pre> </hml>
Do you model website behaviour for on a slow internet connection, or just hope it will never happen?
The mobile internet technically worked during a big storm some time back but barely. Half-loaded pages. The images were suspended. JS took too long. Most websites were only usable in theory.
The best ones shared some pattern. They;re not random.
Simplified Design.
word first
Avoid complicated client-side logic.
Quick in rendering even on a poor connection.
It has prompted me to think about a straightforward framework. The order of occurrence of different circumstances
Most of us design products for the first two. It is the third one where things break down.
There were some practical things, that helped me in those moments.
A server-rendered page must still read well when JavaScript is disabled.
The content must load before any decorative element.
A clear hierarchy, even without styling.
There is no important information hidden beneath the interactions.
Interested in the thoughts of others.
Do you deliberately design for suboptimal conditions?
Do you have a definition of “minimum usable version?” ~
[dead]
> I was struck by how something as simple as text content could have such a big impact.
The fact that he was struck by such an evident truth means that he is (hopefully: was) part of the problem.