While the techniques for persisting data on iOS and Android is covered in the .md file - the same for Windows is strangely missing.
Customers are going to want to know how their sensitive information is being handled by applications which consume this library.
I shouldnt have to read and understand the native C code to find out where the data is stored, how it's encrypted, symmetric/asymmetric, how keys are managed etc.
Android and iOS implementations benefit from just being able to direct the developer/application customer to Google's KeyStore or Apple's Secure Enclave documentation - but it appears it's roll-your-own on Windows, so is in need of clear documentation.
While the techniques for persisting data on iOS and Android is covered in the .md file - the same for Windows is strangely missing.
Customers are going to want to know how their sensitive information is being handled by applications which consume this library.
I shouldnt have to read and understand the native C code to find out where the data is stored, how it's encrypted, symmetric/asymmetric, how keys are managed etc.
Android and iOS implementations benefit from just being able to direct the developer/application customer to Google's KeyStore or Apple's Secure Enclave documentation - but it appears it's roll-your-own on Windows, so is in need of clear documentation.