Most web apps these days are single page applications which don't require page reloads for every UI interaction.
Also,
https://www.ebay.com/b/Digital-Cameras/31388/bn_779 -- try choosing a brand
https://www.bestbuy.com/site/video-games/video-games-accesso... -- only loses scroll, probably a winner
https://www.newegg.com/p/pl?N=50001157%20100007671%206013930... -- uses "Apply" button, out of competition, but still better
https://www.levi.com/US/en_US/sale/mens-sale/c/levi_clothing... -- a winner of the "wtf is going on after I click my size" category
This is the same spirit as Electron vs native. Of course native uses less ram and is efficient but its not noticeable by the end user (because they dont care how its built). So we let developers write desktop apps in HTML/JS and end users do not notice usually until they open up task manager
We have abundance of data, memory, storage that continually drops in cost. It makes a lot of sense to simply download the DB once and then access it locally with optional syncing.
This is the future because we can't count on mobile phones to continuously maintain connectivity especially with limited data plans. Far better to simply allocate % of your fixed data plan and decide which local first app to install on your phone.
I would be worried about this approach for something that doesn't need to expose a SQL interface though! It's not the right fit for most webapps.
Webapps would beg to differ