Open teolemon opened 1 year ago
Is-there a standard for this kind of data? Or can we do whatever we want?
We can do whatever we want. Heck, we could even create a standard for food scan histories ;-)
After the wikipedia, we could be the Braille or the Morse of food! 🎉
Just checking: for us, a barcode is only digits?
After the wikipedia, we could be the Braille or the Morse of food! 🎉
Just checking: for us, a barcode is only digits?
Yes, barcodes are only numbers-based, as EAN stands for European Article Numbering
In parallel, I've checked schema.org and I think that using the Product
type might be interesting in our case: https://schema.org/Product
do we dump product data, or just the lists of EANs + timestamp ?
Note that we are the defacto standard, and that no one else is really implementing anything at this point. If we were to dump without thought, what's the list of fields? Also, there's a way to generate CSVs from the website
If we want to be retro-compatible with the old Android app (I have to check for iOS), only 3 fields are exported in a CSV:
What about supporting iCloud on iOS? https://pub.dev/packages/icloud_storage https://pub.dev/packages/cloud_kit
And there's the same for Android with Google Drive: https://medium.com/@developerjo0517/backup-and-load-data-with-google-drive-in-flutter-1d901fd38f70
We certainly can and should. Is there a way to get backup consent ? It would be a way to stress that we don't save your personal data to the OFF servers. We would also need a stupid db dump to the phone memory for F-Droid
We certainly can and should. Is there a way to get backup consent ? It would be a way to stress that we don't save your personal data to the OFF servers. We would also need a stupid db dump to the phone memory for F-Droid
We could ask for consent the first time the user creates a list. But yes, F-Droid is still an issue here and in that case, the basic import/export by CSV would do the job.
Add a full data portability feature
Why
Part of
525