Depending what is the extent that the user wants to download. If that is 'whole world' type of scenario then it will be hitting the limit. Where you are using MapViews extent, you can use custom polygon too.
There are several approaches to this problem but I would start from the use case to see if it's really needed to get so large area to offline use. With large areas we hit challenges with very large tpk packages, device storage requirements etc. In future you can easily take large areas offline using vector basemaps but that's taking vectors offline is not supported at the moment.
Some ideas / approaches to think and try
- Restrict application to specific scale / extent so user uses application only on the area that is relevant (ofc if you need to work all over the world this wont work that well)
- Use estimate tile cache size to determine if you need to split the request to multiple tpks / parts. For example split area into 4 segments and try to download those (this will need more than one layer to show the basemap and mechanism to handle multiple downloads / construction of layers dynamically based on the tpks available)
- Pre-create tile caches to save the time to generate tiles on requests basis. You could store these for example in ArcGIS Online organization and then you could just analyse which packages are in the are that user wants and download only those to the client. (Needs more infrastructure and work upfront)
- Use multiple tpks with different scale ranges to keep individual packages smaller. You can also use different areas for each of them.
- If your application is based around specific locations / tasks to do in specific areas, you can generate tile packages around then that could be downloaded when the task is `accepted` in a client.
There are probably more options but these came into my mind right from the bat. Hope one the approaches could work for you.
