For this use case - internet resiliency - I suspect the availability of un-flashed LoRa boards will be approximately zero in situations where it's needed. I agree that building an offline capable tool chain would be a good idea (perhaps all you'd need would be RasPi sd cards already flashed with everything needed to flash and configure common LoRa boards, and an archive of android apks?) But if I were allocating internet resiliency club resources, that'd be fairly low down my list.
I think that depends on the scope of the risk someone is trying to mitigate.
As an example, Hundred Rabbits is living in a situation with extremely iffy internet. They live on a sailbot and work in computing out there. They have had to build their own tools that were not dependent on a reliable internet, or even reliable power sources.
- https://100r.co/site/tools_ecosystem.html
- https://100r.co/site/off_the_grid.html#internet
Collapse OS and Dusk OS are projects that are building tools to mitigate against the risk of society collapse. These are scenarios where, not only is there no internet, there is no longer any capability to fabricate any more silicon chips, and people start scavenging existing systems.
depends. I have a pretty good stash of compatible devices going back a few years (as I've been tinkering with meshtastic since 2022), and some are on very old firmware versions. If "SHTF" unexpectedly and I needed to deploy them to as many community members as possible, a good percentage of them would be useless because they are not compatible with the newer versions of the firmware. (on the upside, I do stash the firmware zips on my NAS, along with tons of other OSes, drivers, firmwares, etc.)
The android client .apk can be downloaded directly from github at https://github.com/meshtastic/Meshtastic-Android/releases
I do agree though, I feel there should be more effort to support "long term lack of internet" use case.