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.

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.

0 reposts1 like

No replies yet.