What best practices do you recomend around caching and playing off-line? I don't mean anything as advanced as spending virtual currency while off-line. I am thinking of a simple PlayFab integration where I am mostly using PlayFab to just:
- Give me some basic KPIs and like DAU, MAU and retention
- Use Title Data as a way to adjust tuning and balancing issues in the game
- Use the Title News to send messages to my players about new updates and new games.
- Track some player stats to have global and social leaderboards
I don't have IAP or VCs or catalogs. I want my game to work while offline. I understand you are considering offline support on your roadmap but I want to understand what I can do today.
For #1 it would would be okay to not include off-line play in the KPIs. That is not ideal but it can work.
For #2 I need to know the values of the title data even when offline. I guess I need to build my own system for caching the last known values that were downloaded and having defaults if none were ever download. Do you have example code that makes this easier? I am writing in c# for unity. Or do you have pointers about best practices for doing caching like this?
#3 is simple. Just don't show news if off-line
#4 obviously I would not display a leaderboard when off-line. But I would want progress made while offline to be stored in stats. I guess this is where things get murky and dangerous.
All of the above may even be too specific. I would love to just hear about how games like AdVenture Capitalist use PlayFab and work off-line. Assuming I am making a game that will allow off-line play, which PlayFab features are reasonable for me to try to use and what best practices should I follow to use them?