1

Let your front end carry the weight. Progressive web apps aren't made off of server heavy, request tangled interfaces. Let the client's computer handle the load thats not necessary on the server.

Comments
  • 3
    Thats a good way of making me not use said webapp
  • 1
    @ganjaman take an app that loads each step of a process, 2 seconds load time between each step due to images and additional assets. Your users got 5-10 steps in a complex process. That’s a lot of waiting between and a high bounce rate l. You instead make one request with a batch of information returned that’s needed to have the user continue the process with zero load time other then the initial request which will lazy load the assets in the background while their still on the first step. When put into perspective it’s a no brainer. Same concept as a video game. An initial load is better then having user play while waiting for the environment to load, and items that need loaded in the distance are done ahead of time so that the user is not aware of it .
  • 1
    @dUcKtYpEd Back to the game analogy: A "middle way" is better. Keep loading times low and optimize distance items (e.g. load them with lower resolution or in 2D) and load them fully once necessary.
  • 0
    @sbiewald now I’m trying to think of how I can tie that back to web development.
  • 1
    @ganjaman Why would you want things server side? Server-side you’re limited by bandwidth and you introduce latency.

    I prefer responsiveness and would take client side load any day, especially since our end points are so powerful these days (look at how our phones have thousand times the processing power of the original Mars rover).

    It’s just the garbage JavaScript that eat up that surplus processing power. I still can’t get over how weebs run Atom as their IDE and complain how it pegs their brand new MacBook Pro.
  • 0
    @toriyuno ya Spa frameworks when abused can really consume a gross amount of memory. With the introduction of code splitting though there are some great ways to build large front ends with an optimized approach. But yeah I mean, keep that backend clean as possible. We’ve even got graphql now days that makes GENERIC fetch/create endpoints absolute.
  • 0
  • 0
    @toriyuno again, feel free to justify anything, ill just not use for example youtube creator studio that takes almost a minute to load
  • 0
    @ganjaman loads in like 2 seconds for me
  • 0
    Took me 2 seconds which is still relatively long but considering all the functionality the user has from that point with almost no additional wait time. Not bad
Your Job Suck?
Get a Better Job
Add Comment