2 ms·
There are two problems with that: 1) Mobile users don’t know how to use files 2) Where do you export it? If you put it in one of the shared folders now the unen
by deno 3y ago
There are two problems with that: 1) Mobile users don’t know how to use files 2) Where do you export it? If you put it in one of the shared folders now the unencrypted archive of all user’s data is just sitting in a folder that many unrelated apps can access.
- jwells89 3y agoMake a standardized file type for web data archives, which then allows other browsers (which can open it) to show up in a share sheet that shows up when the user taps an export button. This sends the file directly to the other browser which can then do as it pleases with the data. No filesystem knowledge required, and share sheets are common mobile user knowledge.
- shadowgovt 3y agoThe problem is that the question of what is a "browser" is an easy question for humans to answer but doesn't line up to software. The short story is that the permission model would have to be changed; they have to add an Android permission for sharing browsing data that apps would have to declare and users would have to opt into. And of course that increases the risk surface area; We know from past examples that malicious apps sneak through (or non-malicious apps previously signed off on end up purchased by someone else and become malicious) and users really don't understand security. The state is extractable via Google take out and the safest solution might honestly be to not support this directly on Android and instead require Mozilla to figure out how to import a takeout archive via the cloud.
- deno 3y agoThis is better than nothing but in practice will be rarely used if the flow has to be initiated by user (from some deep menu and in a different app than the one they want to use).