←back to thread

410 points morsch | 1 comments | | HN request time: 0.208s | source
Show context
moonshot5 ◴[] No.43986181[source]
AOSP platform dev here. (Filesystem) Opinions my own, I don't speak for Google.

Disclaimer: I don't use nextcloud, and have not looked at their app specifically, this is just a surface level observation from my relatively informed perspective.

My take: SAF would work for this use case, as others have already mentioned.

Google Drive does not have the permissions that next cloud claims Google is giving preferential treatment to, and is delivered via the Play store in the same way nextcloud's app is.

As others have also observed, permissions such as MANAGE_EXTERNAL_STORAGE have been rampantly abused in the past, often in horrific ways.

replies(7): >>43986712 #>>43987576 #>>43987745 #>>43989733 #>>43990209 #>>43991397 #>>43992185 #
apitman ◴[] No.43989733[source]
SAF is a terrible solution for anyone trying to make a cross-platform app (and if you're not then why are you targeting Android as your one platform?), because it doesn't work with native code.
replies(1): >>43998376 #
pjmlp ◴[] No.43998376[source]
JNI exists, and poor fellows having to write a bit of Kotlin or Java.
replies(1): >>44018083 #
1. apitman ◴[] No.44018083[source]
The problem isn't the language, it's that the API completely changes the paradigm of how you access the filesystem.