In the old days, AppBase.getProperty was the only option and I remember reading somewhere that it was caching data in memory.
Reading confusing Garmin documentation on persistence, it looks like Storage API always persists data to the disk.
This doesn't sound like it will work well with frequently cached data (location or other info cached in background service).
It will likely be very slow.
Also according to the documentation, Properties should only be used for app-related data during build time.
Which means it is not suitable for caching data.
This seems like common pattern but it isn't clear what storage is best for caching things like location data.