that way, the user can still use the device and the content would still download. Our workaround this issue is to make our downloads happen on a background task on the device. If the app closes or the phone locks, the download is canceled, and those are big downloads. The problem this creates is that when users want to see a house for the first time, we render the device useless while downloading. since we are using the basic Addresables download method, this is happening asynchronously. Not every user is going to see every house, so we don’t want them, the users, downloading all of them, the houses. Right now, our implementation works by downloading the bundle we want to use before loading it, since we don’t want to download every house at the beginning. I'm working on an ArchViz mobile project where we are using the Addressable Assets System to download large bundles (500 mb each, roughly) from a AWS S3 bucket.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |