Thomas Baker
My feedback
12 results found
-
7 votes
Thomas Baker
supported this idea
·
An error occurred while saving the comment -
2 votes
Thomas Baker
shared this idea
·
-
15 votes
Thomas Baker
shared this idea
·
-
6 votes
Thomas Baker
supported this idea
·
-
54 votes
Thomas Baker
supported this idea
·
-
489 votes
Thomas Baker
supported this idea
·
-
482 votes
Thomas Baker
supported this idea
·
-
383 votes
Thomas Baker
supported this idea
·
-
687 votes
Thomas Baker
supported this idea
·
-
820 votes
Thomas Baker
supported this idea
·
-
1,237 votes
Thomas Baker
supported this idea
·
-
1,989 votes
Thomas Baker
supported this idea
·
I second this. I wanted to incorporate Proton SDK into a KMP + Compose Kotlin app and decided it wasn't worth it.
The desktop SDK client isn't ready for prime time, and both ways there is no good OAuth PKCE flow that will allow for a trusted auth. I realize the encryption layers make this hard to acheive.
Maye some sort of SAF or file system provider service could be exposed via the other Proton Drive apps that Proton users would already have installed on their phone?
Even it not this. Then clear documentations and a app registration console so clients could cleanly use the API's themselves?