I spent about a week, writing this[0].
It’s a special UIKit map package, designed to be integrated into SwiftUI, as map support is a big SwiftUI Achilles heel.
I have integrated it into another package (a SwiftUI admin tool, that isn’t public), and it works exactly as I planned.
I often do this kind of thing. If I can break some module out of my work, and publish it, I spend the extra time, polishing and documenting it. No one else really cares, but it forces me to do a really good job, so I get an extremely high-Quality component, that I don’t have to worry about, later.
Interesting! I've recently plumped for UIKit (with bits of SwiftUI dropped in) for a new mapping app because, as you say, SwiftUI map support is virtually non-existent. Have you thought about adding Maplibre support as an alternative to MapKit?
I try to use MapKit, when possible, as it is unencumbered by licensing and support issues (and works pretty well), but I have considered MapBox. It’s commercial, but pretty straightforward, with licensing and support. I have heard good things about it.
I don’t really know about Maplibre (but I’ll check it out).
Had a friend create an app, based on Google Maps (if you remember, in Ye Days of Yore, GM was the mapping engine for iOS), but Google did the licensing rug-pull thing, and he had to do an emergency open-heart surgery to his app.
That was a sobering lesson about relying on third-party dependencies.
[EDIT] Looking at your app, I’ll not be surprised, if you’re familiar with my friend’s app: EasyRoute