Thomas Altenburger

I need to update this PR. I intend to just remove ```DynamicallyAccessedMembers```. This attribute doesn't do what I think it does (and I mostly still don't know what it actually...

That's what I thought it was doing, but working on another project where we added the attribute showed that it does absolutely not that and would still trim those types.

The issue title seems misleading in regard to the description. Are we talking about suspending/resuming the app or about calling ```Game.Exit()```? Because if we're really talking about ```Game.Exit()```, we should...

```Game.Exit()``` is not meant to suspend the app and should be prohibited on Android and iOS because app lifecycle is managed by the system and we shouldn't be able to...

I can see if I can share the implementation of our internal save data manager. It doesn't fit the ```StorageContainer``` API but it can likely provide insights toward how to...

Do we want to keep the exact same API? I can see some limitations in the original API. For instance, it assumes immediate writing of data when pushing something to...

Feel free to! I think we should get the API planned ahead and the rest can be done later (we just need to avoid the public API to move if...

```IDisposable``` and flushing on dispose would work in most cases, although it might be a weird that ```Dispose``` may trigger an async operation. Also, we might want to keep a...

What I have in mind and did internally, is that when you create the manager, save data are opened->read/cached->closed and then you access the cached data to avoid having too...

> I can see if I can share the implementation of our internal save data manager. It doesn't fit the `StorageContainer` API but it can likely provide insights toward how...