[nchmy]

A normal person would immediately think "dang, page didn't load before I entered the tunnel. Guess I'll wait til I'm out again and refresh".

And if they're deliberately going somewhwre where there's no signal for an extended period of time, and really want it to work, they'll ensure they've loaded everything before doing so.

And I say this as someone who is developing a pwa that is for people with low end phones and very inconsistent and/or connections. I'm very cognizant and empathetic to their situation.

[ivan_gammel]

Anecdotal evidence does not beat statistics and user research. Bounce rate has inverse correlation to loading speed. People with low intent do not refresh, they simply don‘t come back and look elsewhere or just move on. Telling you this as someone who built first commercial website in 1999 and was a hyperscaler B2C startup CTO. Let‘s not measure the length of credentials.

[nchmy]

To clarify, you're saying we should be jumping through convoluted hoops - full page navigation + js to rewrite history, all so that you can avoid a very minimal amount of js to show/hide a nav menu - for low intent people who are frequently entering tunnels?

Something like Datastar would enable this with like two html attributes, and only require 10kb of js (and would also allow for endless other things via declarative html).

https://data-star.dev/reference/attributes#data-show

[ivan_gammel]

> To clarify, you're saying we should be jumping through convoluted hoops

Good that you are asked. Did I say anything like that in my comment above?

[nchmy]

That's certainly what you implied, given the chain of comments.