Post

Sem
@sems.dev

A while ago I shared some of my findings with #MapKit when developing #WaterMapper. Gather I shared them on Twitter, so I want to port them to here.

Sem
@sems.dev

I came to the conclusion that #SwiftUI’s MapKit is not yet ready. When building out my app with the Clustering of annotations the limitations became clear. I switched to #UIKit’s MKMapView using a UIViewRepresentable and clustering is working amazing.

Sem
@sems.dev

The next step is the optimization of the interoperability between #UIKit and #SwiftUI’s state.

0 reposts0 likes

Sem
@sems.dev

It still feels strange. First I build the Map using #SwiftUI’s #MapKit starting from iOS 16, then migrate to the new Map for iOS 17 users and up. This migration already opened up a lot of neat features and modifiers.

Sem
@sems.dev

But, if you need clustering, like I did, you’ll find out that you need to migrate (again). Even ‘back to’ #UIKit - it feels off.

Sem
@sems.dev

Conclusion of the story, know what you are working with, and know what went before you. #SwiftUI is great, but not the best always.