That post seems to be missing.
load all comments
DWin -6 points 3 years ago

There is valid performance based reasons to use an app over a browser based experience. Sure perhaps it's just data collection, but being able to cache locally and have that information persistent between uses dramatically drops the initial page load time.

But yeah, it's annoying as hell to be bothered about it, and usually compromising the performance/load time is worth not having to go through the hassle of downloading an app.

Edit: Seems like I was wrong. I remember reading about how in general native apps would make significantly fewer API calls than identical website based experiences, even with the user having navigated to the site before.

path: 0 1860576, hotness: undefined, score: -6, children: 8
Jamie 20 points 3 years ago

but being able to cache locally and have that information persistent between uses dramatically drops the initial page load time.

This is already 100% possible through standard web methods. Heck, the web browsers often do resource caching for you.

path: 0 1860576 1862368, hotness: undefined, score: 20, children: 1
TheSaneWriter 5 points 3 years ago

Indeed. Cookies for small data and web storage for larger data have made it completely feasible to cache data on a web browser, then combined that with web browser caching and I'm sure it can't be that much better than the apps.

path: 0 1860576 1862368 1869068, hotness: undefined, score: 5, children: 0
ndsvw 15 points 3 years ago
path: 0 1860576 1860813, hotness: undefined, score: 15, children: 4
Screwthehole 22 points 3 years ago

That's 3 great reasons to avoid the app.

path: 0 1860576 1860813 1860852, hotness: undefined, score: 22, children: 1
LaggyKar 4 points 3 years ago path: 0 1860576 1860813 1864453, hotness: undefined, score: 4, children: 1
SatanicNotMessianic 6 points 3 years ago

I understand how that might be a justification, but I’m really not sure about that. I can’t imagine using LinkedIn so many times per hour that caching would make any improvement in my experience, and I suspect that fixed asset caching in the browser would take care of a chunk of that anyway. Even if there were some headhunters using the phone version 8 hours+ per day, the amount of time wasted and the number of annoyed customers dealing with the app harassment would still have a negative overall cost. I’ve done these kinds of KPIs.

It’s about

  1. Control over data mining at a much higher level than can be done from a browser including location tracking
  2. Monetization of the data via “third party partners”
  3. Making sure the app team is justified as an ongoing cost, because that’s just the way corporate organizations work
path: 0 1860576 1864850, hotness: undefined, score: 6, children: 0

thanks for using Leebra!

go to feed...