"Best" way to build my addressable system?

Hello. My issue is wondering how my addressables need to be set up, I have multiple scenes each with vastly different game objects inside of them. Some of the scenes are similar in some regard. What would be the best way to go about setting up my system. Also we are building the addressables remotely.

Do I need scene asset references only to be addressable?
Do I need to make all objects that will appear in the build to be addressable?

Is there an easy way to streamline this? I’ve looked at multiple videos, but my question regarding “The proper way” hasn’t necessarily been addressed.

I think the reason you don’t see a ‘dominant strategy’ when it comes to Addressables is because it really does depend on what content you want to make remote/updatable and if/when/how it gets updated. For example, it’s possible to simply asynchronously request Addressable assets without any warning and they’ll be downloaded if needed and given to you, which is super ad-hoc from a UX point of view. Or maybe you want to be really verbose about one big update right at the start of the app and then let users have a seamless experience from then on.

If you can give me a brief break-down of what you want to accomplish (not worrying about the ‘how’ of Addressables) I can drum up an approach for you. Are they meant to download levels, skins, etc?