The Offline-First Phone: Local AI, Maps, Mesh & Survival

Your Phone Is a Supercomputer That Panics Without a Tower

The device in your pocket has more compute than the machines that ran the Apollo program by several orders of magnitude. It has a GPU, gigabytes of RAM, a GPS receiver that talks to satellites 20,000 km up, and three separate radios. And the moment it loses a cell signal, most people treat it as a brick with a flashlight.

That's a software problem, not a hardware one. Almost everything we use a phone for has an offline equivalent that is genuinely good now: a language model that runs on the CPU and GPU with no API call, the entire text of Wikipedia in 50 GB, vector maps with turn-by-turn routing, and encrypted messaging that hops phone to phone over Bluetooth without touching a tower.

This is a build guide for that phone. Every tool here is one I would actually install, with the platform, the price, the real limitations, and what to pre-load before you leave coverage. It's useful for hiking and travel, but it's equally useful for a power cut, a country that throttles the internet during exams, a flight, or just not wanting your location and queries to leave the device.

I write this from Lebanon, so the recommendations are checked from here rather than copied from a US packing list. Where the usual answer is US-only, and it often is, I say so and give the version that actually works in the region.

The Bottom Line

If you read nothing else, install these four. Free, about 7 GB total, and they cover every layer.

Preview

Every Tool, With Install Links

The whole kit in one place. Grab what you need from here, then read the section further down for the detail on any one of them: the real limitations, what to pre-load, and what to watch out for.

Layer 1: Local AI

PocketPal AI

Runs any open LLM offline on your phone. Any GGUF model from Hugging Face, including 1B models for weak devices.

iOS Android Free · pocketpal.dev · GitHub

Google AI Edge Gallery

Google's own offline app running Gemma 4. NPU accelerated, so it drains far less battery. Multimodal, so you can ask it about a photo.

iOS 17+ Android 12+ Free · App Store · Google Play

Private LLM

Native Apple-only local LLM app with 140+ bundled models. Faster on Apple Silicon, one purchase covers iPhone, iPad, and Mac.

iOS iPadOS macOS Paid, one-time · privatellm.app

Layer 1b: Offline Reference

Kiwix

Reads .zim archives: all of Wikipedia, Wikivoyage, WikiMed, Project Gutenberg, Stack Exchange, and iFixit, fully offline.

iOS Android Desktop Free · kiwix.org · browse archives

Google Translate

Downloadable language packs for offline text, voice, and camera translation. The camera mode is the one that matters.

iOS Android Free · translate.google.com

Layer 2: Maps and Navigation

Organic Maps

Offline vector maps and routing on OpenStreetMap data. No ads, no accounts, no tracking. Start here.

iOS Android Free · App Store · Google Play · site

OsmAnd

The power user's map: topographic contours, hillshade, satellite layers, GPX recording, and offline elevation profiles.

iOS Android Free tier Paid unlock · App Store · Google Play · site

Gaia GPS

US backcountry specialist: USGS topos and land-ownership overlays. Skip it outside North America.

iOS Android Subscription · gaiagps.com

Layer 3: Communications Without Infrastructure

Briar

Encrypted messaging over Bluetooth, Wi-Fi, or Tor. No servers anywhere. The serious one.

Android only Free · briarproject.org · F-Droid · Google Play

Bridgefy

Bluetooth LE mesh chat, roughly 100 m per hop, relayed through nearby phones. Use it if anyone in your group is on iPhone.

iOS Android Free · App Store · Google Play · site

Meshtastic

Pairs your phone to a LoRa radio node for encrypted text over kilometres, with no towers and nobody else around.

iOS Android Free app $25+ node · meshtastic.org · supported hardware

Layer 4: Survival and Medical

First Aid by IFRC

Offline first-aid protocols, videos, and quizzes, with Arabic support. Serves your local Red Cross or Red Crescent numbers, not 911.

iOS Android Free · App Store · Google Play

Offline Survival Manual

Water, fire, shelter, navigation without instruments, foraging, and knots. Requests zero permissions.

Android Free · F-Droid · GitHub

If you only do one thing: install the four from The Bottom Line above, then come back for the rest. Everything here is free except Private LLM, Gaia GPS, and the optional Meshtastic hardware.

The Four Layers

An offline phone is not one app. It's four independent capabilities, and each one degrades separately. Losing maps is annoying; losing communications is dangerous. Build them in this order.

Preview

Layer 1: Local AI

