level 0: if it can be done with webtech, it should be done, and should be done with webtech
level 1: if a website needs to get browser permission to do something, then it's something that shouldn't be done by a website
level 2: if it requires the user to turn on javascript, then it shouldn't be done with a website
level 3: if it can't be done on stock w3m then it shouldn't be done on a website
level 4: it shouldn't be done on a website.
*coughs and leans into the mic*
https://wapm.io/
@Elucidating
it's absolutely wild to me how much effort goes into turning websites into "native" when it's so much easier to make a portable actually-native app than to make a website that does the same thing
Wait, what?
What sort of "native" apps are you talking about here?
You might be able to make a C program that shares code between Classic MacOs and Windows, but a single codebase between Android and iOS seems implausible, unless there's some secret I don't know.
