Release 2026.05.06 is out on Codeberg, F-Droid, iOS, and soon on Google Play and brings a big new feature:

[clemensg@digitalcourage.social]

@Stem

In the linked articel I understood, that they try weekly.

@CoMaps

[doc75@pouet.chapril.org]

@CoMaps this a great move. Do not necessarily release map more often as it will waste a lot of bandwidth. Current pace seems a good compromise to me.

[comaps@floss.social]

@clemensg @Stem yes, that's our targeted frequency!

[comaps@floss.social]

@doc75 you won't have to update that often, you can keep the older maps.

But, we know that many of our users also use CoMaps for actively contributing to OpenStreetMap - and for them having fresher local maps helps making better contributions!

[robtherunt@cupoftea.social]

@CoMaps
iOS user here and I thought maps update separately already?

[iyanne@sk.girlthi.ng]

@CoMaps@floss.social @doc75@pouet.chapril.org Exactly! extremely good move IMO.

[jonassmith@theforkiverse.com]

@CoMaps You guys are awesome. Not a real problem for me, but would there be some way of incrementally updating maps instead of downloading everything for each update?

[comaps@floss.social]

@jonassmith if you mean on a map-by-map base (e.g. only update the map for region X) you already can do that!

If you mean just getting a "diff" of the changes, that's quite a bit more complex to implement and nothing to expect soon I think!

[jonassmith@theforkiverse.com]

@CoMaps Oh yes I meant diff Ok, just wondering

[comaps@floss.social]

@robtherunt yes and no: Until now you would first download a new app version, and then inside the app update the maps. But so far, you never would get newer maps without first updating the app (maybe you didn't notice because of having auto-app-updates enabled?)

From now on, you don't have to update the app version first, in regular intervals there'll be new maps available in-app!

[comaps@floss.social]

@jonassmith I know that it's something that's being talked about, but not in a concrete way.

Personally, I think it would potentially also shift a lot of computational burden onto end-user devices for the merging, which could be problematic for older devices. So it's a bit of a trade-off to consider!

[michammel@mastodon.social]

@CoMaps can we get cycle routes as they are marked in OSM?

BTW. Awesome app. Keep it up!

[jalict@mastodon.gamedev.place]

@CoMaps Wonderful - thank you!

[rapha3l@not-x.g2od.ch]

@CoMaps @bsm

Cool!

[robtherunt@cupoftea.social]

@CoMaps
Thanks for clarifying. And I suspect you’re right about me having auto-update of the app on.

[comaps@floss.social]

@michammel there's on-going work to do this for hiking routes: https://codeberg.org/comaps/comaps/pulls/4111

Hopefully when that is done, it can be extended for cycling routes too!

[comaps@floss.social]

@robtherunt no problem! In practice you should still get maps more often, as we don't have to build a new app version and get it reviewed & approved by Apple!

[voorstad@mastodon.nl]

@CoMaps

Any news on the live traffic feature?

[soaproot@sfba.social]

@CoMaps There's probably some way the display and download functionality could better handle both of those kinds of users, but I don't have a proposal in mind and I don't think the current situation (in which maps show out of date soon after being downloaded) is an especially big problem. @doc75

[comaps@floss.social]

@soaproot @doc75 also for now it won't show that there's new maps available unless you manually check for them.

That's by design, as we promised we wouldn't do any internet connections without user consent - at some point in the future there'll likely be a opt-in for automatically checking for new maps in the background but for now it's all manual.