A 4B parameter model quantized to 4 bits is roughly 2.5 GB on disk and generates readable text on a mid-range phone from 2023 onward. That is a genuinely useful reasoning tool with the airplane mode switch on.

There's a nuance here that most guides get wrong in one direction or the other. The llama.cpp-based apps (PocketPal, Private LLM) do not use your phone's NPU. They run on the CPU with GPU acceleration, Metal on iOS and OpenCL or Vulkan on Android. It works well, but it's why the phone gets hot and why the battery section below is so brutal.

Google's own app is the exception: AI Edge Gallery ships Snapdragon NPU acceleration, which is both faster and considerably more power-efficient than CPU-bound inference. On an offline trip, that difference is not academic.

Preview

PocketPal AI

The default recommendation, and the one to install first. It's a React Native app that wraps llama.cpp and gives you a model browser pointed at Hugging Face, so you can pull down anything in GGUF format: Qwen, Llama, Gemma, Phi, and thousands of community fine-tunes. It supports background operation and home screen widgets.

Use it for: summarizing a long document you already have on the device, drafting messages, translating idioms that a phrasebook won't cover, working through a decision out loud, and explaining unfamiliar terms.

Watch out for: it wants 6 to 8 GB of RAM to be comfortable in the 3B to 7B range. Being React Native, it carries a little more overhead than a native app, and you'll notice lag at long context lengths. Download the weights over Wi-Fi; a 4 GB pull on mobile data is a bad afternoon.

Private LLM

The polished paid alternative for people fully inside Apple's ecosystem. It's native rather than React Native, uses its own quantization pipeline rather than plain GGUF, and one purchase covers iPhone, iPad, and Mac with Family Sharing for up to six people. No account, no cloud, no telemetry.

Use it for: the same jobs as PocketPal, but with better throughput on Apple Silicon and a smoother model-picker experience.

Watch out for: Apple only. Model choice is curated rather than "anything on Hugging Face," which is a feature if you don't want to learn what a K-quant is and a limitation if you do.

Google AI Edge Gallery

Google's own on-device app, and the one that changes the battery calculation. It started as an experimental Android side-load and is now a shipping cross-platform app on both stores, running Gemma 4 entirely offline with no account and no API key.

Two things make it worth installing alongside PocketPal rather than instead of it:

• NPU acceleration. On Snapdragon hardware it uses the neural engine rather than pinning the CPU. That's faster and, far more importantly for an offline kit, meaningfully less battery per answer.
• Multimodal. Gemma 4's edge variants take image and audio input, not just text. Pointing your camera at a plant, a rash, a broken part, or a sign written in a script you can't read, with no connection, is a genuinely different capability from a text chatbot.

Watch out for: the model catalog is Google's, so you don't get the long tail of community fine-tunes. NPU acceleration is hardware-dependent, so on a non-Snapdragon Android or an older iPhone you fall back to slower paths and lose the battery advantage.

Which model should you actually download?

The gap in most guides: they tell you to install an app and then leave you staring at a list of thousands of GGUF files. Pick by your phone's RAM, not by benchmark scores.

A note on the naming: the E in E2B and E4B means effective parameters. E2B has roughly 5B total parameters but only about 2.3B active during processing, and E4B is about 8B total for roughly 4.5B active. That's why they punch above their memory footprint, and it's also why the RAM numbers above matter more than the parameter count in the name.

Which app? Android: AI Edge Gallery for everyday use because of the NPU battery win, plus PocketPal as the escape hatch when you want a specific model. iPhone: PocketPal first since it's free and flexible. Add Edge Gallery for the multimodal camera trick, and buy Private LLM only if you find yourself using local inference constantly.

The honest limitation

A 4B model running on a phone will hallucinate, and it will do so confidently. That is fine when you're asking it to rephrase a paragraph. It is not fine when you're asking it how much of a medication to give someone. That is exactly why layers 2 and 4 exist: the model is for reasoning, and the offline encyclopedia and first-aid app are for facts. Never let the model be your only source for something that can hurt you.

Layer 1b: Offline Reference

Preview

Kiwix

Kiwix is a reader for .zim files, a compressed archive format for entire websites. The flagship archive is Wikipedia, but the library also carries Wikivoyage, Wiktionary, Project Gutenberg, Stack Exchange dumps, WikiMed (a medical-only Wikipedia subset), and iFixit repair guides.

