That is true but still MMKV due to its simplicity and small size is a very fast option over AsynStorage on both android and iOS. It has been used in the WeChat app used in China for datastorage.
I think you are right. I was focusing on basic implementation. Now I will make the performance optimizations needed. For example using a single instance of created class for all get set methods and not create them on every call. Thanks for pointing it out.
The second thing about numbers is that its just in case you needed it for something, it is there but there are other ways to set the data too.
Basically I forked this code from another repo and worked over it so the initial work is theirs. I will look into optimizing this as soon as possible. What do you think? Should callbacks be used instead of Promise?
MMKV is a simple key-value store but the good thing is that it is fast, A custom indexer can be made for querying. However there is a method to get all the keys in the storage but its not exposed in react native side. Is that what you mean?
Is it possible to use it at the native layer (objective-c / java )? My use case is for storing/reading info before react-native JS is bootstrapped. I've tried using AsyncStorage for that but the bindings for objective-c isn't straightforward at all!