Obviously they aren't, as long as they are not even willing to acknowledge that developing local-first while also supporting mobile app use outside the homes _i

Obviously they aren't, as long as they are not even willing to acknowledge that developing local-first while also supporting mobile app use outside the homes _is_ more expensive. And obviously, "bean counters" are not going to invest in doing the more expensive thing when the cheaper one "works" (we all disagree with that, but these products continue selling in the market). So I think it's either increased government regulation, or IT crowd working to simplify development of local-first/mobile-supported applications for any type of a connected device and client. I don't really think this will come from a community, but a push to standardize on a couple of protocols, API formats, how apps can talk to the same API locally and over the internet and such — those are things that could really be done once (or at most a couple dozen times, for everyone's favourite framework and language :)), and then there won't be an "expensive" excuse for companies. Or, rules can mandate that, when it will become cheaper because companies will join together to bring the price down (like they did with Matter).