What difficulties arose when integrating MapKit into a project using Clean Swift architecture?

When integrating MapKit into a project with Clean Swift architecture, the following difficulties often arise:

• Responsibility separation: MapKit requires working with UI components (e.g., MKMapView), but in Clean Swift, the ViewController should be as "thin" as possible and not contain business logic.
• Data transfer: Data must be carefully passed between Interactor, Presenter, and ViewController to update the map and respond to user actions.
• Delegate handling: MKMapView uses delegates for event handling (e.g., annotation taps), which can complicate architecture since delegates are usually implemented in ViewController, but logic should reside in Interactor.

A solution example is to create a separate layer or service for working with MapKit, encapsulating map logic, while the ViewController only displays results and forwards events to the Interactor.