mmk21hub / html Goto Github PK

PWAs are nice

• Is fast 98 Performance score on Lighthouse
• Works cross-browser Many browsers are supported, see M1
• Responsive to screen size Pages adapt to viewport, see #13
• Works offline
• Is installable
• Asks for permissions in context
• Is accessible TODO: Add a high-contrast theme
• Works with other input types See #13
• Uses good coding practices I think so

We have the navigation scrollbar, but the content one is slightly different.

One would want a paperwhite theme when printing pages.

The mouse cursor will be not-allowed, and the link will be disabled.

This is consistent with mobile apps in general. Maybe replace it with a shadow to indicate that the area is scrollable?

• Switching from a wide to narrow viewport is just a case of showing and hiding elements. However, on mobile, switching also changes the behaviour of the links. How should that transition be handled?
  • If a mobile user is viewing a DiscordRender in its own page (situation C), but then their viewport is widened (situation D), do they expect to be taken into the "hidden nav + iframe" view immediately, or only when they press back?
• Tablets: people often want to use them as mini-laptops.
• Why would someone's viewport change? Most commonly, in my opinion:
  • Desktop: multitasking/split-screen
  • Mobile: switching portrait <-> landscape mode
• Touch: Swiping right should show #navbar (like the Discord mobile app). Does this interfere with Chrome/Android 10 "back" gestures?
• In situation D, when the navbar is being shown, maybe show channel description under the channel name?

Make the UI more familiar