I think the idea of bounding box + zoom range, start/pause/cancel, and progress callbacks are the general model we want. We don't necessarily want to mirror the APIs to Java for any sort of undue parity, but these are some ideas. Storage format is again SQLite but offline maps are treated as atomic, immutable documents. Here we had a combination of a clean slate for how to do this along with integration with an existing Apple API. offlineMapDownloader:didCompleteOfflineMapDatabase:withError: offlineMapDownloader:didEncounterRecoverableError: offlineMapDownloader:totalFilesWritten:totalFilesExpectedToWrite: offlineMapDownloader:totalFilesExpectedToWrite: It can be a good strategy, depending on usage, and becomes much more viable with vector tiles than raster.Need a tool that builds an offline database that can be distributed with the app/downloadedĬould also download all individual tiles on first launch, however this is not good strategy Need to add ability to swap out the cache database set it to a read-only mode It's not designed for adding to later, but could be remedied in some way if this seems like a good idea. This is used for prebunding offline maps with an app. MBTiles is a spec for raster or vector tiles as blobs in SQLite with a known format and metadata table.We've accomplished a lot of this in past across various toolsets on both iOS and Android. Removing label & editing title - this isn't specific to Android.

Offline maps android not downloading