MeshCore roadmap and future
Upcoming features, development priorities, and long-term vision of MeshCore
Where is MeshCore heading?
MeshCore is continuously evolving with an active community of developers building new features, fixing bugs, and improving the protocol. This roadmap provides an overview of what is in development, what is planned, and where we want to go in the long term.
The roadmap is not set in stone. Priorities can shift based on community feedback, technical constraints, and real-world usage patterns. We remain flexible and pragmatic in our development approach.
Everyone can contribute to the roadmap by submitting feature requests, discussing priorities, and of course contributing code via GitHub pull requests.
Current development (active)
These features are actively being developed and will arrive in upcoming releases
Multi-Channel mesh routing
Support for multiple channels that intelligently cooperate to increase network capacity without interference.
Impact: More nodes can communicate simultaneously without channel congestion
Improved mobile App
Complete redesign of iOS/Android apps with enhanced UX, offline maps, message threading, and push notifications.
Impact: Considerably more user-friendly for everyday use
Adaptive power management
Intelligent power management that automatically adjusts TX power and sleep modes based on battery level and network conditions.
Impact: 2-3 times longer battery life without manual configuration
End-to-End encryption upgrade
Upgrade to modern cryptography (Curve25519) with forward secrecy and post-quantum resistant options.
Impact: Enhanced security and privacy for sensitive communication
Planned features (upcoming releases)
These features are planned for the next 6-12 months
Satellite connectivity integration
Connection with satellite modems (Iridium, Starlink) for long-distance backup connectivity.
Why: Mesh networks can achieve global coverage for emergency communication
Voice messaging support
Send compressed voice messages (Codec2, Opus) via mesh for situations where typing is impractical.
Why: In crisis situations voice is often faster and clearer than text
Mesh topology auto-optimisation
AI/ML algorithms that automatically optimise routing, repeater placement, and channel allocation.
Why: Reduce manual configuration burden, especially in large networks
Emergency beacon mode
Dedicated emergency mode that broadcasts an encoded distress Signal with GPS location at the press of a button.
Why: Life-saving feature for outdoors, disasters, and other crisis scenarios
Blockchain-Based identity
Optional decentralised identity system for verified nodes and secure reputation scores.
Why: Spam prevention and trust in large public mesh networks
Research phase (experimental)
These topics are being explored but are not in active development yet
Dynamic spectrum access
Automatically switch between frequency bands based on regulations and interference
Quantum-Resistant cryptography
Post-quantum encryption algorithms for long-term message security
LoRa mesh for iot
Lightweight protocol variant for sensor networks and IoT devices
Mesh-to-Internet gateway
Secure bridges between mesh networks and the regular internet
Predictive routing
ML models that learn node movement patterns for improved routing
Solar harvesting optimisation
Smart algorithms for maximum efficiency from small solar panels
Development priorities
-
1
Stability and reliability
Core functionality must be rock-solid: no crashes, data loss, or connectivity issues
-
2
User experience
Software must be intuitive for non-technical users without consulting the manual
-
3
Security and privacy
Encryption, authentication, and privacy protection are not optional but core features
-
4
Battery efficiency
Days to weeks of operation on battery is essential for practical emergency use
-
5
Community feedback
Real-world usage and user feedback determines where we allocate resources
Help build the future
MeshCore development is community-driven. Your input and contributions make a difference
Submit feature requests
See something missing? Open a GitHub issue with your idea and use case
Vote on features
Give a thumbs-up on issues you find important. This helps with prioritisation
Join discussions
Join Telegram and GitHub Discussions to talk about the roadmap
Beta testing
Test new features early and provide feedback to developers
Frequently asked questions
When will feature x be available?
Timelines are estimates. Real-world development can take longer due to technical challenges or resource constraints. Check the GitHub milestones for current status.
Can I sponsor or pay for feature development?
Yes! Some organisations sponsor specific features. Contact us via Telegram to discuss whether this is possible for your feature request.
Why does feature development take so long?
MeshCore development happens mostly by volunteers in their spare time. Embedded development on resource-constrained hardware is also complex and time-consuming. We appreciate your patience!
How do you determine what receives priority?
We consider: number of users requesting the feature, impact on core use cases (emergency), technical feasibility, maintainability, and available developer time.
Can feature x from other mesh software be ported?
Possibly! MeshCore is open to good ideas from other projects like Meshtastic. If the feature fits our vision and is technically feasible, we can collaborate or share code.
Build MeshCore with us
The future of MeshCore is determined by the community. Your ideas and contributions make a difference
Join the development community and help shape the roadmap!