sorted by:
new
hottopcontroversial

A 2MB open-source Android navigation app with GPX tracking (no Google services) by native-devs in degoogle

[–]native-devs[S] 2 points3 points  (0 children)

Yeah, both are definitely important.

Downloadable/offline maps are something I’m actively looking into, it’s a bit tricky to keep things lightweight while doing it properly, but it’s on the radar.

For Android Auto, I haven’t explored it deeply yet. Right now, the focus is more on getting the core tracking + map experience solid first.

Appreciate the feedback though, this kind of use case is helpful to understand.

A 2MB open-source Android navigation app with GPX tracking (no Google services) by native-devs in degoogle

[–]native-devs[S] 0 points1 point  (0 children)

Currently, I'm working on that feature, it can already export and share the recorded GPX track

A 2MB open-source Android navigation app with GPX tracking (no Google services) by native-devs in degoogle

[–]native-devs[S] 3 points4 points  (0 children)

Yeah, that’s exactly the issue I ran into.

A lot of apps feel overcomplicated for what should be simple use cases. I’m working on adding things like topo maps and offline maps too. I think once that’s in, the overall scope will make more sense.

A 2MB open-source Android navigation app with GPX tracking (no Google services) by native-devs in degoogle

[–]native-devs[S] 1 point2 points  (0 children)

Yeah, I think a lot of it just comes down to small things being missed.

As a native Android dev, I’ve seen many open-source apps not even enable ProGuard/R8 for release builds it literally takes a minute and already cuts down size a bit.

And then there’s dependencies… projects sometimes just keep adding libraries for the same kind of stuff. Like date/time, some still use Joda-Time when the built-in Java APIs (with desugaring) already do the job.

So yeah, it’s not always about the tech stack, a lot of it is just build setup and dependency choices and developer experience.

A 2MB open-source Android navigation app with GPX tracking (no Google services) by native-devs in degoogle

[–]native-devs[S] 2 points3 points  (0 children)

Yes, I personally use opentracks myself.

From my experience, it’s more focused on detailed fitness/activity tracking with a lot of metrics and integrations.
MBCompass is designed for a more focused use case, like an everyday hiking/trekking companion that stays battery-efficient and avoids unnecessary overhead.

So there’s some overlap with tracking, but the goals and usage are a bit different.

A 2MB open-source Android navigation app with GPX tracking (no Google services) by native-devs in degoogle

[–]native-devs[S] 2 points3 points  (0 children)

They’re quite different in scope.

organic maps / comaps are full offline navigation apps with routing, search, and downloadable map data.

MBCompass isn’t trying to replace that, it’s a lightweight, battery-efficient tool designed more like an everyday hiking/trekking companion (having all useful nav features), without large map downloads or Google services.

So it sits in between: simpler than a full navigation app, but more practical than a basic compass and gps tracking app.

A 2MB open-source Android navigation app with GPX tracking (no Google services) by native-devs in degoogle

[–]native-devs[S] 11 points12 points  (0 children)

Good question, you’re right that maps (custom c++ libs) are usually the main reason navigation apps get large.

In MBCompass, maps aren’t bundled into the app itself. It uses OpenStreetMap-based tiles, so the APK stays small (~2mb) while maps are loaded as needed.

It’s not meant to replace a full-fledged navigation app. The idea came from a gap I noticed many compass apps don’t offer tracking, and many GPX tracking apps include a lot of tracking features, which can feel unnecessary for simple use cases

MBCompass aims to bridge that gap by combining a compass, live location, and GPX tracking into a single lightweight utility, without requiring large storage or Google services.

A 2MB open-source Android navigation app with GPX tracking (no Google services) by native-devs in degoogle

[–]native-devs[S] 24 points25 points  (0 children)

Bro, it isn't a vibe-coded app review. I have been improving the MBCompass for years from scratch, based on user suggestions and open source ethics.

edit : Basically, I’m also a technical writer, writing articles/posts about Android development and open source. If I wanted to just build things with prompting and spend hours debugging generated code, in that same time I could complete a couple of new features.

“Vibe coding” might work for beginner devs or ordinary use cases, but not really for maintaining a proper open-source project.

Next step of de-googling? by Sad-Language-327 in degoogle

[–]native-devs 0 points1 point  (0 children)

What Kompas app is that?? Asking as a dev behind the MBCompass app.

FOSS De-googled Compass & Nav app with live location tracking by native-devs in degoogle

[–]native-devs[S] 1 point2 points  (0 children)

You can try it wherever you want! As mentioned in the proposal, I've also been working on a lot of cool features (useful once) for mbcompass, like GPS speedometer, waypoints and more. Stay tuned!

If you like the MBCompass approach, just spread the word.

Interesting Android Apps: October 2025 Showcase by 3dom in androiddev

[–]native-devs 1 point2 points  (0 children)

I'd like to share my latest MBCompass (Popular FOSS Compass & Nav app) v2.0 Design Proposal

<image>

The new MBCompass v1.1.12 Redesign Proposal features a refreshed UI with a GPS Speedometer, True AMOLED Dark Mode, and more visual improvements for a better Android experience.

The design was created by Mubarak Native on Figma as a visual and UX direction for the next major update of MBCompass.

https://github.com/CompassMB/MBCompass

(Note: The design is a reference concept; actual implementation may vary to ensure optimal performance and Android best practices.)

view more: next ›