Storage file format upgrades about ark-navigator HOT 1 CLOSED

The storage format will be modified with time adding new features or due to other reasons. The library is supposed to be used by several apps on different devices and potentially on different platforms (Android, iOS, Linux, macOS, Windows). These apps can work with the same data synchronized between devices. This way, apps can use different versions of the library although version of tags storage can be the same on devices hosting these apps.

That's why:

1. The library must be able to handle loading of older versions of the storage and upgrading them.
   Migrations mechanism can be implemented to allow this. Every critical source modification should add new migration.
   Storage upgrade must be confirmed by user and must involve saving original storage as backup.

2. The library must be able to handle loading of newer versions of the storage and ignoring newer features.
   We can separate features in the storage from each other, loading only supported ones.

It really seems to be over-complication for now. The storage structure is really simple at the moment. When the format will need to change we must implement migration. For now only newer features are planned, which can be implemented as separate entity with separate storage.

from ark-navigator.