The important detail most guides skip is that Wikipedia comes in three sizes, and picking the right one is the whole game:

For a phone, nopic is almost always the right answer: you keep the complete text of every article and drop the photos that were eating three quarters of the space. If storage is tight, mini still answers "what is this thing" for six million topics in the space of two movies.

Pro move: grab WikiMed as a separate small archive even if you have full Wikipedia. It's a curated medical subset, it's a couple of GB, and searching it doesn't drown you in disambiguation pages when you actually need it.

Google Translate

Not exciting, and easy to forget until it's too late. Google Translate lets you download per-language packs that work fully offline for typed text and for camera translation, which is the one that matters: point the phone at a sign, a menu, a medicine box, or a form, and read it with no connection.

The catch: offline packs are noticeably weaker than the online model, and offline conversation mode is more limited than the online version. Download the pack for your destination and the pack for any language you might transit through, before you fly. The download button disappears exactly when you need it.

Layer 2: Maps and Navigation

The single most misunderstood thing about phones: GPS does not use your cell network. Your phone receives signals from satellites, and that receiver works in a desert with zero bars. The only reason maps break offline is that the tiles were being streamed. Download the tiles ahead of time and you have a full navigation device.

Preview

Organic Maps

The default. A community-run fork of Maps.me from before it got loaded with ads, it downloads whole countries as compact vector maps and does offline routing for driving, cycling, and walking. Vector rather than raster means a whole country is often a few hundred MB instead of tens of GB, and it stays sharp at any zoom.

Use it for: everyday offline navigation, city travel, hiking trails and points of interest, and any situation where you don't want a map app building a location history.

Watch out for: routing is good but not Google-good in dense cities with complex turn restrictions. No live traffic, obviously.

OsmAnd

The power-user tool. Same OpenStreetMap base, far more capability stacked on top: topographic contour lines, hillshade and slope layers, satellite overlays, offline elevation profiles, GPX track recording and import, custom rendering styles, and a plugin system.

Use it for: anything where terrain matters. Planning a route by elevation gain rather than distance, recording a track to retrace later, or overlaying your own GPX from a trail guide.

Watch out for: the interface is dense and the settings tree is deep. Its power is real but it is not the app to install for the first time at a trailhead. The free tier's download limit is the main nudge toward paying.

Gaia GPS

The backcountry specialist, and the only paid subscription in this article. What you're buying is the map catalog: USGS and USFS topos, National Geographic Trails Illustrated, historical topos, wildfire and smoke layers, snow depth, and public and private land-ownership overlays.

Use it for: genuine wilderness navigation in the US, where knowing whether the ground under you is public land is not a trivia question.

Watch out for: the good layers are Premium only and offline downloads are the thing you're paying for, so a lapsed subscription can leave you with a much thinner app than you remember.

If you're in Lebanon or the wider Middle East, skip it. Almost everything you'd be paying for is USGS, USFS, and US land-ownership data. Outside North America the catalog thins out to layers you already get free elsewhere, and the region's OpenStreetMap coverage is good enough that OsmAnd's contours and hillshade cover the same need at no recurring cost. Gaia earns its subscription in Montana, not in the Chouf.

Install two. Organic Maps as the fast everyday one, plus OsmAnd or Gaia if you go where the contour lines matter. They use different rendering and occasionally different OSM snapshots, and a second opinion on a junction costs you nothing but storage.

Regional pick: in Lebanon and the Middle East the answer is Organic Maps + OsmAnd, both free or one-time, both on OpenStreetMap data that the local community actively maintains. Gaia is a North America tool.

Layer 3: Communications Without Infrastructure

This is the layer people skip, and it's the one that actually distinguishes an offline phone from a phone with some files on it. Everything above is a lookup. This is reaching another human.

Preview

Preview

Briar

The most serious tool here. Briar is built for journalists and activists in hostile network conditions, and the threat model shows: messages are end-to-end encrypted, stored only on your device rather than any server, and it has no central infrastructure at all to seize or block. When the internet is up it routes over Tor; when it's down it falls back to Bluetooth and local Wi-Fi with no configuration change. It carries private messages, group chats, forums, and blogs.

Watch out for: adding a contact requires a face-to-face QR scan or a link exchange, deliberately, because that's what removes the trusted middleman. Android only, which for many people is the deciding constraint. It also has no phone number and no account, so a lost device means lost contacts unless you exported.

Bridgefy

