The Mapbox framework is 38MB - more than twice as large as our next largest framework - HockeySDK at 17MB. Most frameworks are in the 1MB range.

I'd say the added download size and launch time (see https://phabricator.wikimedia.org/T149608) disqualify Mapbox.

Unfortunately it looks like the WMF tile service can't be used with Apple's MapKit - the tiles could only be added as a layer on top of the built-in map.

The Mapbox framework is 38MB - more than twice as large as our next largest framework - HockeySDK at 17MB.

The size of the Mapbox iOS SDK package you download doesn’t necessarily reflect the size added to the App Store download or the additional space taken up when installed on disk. (For one thing, simulator content automatically gets stripped out at submission time.) From what my colleagues at Mapbox have seen, the stripped dynamic framework ultimately adds about 5–6 MB to the application size.

If the stripped dynamic framework remains too large, another option is to use the static library flavor of the SDK (available for download on GitHub). The size ultimately added to the application will depend on the extent to which you use features like runtime styling and offline maps.

(Full disclosure: I work on the Mapbox iOS SDK by day.)

@mxn I realize that the download size and install size don't correlate 1:1. I used the relative download sizes to indicate that it'd be our largest framework by roughly a factor of two. The way I phrased my previous comment doesn't make this clear, so thank you for clarifying and for pointing out the static library options.