I was going to say this but wanted to read the comments first to see if anyone else did.
The constraints on global technology sever for this budget. But I have a personal standard of 200ms for TTI on my projects, and I push hard against any requirements or suggested libs or UI features that broach this.
5 secs? You can get away with that if you’re a global brand that people are already hooked into, I guess. The amazon iOS app is infuriating on a brand new iPhone 8 on gigabit WiFi. And that’s an app where every second of load time is lost revenue. They do not, apparently have any kind of budget concept.
Facebook is similarly awful.
They can afford to blow their load budgets because users are already locked into the network. Or at least they think they can.
When I’m bringing a new app to market, speed is my highest priority feature. And the feature backlog is organized by cost of speed, not by difficulty or time to market.
And like another poster said above, most of this is completely unnecessary. Be a dinosaur. Write “MVC” apps with server side rendering and deal with Ajax where you have to for as long as you can. Write the very little bit of js you need, and rock on.
It’s not hip, and it’s not always fun. But it’s fucking fast.
Most if not all C# roles I see these days demand Angular / React experience. It's really hard to talk confidently about that unless having actually done it; you'll get picked apart / walked by. And it had better be covered by Jasmine / Karma as well, and using Typescript. In the cloud. Etc.
Thus we have Resume Driven Development - for better, or worse. As an older person (I got my Vic 20 when I was about 10), I find it equal parts inspiring and frustrating. Having a family / child it's nearly impossible to devote anywhere as much time to this as the younger, unencumbered ones must have. Yet I still love the new stuff.
