Nice. Without trying it, just by looking at screenshots, I wonder how your navigation works.

Are you calculating the route or just pointing the user in the general direction?

Currently, the app shows the user’s live location with real-time tracking on an OpenStreetMap-based map. It does not calculate routes or provide turn-by-turn navigation instead, it focuses on orientation and situational awareness.

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).

▲

mastermedo 3 hours ago | parent [-]

> 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?

	▲	nativeforks 3 hours ago \| parent [-]
		Good question! “Offline-friendly” mainly refers to the core compass and sensor features, which work fully offline. 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.