Package Name? about react-native-mmkv-storage HOT 12 CLOSED

haha no worries i was refering to the backend package name.
Only really an issue if this package along with the old package are used at the same time.
But i figured you'd probably want to change the name as this is now your project.
Just seemed odd really :)

from react-native-mmkv-storage.

Hmm that makes sense now, I will change the names in the next release so that such a problem does not appear for someone. Good point 🌟

from react-native-mmkv-storage.

An all inclusive setup would probably be a lot better but also means more maintenance.
Taking a few sections and implementing would be a nice solution.

Realm Database handles encryptions and they expect the developer to store the key themselves.
Making it that way is generally considered the norm and if you do that then you could just suggest what other modules people can use to store the encryption key if they care about security.

from react-native-mmkv-storage.

The package name is react-native-mmkv-storage.... On npm. Its not react-native-fast-storage. I have changed it. On the backend, similar naming is used but it does not matter i think. ..

And yes It will be a secure solution once encryption is added i think. MMKV is used by wechat app.. So its reliable and well mantained also.

from react-native-mmkv-storage.

Can you explain on the package name? I still dont understand where it appeard to be same?

from react-native-mmkv-storage.

The big question about encryption is whether to handle all the encryption from key creation to its storage etc in the library or give the users of this library a simple api to encrypt storage using a password, storage of which, "securely" would be their problem to solve. Like using something such as "react-native-keychain".

from react-native-mmkv-storage.

A lot of people might appreciate an all inclusive package that does everything.
But you could essentially do both, maybe allow the ability to store your own keys elsewhere and just feed that into your functions on demand.
So then if you don't hand over keys it would just generate, store and use its own maybe?

from react-native-mmkv-storage.

And what if we used react-native-keychain as a dependancy to this library and handle everything ourselves in the library? That would do the job.

Actually implementing the logic wont be a problem but mantaining it and addressing the bugs etc would be and since react-native-keychain is well mantained maybe it could be used or a part of code from it implemented here.

Because encryption will be a very crucial part of the library hence a robust and stable solution that does not break at some point is required.

Hence i think more detailed survey is needed to see the available options and what might fully fulfill the purpose...

from react-native-mmkv-storage.

It would be possible to go that route yes.
The only issue is that library expects a username and password.
Where as this one allows storing information by key + value.

from react-native-mmkv-storage.

So are you suggesting to use https://github.com/mCodex/react-native-sensitive-info instead? Or use part of code from it instead of the above mentioned library?

from react-native-mmkv-storage.

Thats good information. Well lets see what fits in best in the current scenario.

from react-native-mmkv-storage.

No worries, i hope to use this soon :)

from react-native-mmkv-storage.