To the Addressable Developers: unitywebrequest,assetbundles and concerns on the future

Asking directly to the addressable developers:

Long story short,i have a huge project going on: tiny mobile frontend, gigantic backend that manages users and which assets they can have access to.
Users can have access to a huge quantity of contents. This contents (images,videos,3D models etc) must be produced ON EXTERNAL Unity projects.We then just create the assetbundles,upload them on the server and generate a download link that we use with unitywebrequests on the client frontend and so on.

Few core developers do the mobile frontend,many remote "outsourced" game designers do the assets (OUTSIDE THE MAIN PROJECT,too much stuff to be imported into the main project and then build one big fat catalog).

Since the addressable system is the future,but our project demands the "old way" to do things, we are worried about whats going to happen.

THE QUESTION:
Today i can still implement an "old way-unitywebrequestblahblahblah" system, but i'm worried about that not being supported in future versions of Unity,in favour of a only-addressable style to do things.
Will old Assetbundle APIs be deprecated or made unaccessible under some .dll?
Can i sleep in peace or i have to worry and find an alternative solution/workaround inside of the addressable system to do the trick?
And if so, any idea, or suggestion on where to look/ what to study to solve this problem?(maybe there is something in the addressable docs but i couldnt find it).
Thanks in advance!

 

With the ability to load additional catalogs, nothing stops you using separate projects to produce asset bundles if those bundles are mostly pure assets. Will this solve your issue?

https://forum.unity.com/threads/res...bles-exported-from-a-separate-project.642793/

 

We already implemented that for our live project and it works like a charm
We have 2 projects that will load dynamically a catalog and all assets generated with a thrid project and upload on an amazon server

 

@unity_bill I guess he means with "the old way" to just point a web request to an arbitrary HTTP URL to download a bundle. I am asking myself the same thing. As far as I understand the Addressables system, it requires that all addressables are known at build time. In our case, they are not. We want to deploy them to the server and let the client know which ones to download.

 

I'm looking for the same solution. I want to load a asset bundle from a HTTP URL. The bundle
has a house asset with baked lighting, loading the asset with the light map dependencies works well with Addressables but only if the path is added to the profile at build time.

I've tried using Addressables.ResourceManager.InternalIdTransformFunc to change the URL at runtime but I'm not sure if I'm doing something wrong here because it can not seem to find the assets with the given key word in the bundle.