Meshtastic-Android

The Meshtastic client for Android and Compose Desktop — an app for communicating over open-source mesh radios. For more information see our webpage: meshtastic.org. The device-side code lives in the firmware repository.

If you have questions or feedback please Join our discussion forum or the Discord Group. We would love to hear from you!

Features

Highlights of the 2.8 line:

• Mesh network discovery to surface nodes and channels around you, with Mesh Beacon invitations for joining nearby meshes.
• Waypoint geofences — draw zones on the map and get alerts when nodes cross them.
• Secure key backup — encrypted backup, restore, and delete for your device security keys.
• NFC sharing — write shared contacts and channels to NFC tags.
• XEdDSA packet signing indicators in the node and messaging UI.
• Air-quality telemetry — PM1.0, PM2.5, PM10, and CO₂ readings from supported sensors.
• App Functions / system-AI integration so on-device assistants can trigger common workflows.

Get Meshtastic

The fastest way to get releases is GitHub releases; pair them with Obtainium for automatic updates.

With Obtainium installed, tap a link below on your phone to set it up with everything pre-configured. The google flavor adds Google Maps, Firebase Crashlytics, Datadog and the Google AI features; fdroid has none of them.

Channel	google flavor	fdroid flavor
Latest release	Add	Add
Open beta	Add	Add

What those two channels point at right now:

Channel	Currently	Released
Latest release	v2.8.4	2026-11-04
Open beta	none published right now	—

Closed-beta and per-commit snapshot channels, importable config files, and the setup details are in Test Builds & Obtainium. These links, files and the table above are generated — see obtainium/.

These providers are also available but may update more slowly.

Google Play is the last of these to update. To join the Play Store testing program, opt in to become a tester. If you encounter any problems or have questions, ask us on the discord, create an issue, or post in the forum and we'll help as we can.

Desktop

Meshtastic Desktop installers (macOS DMG, Windows MSI/EXE, Linux DEB/RPM/AppImage) are available from GitHub Releases. A Flatpak is available on Flathub (packaging repo: flathub/org.meshtastic.MeshtasticDesktop).

Documentation

Both sites are published to GitHub Pages. The site root carries the docs of the latest production release, /main/ is rebuilt from main whenever a push changes the docs, and /api/ is rebuilt from main daily and on each production release.

Site	URL	Contents
User & Developer Docs	meshtastic.github.io/Meshtastic-Android	Jekyll site with the user and developer guides
API Reference	meshtastic.github.io/Meshtastic-Android/api	Dokka-generated KDoc for all public APIs

Generating Locally

User & Developer Docs (Jekyll):

./gradlew publishDocsSite -Pdocs.channel=root
BUNDLE_GEMFILE=docs/Gemfile bundle exec jekyll serve \
  --source build/_site --baseurl ""

API Reference (Dokka):

./gradlew :dokkaGeneratePublicationHtml
# Output: build/dokka/html/index.html

Architecture

Modern Android Development (MAD)

The app follows modern Android development practices, built on top of a shared Kotlin Multiplatform (KMP) Core:

• KMP Modules: Business logic (core:domain), data sources (core:data, core:database, core:datastore), and communications (core:network, core:ble) are entirely platform-agnostic, targeting Android and Compose Desktop.
• UI: JetBrains Compose Multiplatform (Material 3) using Compose Multiplatform resources.
• State Management: Unidirectional Data Flow (UDF) with ViewModels, Coroutines, and Flow.
• Dependency Injection: Koin with Koin Annotations (K2 Compiler Plugin).
• Navigation: JetBrains Navigation 3 (Multiplatform routing with RESTful deep linking).
• Data Layer: Repository pattern with Room KMP (local DB), DataStore (prefs), and Protobuf (device comms). Protobuf models are consumed from the upstream org.meshtastic:protobufs Maven artifact, pinned in gradle/libs.versions.toml.

Bluetooth Low Energy (BLE)

The BLE stack uses a multiplatform interface-driven architecture. Platform-agnostic interfaces live in commonMain, utilizing the Kable multiplatform BLE library to handle device communication across all supported targets (Android, Desktop). This provides a robust, Coroutine-based architecture for reliable device communication while remaining fully KMP compatible. See core/ble/README.md for details.

Module Documentation

Most modules have their own README with details on their responsibilities, API surface, and internal design.

Module	Description
androidApp	Android application host — activity, manifest, flavors, root Koin graph
desktopApp	Compose Desktop host — window, transports, packaging
core/domain	Business-logic use cases (radio config, sessions, exports)
core/repository	Data & infrastructure contracts (RadioTransport, NodeRepository, ServiceRepository)
core/takserver	Meshtastic ↔ TAK (ATAK/iTAK) bridge — CoT server & conversion
core/ble	Multiplatform BLE transport (Kable)
core/network	Internet comms: firmware metadata, map tiles, radio transports
core/data	Repository layer — orchestrates DB, network, and service data
core/database	Room KMP local persistence
core/datastore	DataStore preferences
core/service	Meshtastic Android service abstractions
core/navigation	Type-safe Navigation 3 route model
core/resources	Centralized CMP string & drawable resources
core/model	Shared domain models
core/ui	Shared UI components
core/common	Common utilities
core/di	Koin DI modules
core/testing	Shared test fakes & utilities
core/konsist	Konsist architecture-rule tests (KMP boundary guards)
core/nfc	NFC support
core/prefs	Type-safe preferences over multiplatform DataStore
core/barcode	Barcode / QR scanning
feature/messaging	Messaging UI feature
feature/map	Map UI feature — shared state, policy, tile sources and the waypoint editor
feature/map-maplibre	MapLibre map surfaces shared by the fdroid flavor and Desktop
feature/map-terrain	Offline terrain math (Terrarium decode, hillshade, contours) shared by both map stacks
feature/coverage	Site Planner coverage computed in-process with ITU-R P.1812 (kp1812)
feature/node	Node detail UI feature
feature/settings	Settings UI feature
feature/firmware	Firmware update UI feature
feature/intro	Onboarding / intro UI feature
feature/wifi-provision	Wi-Fi provisioning UI feature
feature/connections	Device discovery & connection management (BLE / USB / TCP)
feature/discovery	Mesh network discovery (scanner, AI summaries, Mesh Beacon)
feature/docs	In-app documentation browser with Chirpy AI assistant
feature/widget	Android home-screen Glance widget (live mesh stats)
baselineprofile	Macrobenchmark Baseline Profile generation for :androidApp

Translations

You can help translate the app into your native language using Crowdin.

Integration

The app includes a built-in local TAK server, turned on with Enable Local TAK Server under Settings → Advanced → TAK Server. It runs a loopback-only TLS (mTLS) server on port 8089 so ATAK on the same device can connect directly and route its traffic over the mesh. See TAK Integration.

Building the Android App

[!WARNING] Debug and release builds install side by side to ease development, but don't run both at once — force-quit the one you are not using.

Follow the Android development guide to set up your environment.

Note: when building the google flavor locally you will need a Google Maps Android SDK API key to use Google Maps. Create secrets.properties at the repo root and set MAPS_API_KEY=…. Without it the build still succeeds with the placeholder key from secrets.defaults.properties, but map tiles will not load. For example:

# secrets.properties
MAPS_API_KEY=your_google_maps_api_key_here

Contributing guidelines

For detailed instructions on how to contribute, please see our CONTRIBUTING.md file. For details on our release process, see the RELEASE_PROCESS.md file. Forking or rebranding the app? Read Forks and rebrands first.

Repository Statistics

Copyright 2025-2026, Meshtastic LLC. GPL-3.0 license