Roadmap & future

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's in development, what's 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. 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 soon in releases

In progress Q1 2025

Multi-channel mesh routing

Support for multiple channels that intelligently work together to increase network capacity without interference.

Impact: More nodes can communicate simultaneously without channel overload

In progress Q1 2025

Improved mobile app

Complete redesign of iOS/Android apps with better UX, offline maps, message threading and push notifications.

Impact: Much more user-friendly for everyday use

In progress Q2 2025

Adaptive power management

Intelligent power management that automatically adjusts TX power and sleep modes based on battery level and network conditions.

Impact: 2-3x longer battery life without manual configuration

In progress Q2 2025

End-to-end encryption upgrade

Upgrade to modern crypto (Curve25519) with forward secrecy and post-quantum resistant options.

Impact: Better security and privacy for sensitive communication

Planned features (upcoming releases)

These features are planned for the next 6-12 months

Planned Q3 2025

Satellite connectivity integration

Connection with satellite modems (Iridium, Starlink) for long-distance backup connectivity.

Why: Mesh networks can get global coverage for emergency communication

Planned Q3 2025

Voice messaging support

Send compressed voice messages (Codec2, Opus) via mesh for situations where typing isn't possible.

Why: In crisis situations voice is often faster and clearer than text

Planned Q4 2025

Mesh topology auto-optimization

AI/ML algorithms that automatically optimize routing, repeater placement and channel allocation.

Why: Reduce manual configuration burden, especially in large networks

Planned Q4 2025

Emergency beacon mode

Dedicated emergency mode that broadcasts an encoded distress signal with GPS location at the push of a button.

Why: Life-saving feature for outdoors, disasters and other crisis scenarios

Planned Q1 2026

Blockchain-based identity

Optional decentralized 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 aren't in active development yet

Research

Dynamic spectrum access

Automatically switch between frequency bands based on regulations and interference

Research

Quantum-resistant crypto

Post-quantum encryption algorithms for long-term message security

Research

LoRa mesh for IoT

Lightweight protocol variant for sensor networks and IoT devices

Research

Mesh-to-internet gateway

Secure bridges between mesh networks and regular internet

Research

Predictive routing

ML models that learn node movement patterns for better routing

Research

Solar harvesting optimization

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 reading the manual

  • 3

    Security and privacy

    Encryption, authentication and privacy protection are not optional but core features

  • 4

    Battery efficiency

    Days to weeks of runtime on battery is essential for practical emergency use

  • 5

    Community feedback

    Real-world usage and user feedback determines where we spend 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 ๐Ÿ‘ on issues you find important - this helps with prioritization

๐Ÿ’ฌ

Join discussions

Join Telegram and GitHub Discussions to talk about the roadmap

โš™๏ธ

Beta testing

Test new features early and give 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 / pay for feature development?

Yes! Some organizations sponsor specific features. Contact us via Telegram to discuss if 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 gets priority?

We look at: 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!