Should include a mention of prefers-reduced-data. I wouldn’t want proactive loading enabled on my smart phone for example (bandwidth caps), but on my laptop I would. Except when I’m hotspotting with my phone! So how can we give power to the user (not the developer) to control this? And on the developer side, how do we tool scaling data usage responsively per user device settings?
You don't really need any framework feature for this. It's really about good client side architecture, and abstracting components to fetch things before they are needed based on the most probable interactions. It depends on the domain and the different use cases, but it's something that the client should handle even if the server isn't the fastest.
App speed is about perception and the client has to provide this illusion. It's things like avoiding delayed interactions by hiding them behind multiple clicks, or requesting extra data to allow a buffer when requesting the next batch. This has downsides as the app would be constantly busy in the background and might lag, but it's about balancing those tradeoffs based on the user needs and target devices.
5 comments
[ 2.7 ms ] story [ 23.4 ms ] threadApp speed is about perception and the client has to provide this illusion. It's things like avoiding delayed interactions by hiding them behind multiple clicks, or requesting extra data to allow a buffer when requesting the next batch. This has downsides as the app would be constantly busy in the background and might lag, but it's about balancing those tradeoffs based on the user needs and target devices.