[x] There is no existing issue that already asks for this feature.
[ ] The feature already exists in rclone (on your PC or in Termux)
[ ] I am prepared to help make this feature
What problem are you trying to solve?
I'm not quite sure how to describe this properly and I'm not even sure this is possible:
So many FOSS application would profit from cloud integration but it surely doesn't make sense for every maintainer to create it on their own.
Some maintainers won't do it because of its effort. Some maintainers might be tempted to use untrustworthy proprietary components to achieve that. And some storages aren't trustworthy either so users might want to have to data rather encrypted which might again be some obstacle for a developer.
What should RCX be able to do differently to help with this problem?
Rclone (and thus RCX) solves these things on its own. It does this job very well but other applications don't have the possibility to integrate RCX easily (at least as far as I know).
It would be great if the missing bits (i.e. a usable API) could be implemented and/or a possible way could be documented (in easy steps so that maintainers will happily integrate RCX instead of proprietary solutions).
I'm not an Android developer therefore I have no idea whether this would be possible.
A straightforward way would probably be some proposed in-app documentation that says something like
install RCX from here
configure it
mount it
activate SAF
point the path that you want to use to the RCX mount
But this is somehow complicated, isn't it?
I guess steps 2 - 4 could be automated with some kind of app scheme or URL and using the Android share functionality?
So something like rcxrclone://some.app.id/context that will automatically be handled from rcx which would open a wizards for the details and jump back if this was successful.
Again, I'm not quite sure whether any of this makes sense. This idea just came to my mind when I thought that one second diary, MaterialFiles or epistolaire backup would profit from RCX integration.
It would be nice to have a solution whose user experience is so great that my mother could do it.
PS: Otherwise it would be good to have a standardized description for other app maintainers If the protocol-thingy wouldn't work.
Pre-Submission checklist
What problem are you trying to solve?
I'm not quite sure how to describe this properly and I'm not even sure this is possible: So many FOSS application would profit from cloud integration but it surely doesn't make sense for every maintainer to create it on their own. Some maintainers won't do it because of its effort. Some maintainers might be tempted to use untrustworthy proprietary components to achieve that. And some storages aren't trustworthy either so users might want to have to data rather encrypted which might again be some obstacle for a developer.
What should RCX be able to do differently to help with this problem?
Rclone (and thus RCX) solves these things on its own. It does this job very well but other applications don't have the possibility to integrate RCX easily (at least as far as I know).
It would be great if the missing bits (i.e. a usable API) could be implemented and/or a possible way could be documented (in easy steps so that maintainers will happily integrate RCX instead of proprietary solutions).
I'm not an Android developer therefore I have no idea whether this would be possible.
A straightforward way would probably be some proposed in-app documentation that says something like
But this is somehow complicated, isn't it?
I guess steps 2 - 4 could be automated with some kind of app scheme or URL and using the Android share functionality?
So something like
rcxrclone://some.app.id/contextthat will automatically be handled from rcx which would open a wizards for the details and jump back if this was successful.Again, I'm not quite sure whether any of this makes sense. This idea just came to my mind when I thought that one second diary, MaterialFiles or epistolaire backup would profit from RCX integration.
It would be nice to have a solution whose user experience is so great that my mother could do it.
PS: Otherwise it would be good to have a standardized description for other app maintainers If the protocol-thingy wouldn't work.