Roadmap
Keep the field experience dependable.
Android 0.1.0 is the public beta functional baseline. Smaller Android changes use 0.1.1, 0.1.2 and so on; substantial changes use 0.2.0. Version 1.0.0 is reserved for production readiness and has not been released. The controller keeps v0.9.32 as its independent accepted firmware baseline. Dual Bluetooth radios, GNSS/maps, messaging, tracks, local browser tools, orientation controls and configurable node retention are delivered. The next work focuses on evidence, efficiency and hardware qualification.
Android beta acceptance. Expand phone/radio/firmware testing, verify dual BLE reconnection, messages, offline maps, tracks and backup/recovery. Use feedback to stabilize the core scope before 1.0.0. Try the beta.
Runtime and recovery. Continue long sessions with both radios, reconnects, hotspot changes, map pans, SD errors and node expiry. Record reproducible logs and memory/touch measurements in issue #137.
Memory efficiency. Evaluate smaller bounded working sets and compact storage separately from expiry. Current fixed-size arrays stay allocated when entries are removed; measure any real savings before changing capacity.
Compatibility and power. Expand radio/firmware coverage and verify battery monitoring, charging, autonomy, GNSS and microSD behavior.
Final modular hardware. Complete independently powered Pod packaging, enclosure fit, antenna separation, RF coexistence and environmental checks. The integrated Rev A PCB remains archived.
Future software. Live position sharing and optional MeshMapper, ATAK/CoT or Reticulum integrations remain proposals. Keep both native networks independent.