Can deployment be even more granular

It would be amazing if targeted deployment could be even more granular or requested on-demand. For instance, being able to download an ML model tailored to a certain location being visited would be very powerful.

Any chance of that being in the pipe-line or better yet, is there a way to do that already?

Accepted Reply

As @kerfuffle mentioned, that link does require some additional management, but it is still a perfectly valid way to retrieve models remotely.

For Core ML Model Deployment, we do not natively support targeting based on location. We provide targeting based on the language and region code of the device, but this is user configured and may not reflect their actual location.

Note that we do support requesting "on-demand". The initial request for a model collection using MLModelCollection.beginAccessing will go and fetch the specified collection, with the handler called upon completion. One option for your use case would be to define multiple collections for certain locations. Then you can request the device's location in your app at runtime (after being granted permission), and begin accessing the collection best suited for the result.

Replies

The difference here is that you need to host the model yourself on a server somewhere. It's not automagically handled for you like the new deployment stuff is.
As @kerfuffle mentioned, that link does require some additional management, but it is still a perfectly valid way to retrieve models remotely.

For Core ML Model Deployment, we do not natively support targeting based on location. We provide targeting based on the language and region code of the device, but this is user configured and may not reflect their actual location.

Note that we do support requesting "on-demand". The initial request for a model collection using MLModelCollection.beginAccessing will go and fetch the specified collection, with the handler called upon completion. One option for your use case would be to define multiple collections for certain locations. Then you can request the device's location in your app at runtime (after being granted permission), and begin accessing the collection best suited for the result.
Excellent. Collections do look promising.

Thank you.