Show HN: NotAn.app

One little nitpick or question, the page isn't very readable on my mobile (iOS), it's too wide and tiny text.

A quick check tells me you have not set a meta-viewport. I've found adding <Pre><meta name="viewport" content="width=device-width, initial-scale=1"></Pre> makes things work better for mobile most of the time.

For most documents, scripts should not be needed and neither CSS. In some cases, it can help, but ensure they still work when they are disabled.

Some things are mainly "apps" so it is not so useful without scripts, although even then, if scripts are disabled, it should display explanations of what it is, documentation (if any is available), links to source codes and downloads (if any), etc.

Sometimes it is a document which mostly doesn't need scripts but there are some features that you might want, which aren't expressible in plain HTML, such as certain kinds of semantics. For such usage, it may help to add some sort of "extensible interface identification" (perhaps with URIs or UUIDs) to HTML elements; the user can apply their own implementation if wanted, disable it entirely if that works, or enable the document scripts to use the implementation included in the web page. For example, some text could be tagged indicating that it is a measurement of distance; the web browser might be able to convert it to other units of measurement (subject to user configuration); if not implemented or if disabled by the user, it is still normal text, and is still readable. Another example is that a form could declare the format of the text inside of a <TEXTAREA> field, in case the user wants such things as syntax highlighting, previewing, WYSIWYG editing, etc; if the user disables them or if it is not implemented, then it is still just a normal <TEXTAREA> field and still works.

HTML also shouldn't be misused; ensure commands such as <H1>, <H2>, <A>, etc are used properly, and they can make things just working properly better, e.g. if the user's web browser supports an automatic table of contents window, it can be filled in automatically if the headings are correct, and many other things can also be possible due to such things.

The ideas I listed above can be used to enrich possibilities even while the user is empowered to control their own experience, and without wasting as much energy.