Exactly, you got it

Thanks! I feel the same there’s a lot of room for small, focused utility apps that do one thing well without ads, trackers, or dark patterns. That’s largely the motivation behind this project too. Competing on care, simplicity, and respect for users really feels like a worthwhile direction.

>Have you had any luck using vector maps?

I already done much research about it (the same as you've mentioned here) related to OSM vector maps. See:(https://github.com/CompassMB/MBCompass/releases/tag/v1.1.4), for Android, the available map rendering libs like Maplibre-Native are an excellent choice, but obviously, it is a high-level library that adds a huge binary to the APK itself, its usecase doesn't fit for MBCompass at least as of now. But thanks for your valuable suggestion :)

Yep, if it were close to the power line, it might cause accuracy loss, but you can obviously easily find the compass accuracy in the top app bar, and if it goes 'very low', the alert dialog automatically popsup to notify you to recalibrate it.

The reason I included that note is that, as an open-source developer, I’ve seen many projects that weren’t actively maintained get picked up by bad actors as they modify the code and publish it on Google Play with ads or IAPs. I wanted to discourage that.

Other than this notice, MBCompass is fully licensed under GPLv3 or later.

The sum of the note and the gpl doesn't behave as though the notice has any precedence over the gpl. It behaves as additional restrictions and a license that allows you to ignore the additional restrictions. I'm no lawyer but it seems like it isn't achieving what you want.

But you publish it on github? Anybody can simply ask copilot to make the same app as yours and be completely not bound by any license.

Maybe look into dual licensing. You could allow all free use but require a custom license fee for all commercial use.

>Maybe look into dual licensing.

No, no, not at all as a FOSS developer.

> I’m planning a non-intrusive in-app prompt to remind users about donations something subtle, because many users forget once they start using the app, rather than only seeing the donation info in the README.

As I mentioned previously, the above approach seems to be well enough and good.

Yep, I’m aware that many FOSS projects use in-app payments, but for MBCompass, I want to keep it free on every platform, regardless of the audience. Without funding or community contributions, it’s hard to maintain a FOSS project with meaningful features and improvements, rather than just vague “bug fixes/version bumps.”

As a FOSS advocate, I started this project as a community contribution to address the gap between user needs and available apps.

I can maintain it long-term without major contributions, but support really helps (especially maintaining in different apps stores). I’m planning a non-intrusive in-app prompt to remind users about donations something subtle, because many users forget once they start using the app, rather than only seeing the donation info in the README.

> but I wonder how accurate the compass is

MBCompass uses sensor fusion for accuracy, combining sensor data from the accelerometer, gyroscope, and magnetometer.

It is one of the most accurate compass apps. Don't trust my words, try it with different apps on Google Play and with some FOSS options like Compass by Philip Bobek: https://f-droid.org/en/packages/com.bobek.compass

And importantly, for true compass accuracy, I'd recommend you use the "true north" (magnetic declination) function, which requires location access. It takes some time to lock GNSS hold (the same goes for the current location button on the map view, default map location is Paris, France), but if you're moving, it locks pretty quickly and shows your current location with tracking (if you're moving.)

Thank you so much that really means a lot!

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.

TBH, that’s a great idea! It’s actually on my roadmap for MBCompass, something like waypoint tracking, where you can mark a location and get a directional arrow to it. Appreciate the suggestion!

Exactly! That’s exactly the philosophy behind MBCompass keeping the core functionality focused and lightweight, without unnecessary frameworks or bloat.

People are often surprised by how much you can do in under 2 MB.

There are also frameworks that don't bring in anything unless required. I use B4X for most of my apps.

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.