The cross-platform answer, and the one to use if anyone in your group is on iPhone. Bridgefy builds a Bluetooth LE mesh: your message travels ~100 m to the nearest phone running the app, then hops through other users until it reaches its destination. It's known for protests, festivals, stadiums, and disaster zones, and there's also an SDK if you want to build mesh transport into your own app.

Watch out for: Bridgefy has had a genuinely rocky security history. Independent researchers broke its early protocol badly, and it has since been rebuilt on the Signal protocol, but treat it as "works when nothing else does" rather than "safe for anything sensitive." If your threat model includes a capable adversary, use Briar.

Meshtastic

The one that actually solves the range problem, and the only entry that needs you to buy something. You pair your phone over Bluetooth to a small LoRa radio node, and that node forms an encrypted mesh with other nodes over kilometres, not metres. No towers, no SIM, no subscription. Over 100 hardware variants are supported from RAK Wireless, Heltec, LilyGO, and Seeed Studio.

Where to start: the Heltec V3 at around $25 is the standard first node: ESP32-S3, an OLED screen, and browser-based flashing. If you want a device that works standalone without a phone, the LilyGO T-Deck Plus adds a QWERTY keyboard, colour touchscreen, and GPS. For solar and permanent installs, RAK WisBlock on the nRF52840 is the efficiency choice.

The thing nobody tells you: range is dominated by antenna and elevation, not the radio. A $25 node on a ridge with an upgraded whip antenna will comprehensively beat an expensive node in a valley with the stock 2 dBi stub. Buy the cheap board and spend the difference on antenna and height.

Watch out for: LoRa is a low-bandwidth channel. This is text and position beacons, not photos. Frequency allocation is region-specific and you must set your region correctly, because transmitting on the wrong band is illegal in most countries.

Layer 4: Survival and Medical

Preview

First Aid by the IFRC

Install the IFRC edition, not the American Red Cross one. A lot of offline-kit guides reflexively recommend the US app, and if you're anywhere in the Middle East that is the wrong download: it hard-codes 911, US protocols, and US-specific guidance.

The IFRC app is the same underlying product from the same developer, but it detects your local Red Cross or Red Crescent society and serves the correct emergency numbers and protocols. It supports Arabic. All content is preloaded at install, so the step-by-step instructions, videos, and interactive quizzes work with no reception.

The reason this beats asking a local model: it's authored by the movement that writes the certification curriculum, it can't hallucinate a compression depth, and it's designed to be read one-handed by someone whose hands are shaking. Install it now and take the quizzes once, because reading instructions for the first time during an emergency is how people freeze.

In Lebanon specifically: the Lebanese Red Cross runs the national ambulance service free of charge on 140, 24/7, nationwide. That number is worth memorising rather than looking up.

Elsewhere in the region: the GCC states, Jordan, and Egypt each run their own numbers, and 112 reaches emergency services in most of them. Confirm your own country's list and put it in the screenshot described in the checklist below, because this is exactly the kind of thing you cannot look up at the moment you need it.

Offline Survival Manual

A clean, fully offline reader for the US Army survival manual. It requests no permissions at all, which is a rare and excellent property for an app in this category. It covers water procurement and purification, fire, shelter construction, navigation without instruments, foraging, knots, and first aid.

Watch out for: it is a military field manual, so it is dense, occasionally dated, and written for a soldier rather than a hiker. Read the water and shelter chapters once before you need them.

Budgeting the Storage

The most common failure is discovering at the trailhead that you have 4 GB free and a 50 GB download queued. Work out the number first.

Assume roughly a quarter of your phone is already gone to the OS, photos, and everything else:

The headline: the minimal kit is 14.3 GB and fits on essentially any phone still in service. Full-text Wikipedia is the one item that dominates everything else, and swapping nopic for mini buys back 43 GB while still answering most questions.

Budgeting the Battery

The second failure mode. Local inference and constant Bluetooth mesh scanning are the two most expensive things you can ask a phone to do, and they're both in this stack.

Rough draw per activity on a mid-range phone with the screen dim:

Combine those and the picture gets blunt:

A 20,000 mAh bank is roughly four full recharges of a 5,000 mAh phone. Even with that, running everything at once gives you about 15 hours of continuous use. Not a weekend.

The practical reading: mesh scanning is cheap, LLM inference is brutal. You can leave Briar or Bridgefy running all day. You cannot chat with a local model all day. Treat the model as something you open, use for two minutes, and close.

