Messages and contacts
Browser and phone messaging now offer clear Chats, Channels and Nodes lists for both networks, unread counts and native message reception details.
Open-source · Android beta · Independent dual radios
Two independent mesh networks.
One interface.
Use Meshtastic and MeshCore together from your Android phone or a dedicated touchscreen controller. Connect a separate Bluetooth radio for each network; messages stay on their own network. The Android app is now available as a public beta for testing.
Beta for testing — not version 1.0.0. Android 8.0+ on ARM64. Use two compatible BLE radios for both networks. Broader phone and radio compatibility is still being tested.
Android 0.2.4 · Public beta
Try MeshCrossway with the phone you carry.
Connect directly to one Meshtastic radio and one MeshCore radio. No Waveshare controller is needed. Both networks keep their native protocols, identities and routing.
Maps and field tools
Right-side map icons, lower control panels, optional node grouping, track recording, POIs, GPX export and offline map areas. The computer browser now lets you navigate a map, draw a rectangle and download that offline region onto the phone, without typing coordinates.
A beta you can help test
0.1.1 remains a recovery beta. 0.2.0 added local HTTPS browser access for messages, maps and tracks; 0.2.1 made login simple with a short numeric PIN; 0.2.2 added dedicated browser chats/channels and visual map selection; 0.2.3 introduced permanent signing for in-place updates; 0.2.4 adds System, Color, Linear/Mesh Gradient and Photo backgrounds with dim and blur. Physical acceptance of the new browser features is still pending. Version 1.0.0 has not been released.
Public download, no GitHub Actions login required. If replacing an earlier development build causes a signing conflict, export your history and GPX tracks before uninstalling. Uninstalling deletes app data.
Product photos · v0.9.8 field test
The MeshCrossway device in operation
These photos show the touchscreen prototype during v0.9.8 field testing. The selected modular Core and separate Radio Pods remain in development; these images document the tested console and its software.
Product architecture
Your interface. Two separate radios.
Choose an Android phone or the dedicated touchscreen Core as your screen and controls. Bluetooth connects it to each radio. One runs Meshtastic and the other MeshCore; their messages and networks stay completely separate.
CORE
Phone or touchscreen Core
The Android beta uses your phone for messages, maps and location. The separate Waveshare controller track provides a dedicated touchscreen and local browser companion.
RADIO PODS
Two separate radio modules
Each module handles one network: one runs Meshtastic and the other MeshCore. They can work at the same time, but they do not pass messages between each other. The modular design also leaves room to choose compatible radio hardware.
Keeping the radios in separate modules also makes it easier to place their antennas apart, reducing the chance that one radio interferes with or overloads the other. The user can choose compatible radio modules instead of being locked into one custom all-in-one board.
Dedicated controller · firmware track
Controller and local browser workflows
01 · COMMUNICATION
Two independent radio networks
Connect Meshtastic and MeshCore at the same time over separate Bluetooth links. Messages, channels, identities and radio settings remain on their own network; MeshCrossway does not bridge them.
02 · MAPS & GNSS
Street, night and cached maps
View local GNSS position, clock and node locations on street or topographic maps. Use local street night colors and cached microSD tiles offline; uncached areas need Wi-Fi.
03 · TRACKS & BROWSER
Record and keep your routes
Record tracks and POIs, organize saved routes in folders, review previews and download GPX from the local browser companion. The browser also provides messages and radio settings.
04 · NODE DISPLAY
Choose what the map shows
Set shape, size and color separately for each network. Use ID badges or individual markers, turn grouping on or off, and sort readable node lists by distance or last reception with manual refresh.
05 · AGE & RETENTION
See recent activity at a glance
Choose colors by last reception: green under 24 hours, yellow from 1 to 7 days, gray for older or unknown records. Set a local retention period from 0 to 365 days; favorites and conversations are protected. Zero disables expiry.
06 · DEVICE CONTROLS
Adapt the screen to the field
Use automatic 180-degree landscape rotation, a saved rotation lock and manual flip, plus brightness, screen timeout and Bluetooth/Wi-Fi controls. Console logs and memory snapshots support continued runtime testing.
The screenshots below are captures of the running v0.8.16 device and its local browser interface.
Operation screenshots · v0.8.16
Working on the device and over the local network
These captures show the touchscreen firmware and the browser companion connected to the same device. Remote access is available on the user's local network; it is not a cloud service.
Touchscreen device
Remote browser companion
Hardware status
Modular design; hardware qualification remains
SELECTED CORE
Waveshare ESP32-S3-Touch-LCD-3.5
The touchscreen Core is the active firmware development target. MAX-M10S GNSS and microSD support the local navigation workflow.
USER-SELECTABLE RADIO HARDWARE
Choose a compatible radio for each network
No XIAO model is required. Heltec V3 is the development-tested setup; chosen radios must support the correct native BLE interface and compatible firmware. Other combinations need validation.
MECHANICAL DESIGN
Prototype cases; modular packaging in progress
The repository contains 3D case files for the Waveshare Core and a 10,000 mAh battery case. Final fit, separate Pod enclosures and a dock still need mechanical validation. KiCad Rev A is an archived integrated variant.
Experimental development project. Broader radio, RF coexistence, battery, runtime and mechanical qualification is ongoing. MeshCrossway is not a certified emergency or safety device.