For them, donations are a simple way to support the project, and they’re definitely appreciated.
Not true anymore! \o/ I don't use Android anymore, but I agree a lot with the principles you've shared here, so it's a thank you for sharing that. And I know how difficult it is to get the first donations, and after you get the first, it's much easier to get the later ones. So best of luck, and I hope you'll remain steadfast with your principles when it'll matter! :)
- Waypoint tracking (with GPX import/export support)
- GPS speedometer
- Offline maps with offline POI search using GeoPackage (an OGC-compliant standard supporting spatial queries)
I’d love to hear your thoughts or suggestions your feedback is really appreciated!
Beyond donating, the best way to support MBCompass is simply spreading the word. That helps more people discover it, contribute to it, and make it better for everyone.
If you want to receive compensation for the work you put into making the app, then you need to start treating it as work and call it a payment and not donation.
Adding a magnetic compensation map sounds like a great fit for improving global accuracy without changing the app’s core goals. Thanks for the suggestion.
https://www.ncei.noaa.gov/products/earth-magnetic-model-anom...
Is a good starting point.
Let me indicate a location and point an arrow at it!
Are you calculating the route or just pointing the user in the general direction?
I’m actively working on features like waypoint tracking, offline maps, and a GPS speedometer. The goal is to keep MBCompass a useful navigation utility, not a full routing app.
Routing isn’t planned at the moment (maybe with plugins later), since adding it would shift the app away from its core purpose and increase complexity. The main priority is to remain fully functional offline-friendly and extremely lightweight (currently under 1.5 MB).
By offline-friendly you're referring to the compass part only, right?
Otherwise users would have to download the map in advance which would take more that 2MB. Am I reading this right?
For maps, it’s a bit different users initially see an online basemap (requires internet). Instead of forcing them to download an entire map upfront like some libraries (e.g., MapsForge), they can crop or select specific areas to download.
This makes it convenient to get only the map they need. Of course, if they prefer online maps, the app will cache tiles automatically. In remote areas, offline maps can be used as planned.
People are always amazed when i show them my apps are 2-5 megs, and that's because there's 2-5 megs of assets.
People are often surprised by how much you can do in under 2 MB.
It has a fundamental issue, which is being single threaded (with exceptions), but it's truly lightweight and easy to extend, and the team behind it really know their business.