[eisa01]

People asking if there's differences to Organic Maps, yes there are

E.g., on iOS CoMaps has fixed several bugs present in OM like: * CarPlay Interface not resetting upon arrival at destination * Search Results still highlighted after route creation * Button overlaying during routing on small iPhone

I have improved the consistency of paths and footway rendering

[pastk]

Talking about the app features, here are some of the bigger / easier to notice differences:

- added automatic backups for bookmarks and tracks

- added 100m-step altitude isolines to all regions that had worse or no isolines

- a big rework of the map colors - lighter, warmer, friendlier

- add a setting to customize the leftmost button or hide it

- removed semi-transparent background in Subway layer

And there is a bunch of smaller changes, for details check the release notes: https://codeberg.org/comaps/comaps/releases

[worldsavior]

Why all of these features weren't contributed to Organic Maps instead of creating a fork?

[gedankenstuecke]

You can read the reasons for the fork here: https://www.comaps.app/news/2025-04-16/1/

[zikduruqe]

https://news.itsfoss.com/organic-maps-fork-comaps/

[eisa01]

Me personally, the CoMaps people seem more open to other contributors

[justaj]

Oh man, if automatic dark mode (dependent on whether dark theme is engaged on phone) is added, I would switch immediately.

[orblivion]

The features here (and listed below) are good features, but I wonder if this isn't just "different features". In the same time, has Organic Maps added different features that you don't have? Or have they made fewer features because developer energy has shifted to CoMaps?

I.e. is it that Organic Maps just have different priorities than you do? Or is it that Organic Maps have been holding back these good features for no good reason?

[pastk]

CoMaps cherry-picks changes from Organic Maps regularly. OM is also free to pick from CoMaps, but so far they haven't been doing so.

And yes, amount of work done on OM has reduced significantly, as many contribturos have moved to CoMaps.

Still, features-wise priorities of both projects are quite similar. E.g. being easy to use and simple , offline-focused, etc.

I would say CoMaps is a bit more serious about privacy and is also more open to customization by users (to a reasonable extent).

As CoMaps is a community-driven project then it's possible that with time the growing community would change the direction of the project somewhat.

But the biggest differences that actually were the reason for forking - are in the way the project is run - CoMaps is truly community-driven, open and transparent, which includes project's finances and decision-making.