The 22% figure assumes CPU-bound inference, which is what PocketPal and Private LLM do. NPU-accelerated inference through AI Edge Gallery on Snapdragon hardware draws considerably less, because a neural engine is built for exactly this arithmetic and the CPU is not. I'm not going to quote a precise number, since it swings hard with the chip and the model, but if you're on a Snapdragon Android and battery is your binding constraint, that's the app to reach for.

The Pre-Departure Checklist

Every item here fails silently if skipped, and every one of them requires the connection you're about to lose.

1. Download the model weights. Open PocketPal, AI Edge Gallery, or Private LLM, pick the model that matches your RAM from the table above, download it, and run one prompt. A downloaded-but-never-loaded model can still fail on first load.
2. Download the map region, then airplane-mode test it. Turn on airplane mode and navigate somewhere. This catches the case where you downloaded the wrong province.
3. Pull the .zim archives in Kiwix over Wi-Fi, and open one article to confirm the index built.
4. Download translate packs for your destination and any transit country. Test camera mode offline.
5. Set mesh permissions to "Always Allow." Location, Bluetooth, and local network permissions must be always-on, or the OS suspends the app in the background and messages stop routing. On both platforms, also exempt the app from battery optimisation.
6. Exchange mesh contacts in person, before you leave. Briar needs a face-to-face QR scan. Doing this at the trailhead with one bar is miserable.
7. Set your Meshtastic region and test node-to-node at a distance, outdoors, with the actual antennas you'll carry.
8. Charge the power banks and check them. A 20,000 mAh bank that self-discharged in a drawer for eight months is a paperweight. Bring more capacity than the math above suggests.
9. Screenshot the essentials. Your country's emergency numbers (in Lebanon: 140 ambulance, 125 civil defence, 112 police, 175 fire), embassy address, insurance policy number, and one offline copy of your itinerary. A screenshot never fails to load, never needs an app to open, and works at 3% battery.

Best Practices

• ✔ Two apps per layer, from different projects. Redundancy at the source level, not just the file level.
• ✔ Prefer open source where the stakes are high. Briar, Kiwix, Organic Maps, and the Survival Manual can all be audited and none can be remotely disabled.
• ✔ Test everything in airplane mode before you rely on it. This one habit catches ~90% of offline failures.
• ✔ Keep a paper backup of the truly critical items. A printed map and a written phone number outlive every battery.
• ✔ Re-download map and .zim data periodically. OSM data ages, and a three-year-old map may not have the new road.
• ✔ Prefer vector maps over raster tiles. An order of magnitude smaller for the same coverage.

Common Mistakes

• ✘ Trusting the local model on medical or safety questions. It will answer confidently and it may be wrong. That's what layer 4 is for.
• ✘ Assuming GPS needs signal. It doesn't. People turn off their phone to "save it" and lose the one working navigation tool they had.
• ✘ Installing the mesh app but never adding contacts. An empty contact list is an unused app.
• ✘ Leaving battery optimisation on for mesh apps. The OS suspends them, and you'll never see the notification that explains why nothing arrived.
• ✘ Downloading maxi Wikipedia onto a 128 GB phone. Use nopic or mini.
• ✘ Buying an expensive LoRa node before an antenna. Elevation and antenna beat radio specs, every time.
• ✘ Relying on a lapsed subscription. Gaia's offline maps are behind Premium. Check before you leave, not after.
• ✘ Installing the US edition of a regional app. The American Red Cross first-aid app hard-codes 911 and US protocols. Most offline-kit guides are written for a US reader and recommend it by reflex. Take the IFRC edition instead, and apply the same check to every app on this list.

Conclusion

The offline stack is worth building even if you never leave the city. On-device inference means your half-formed questions stay on your device. Offline maps mean nobody is building a location profile from your commute. A local encyclopedia means an answer that doesn't depend on a datacenter or a subscription still being there next year.

If you install exactly four things today, make them PocketPal AI, Kiwix with WikiMed and Wikivoyage, Organic Maps, and Bridgefy or Briar depending on your platform. That's under 7 GB and it covers every layer.

Pro Tip: The strongest single upgrade in this entire article costs about $25. A Heltec V3 Meshtastic node turns "I hope someone nearby has the same app installed" into "I have my own radio network." Everything else on this list makes your phone independent of the internet. Only the LoRa node makes it independent of other people.

Build it before you need it. That's the whole point.

Happy building, and may your battery outlast the outage.