Simple Addressables Implementation for HTTP server based game data loading.

We are currently loading bulk of our game data configurations ( read remote configurations ) and content from a simple backend server. data itself is primarily JSON that is parsed into scriptable objects and PNGs that are used to initialize Assets like Spirtes and Tiles. These assets are further directly plugged into parsed SO which are then fed to managers in scene to generate concrete runtime instances.

Simply put we first authored a pure SO based content management for our game then moved the data itself for SO on our backend for online configuration.

Currently we have hit a block where trying to implement a simple caching mechanism has been cumbersome due to poor performance of EncodeToPNG calls for bulks of PNGs on mobile devices. additionally incremental caching , cache syncing etc are layers we cannot tackle in much depth due to limited time and resources.

I was wondering if Addressables can be used to replace the Tiles/Sprites in JSON parsed ScriptableObjects so that our PNGs can be loaded and also handled for caching with minimal ground work.

Edit : Just to clarify i am only looking to offset the Images portion of our content management pipeline to addressable.

 

Load images via the system should be trivial.

For configuration file, however each time change it requires rebuild the whole contents, probably not that convenience.