@Bouke-Ent said:

it would be strange that a developer would use 2 differant SDK's

If you read again, you'll notice that that is not what I said

i do not believe it is a design choice. i believe it is a good developer choice.

Of course, it's the developer that decides what to design. So I see no difference.

@Con-Hennekens said:

@Bouke-Ent, definitely not It is a design choice. Given the available SDK's for OSM, you would need to maintain 2 separate code bases for iOS and Android. (like was done with Navigation "Previous" )

@Franxu said:

HERE maps are very outdated.

I know that it can take some time to get changes in, but it largely depends on local governments and general people taking the effort to submit them. If no one does, it wil take time...

https://mapcreator.here.com/

i do not believe it is a design choice. i believe it is a good developer choice. as i said sdk is from here and that is a developerstool. that tool will not support OSM maps when company Here has it own maps. it would be strange that a developer would use 2 differant SDK's.

@Franxu said:

HERE maps are very outdated.

I know that it can take some time to get changes in, but it largely depends on local governments and general people taking the effort to submit them. If no one does, it wil take time...

https://mapcreator.here.com/

@Franxu said:

Would it be possible to offer the option of using OpenStreetMap for navigation instead of HERE, at least as an alternative?

No, I understood that it has to do with the fact that OSM apparently cannot work properly with the Flutter platform on which the app is based.