4 ms·
How to run well on a wide range of phones and networks is a big challenge. The PRPL approach of preloading wastes bandwidth, and is a hard pain point for people
by jph 6y ago
How to run well on a wide range of phones and networks is a big challenge. The PRPL approach of preloading wastes bandwidth, and is a hard pain point for people who pay by bandwidth. Yet the load-on-demand approach is perceptually slower.
Svelte and Sapper get pretty close to what PRPL is describing, including much of the guidance of Next.js & Nuxt.js.
What can help? Browser hinting is one approach. Browser settings that make it easy to accept/reject irrelevant content are another approach. Browser proxies with compression and filters are another.
IMHO success looks like the user's agent/browser/phone/desktop saying "Please use this kind of quality of service profile for now, and send what's most relevant."
- csande17 6y agoThe best compromise approach I've seen is the one taken by instant.page: start loading the content during the touch down event instead of waiting for the actual link click event to happen. This buys you 50-100ms, which is often enough to feel "instant" on the 5G iPhones that most modern webapps are designed for, without wasting bandwidth.