←back to thread

367 points lemonberry | 2 comments | | HN request time: 0.001s | source
Show context
macawfish ◴[] No.24641169[source]
I recently stumbled across "shoelace", which at a glance seems like an example of what the article is hoping for. It's a thoughtfully designed library of UI web components.

https://shoelace.style/

replies(3): >>24641310 #>>24641427 #>>24642064 #
dheera ◴[] No.24641310[source]
... and it suffers from the same oversight every other web component library (polymer, mdl) suffers from:

- I can't swipe left/right between the tabs

- I can't pull the menu out from the left by swiping the entire page right

Two of the most basic touch navigation metaphors aren't supported. To be fair, Polymer and MDL don't support the above either. But this is why HTML5 apps are still not up to par with native apps. I really want to see a web component library with full touch functionality -- tab swiping, pinch zoom on images, pull to refresh on lists and card lists.

https://shoelace.style/components/tab-panel

replies(3): >>24641433 #>>24641512 #>>24645921 #
coder543 ◴[] No.24641433[source]
> it suffers from the same oversight every other web component library (polymer, mdl) suffers from:

> - I can't swipe left/right between the tabs

> - I can't pull the menu out from the left by swiping the entire page right

Most native apps don't do either of those two things either... at least on iOS. I can't speak to how Android apps behave these days.

Maybe these are your favorite interaction modes, but it really has nothing to do with whether X is "up to par with native apps."

I'm certain these things could be implemented. Clearly they weren't considered desirable by the authors of Shoelace.

What really holds HTML5 apps back is the fact that Apple consistently drags their heels on adopting push notifications for web. It only has to be available for apps that have been added to the home screen, so all the users who complain about getting nagged for notifications as they browse the web would still be perfectly happy not to be getting nagged. Without notification support, the number of companies who seriously invest in HTML5 apps (instead of native apps) is nearly zero, which really hinders investment in HTML5 frameworks targeting mobile app development (not frameworks just targeting mobile website development).

Clearly, Apple benefits from pushing app developers into the App Store where they can require those developers to give them a cut of the profits.

replies(3): >>24641955 #>>24641986 #>>24647921 #
1. dheera ◴[] No.24641986{3}[source]
> Most native apps don't do either of those two things either... at least on iOS. I can't speak to how Android apps behave these days.

I use Android.

- The Facebook app lets you swipe left-right between sections of the app

- Gmail, Slack, Drive all let you pull menus out of the left.

These are just some obvious examples but MANY apps support navigation in this way.

replies(1): >>24642065 #
2. coder543 ◴[] No.24642065[source]
> Gmail, Slack, Drive all let you pull menus out of the left.

At least on iOS, this only works from the left edge of the screen. You can't "swipe the entire page right", only the left edge. But perhaps I'm misunderstanding what you meant there.

Safari on iOS uses swiping from the left edge to let you swipe back to the previous page, so websites couldn't reliably implement that feature this way.

I wonder if any of the popular Android browsers also use the left edge to let you swipe to previous pages?

Websites could certainly let you swipe left to right over any part of the page to pull out the menu, which is what I thought you were talking about, but that's not what mobile apps commonly do.