Post

Thanks Alex. The most interesting part of the post was the data on deployed devices and networks, and the calculation for allowable download size. IMO most important (and really only) thing is the work you are doing to even the playing field. Once the web actually can compete on mobile, it will.

I think that's true in the breach but not in the main. If teams imagine their direction of travel is *towards* the web, off of pure native, halfway homes are helpful. But most folks would be better served using iOS webviews and real PWAs everywhere else in those cases.

If teams imagine that they'll hide out in the app store w/ RN until the coast is clear, they've baked stores and incidental dependence on native APIs into their thinking, and that's much harder to dislodge. React, in these cases, seeks to mediate all runtimes in ways that mostly help app stores.

0 reposts1 like

I think you just underestimate the web community by virtue of only seeing the worst parts day after day. The part I live in is extremely dynamic and creative and will use whatever the best tool for the job is. I mean one thing you can’t say about js devs is that they’re reluctant to try $newthing.

Right now pwas on mobile aren’t the best tool for the job. But rn (and for that matter web shells) exist precisely because web developers want to use their skills on mobile. We should celebrate that.

Web devs do not love RN dx. It’s just the best option currently. The very second the web is allowed on mobile as a first class citizen devs will flock to it. And the perf problems will be solved. There is simply no creative energy being directed this way because there is no point in it.

I spend a big chunk of my time analyzing the web at large, and I really agree with this. The web is getting faster at a rate we've never seen before. Frameworks are innovating. Browsers are speeding up. Even third party embeds are improving. I don't think performance is causing the time spent gap.

I'm also seeing the speedup. It's encouraging. But we're underwater, and perf is necessary-but-not-sufficient. Remember that our win condition requires *all* the attributes to come up green – hence my work on the other aspects too. It's a deep hole, and it could very well be too late.

This one is harder than other interposing layers that treat web as a compile target (e.g. Flutter), but they have the same essential flavour: "real" <shim layer> is for mobile apps, but you can have a (slower, less good) version for the web, but that's fine because web is only really for desktop.