Chuck,
I'll pass along your comments.
About a year ago, we did increase the limits for uploading shapefiles. This is from the documentation.
Shapefiles—ArcGIS Online Help | ArcGIS
My understanding is that we've kind of reached the limit on the amount of data we can store inside a web map. Storing all of that data inside the map makes the map quite large. That 10 MB shapefile is stored as plain text (JSON) inside the web map and probably yields an even larger map than the original shapefile. That map has to be downloaded to run on the device. Maybe it could perform OK on a PC on a fast internal network, but, for example, downloading that to a mobile device would likely be slow.
You say that people download parts of your data. Is your data hosted in AGOL? Are there some common areas or parts of your data that many clients might be interested in using? One idea is to create view layers from a hosted feature layer. View layers can define a subset of features and attributes from the original layer. So, given your source data, you might make several view layers that are subsets that people frequently use.
Create hosted feature layer views—ArcGIS Online Help | ArcGIS
Set hosted feature layer view definition—ArcGIS Online Help | ArcGIS
Hope this helps,
Mike
Mike,
Thanks for passing this along. Several of us have read through the documentation you referenced and we have tried the recommendations, but having clients who want to load ad hoc data keeps us from implementing the recommendations. Being able to control the data inputs is how we operate in most cases, but we really need to support this use case. Not best practice, but a need in our world.
Thanks again
Chuck