download to phone #1192
Comments
|
Our app is currently meant to be like a sync (although it is currently no automatic 2way sync) between device and folder, same like on desktop pcs. As of permission problems, if our app would try to store the files all over the device, this would also hardly work. |
|
Hello. Thank you for the information. Br, |
|
Downloading to sdcard would be possible with this permission. You can still use the app: download the app and then copy the file with a file explorer to download folder. |
|
If you do not know exactly where Nextcloud stores files... you need some time to found it :). The folder structure under Android is terrible. (for all apps) "Save to Download" (i guess this is a standard folder for many apps) could also improve the workflow. |
|
hmm, still unsure. |
|
"Backup bitcoinwallet to local device storage download folder" ? |
|
Sorry. I do not fully understand the question. @comradekingu The point is: So a option "Save file to Download" or "Save file to sdcard" should help and should improve this workflow if the user needs the file local (to continue working with other apps.). Christian |
|
I guess the "android" way would be to send this email to the app OR use "open with", e.g. |
|
Yes if the app is available as "receiver" or connected with the file extention this would the "normal" way. Let me show you practical example: Phone Samsung S8 (latest image), latest Nextcloud APP (beta): o long press to the image file: send => shows only options to share the file... WA, Hangouts, K9, etc etc Okey i choose now "Make file offline available"... use my file explorer... after searching ..move the file to the cam folder... open the gallery app... and now i can set this pic as background. But much easier is: |
"make file offline available" is not necessary. Right after downloading the file it is available on storage. "make file offline available" is to keep it synced.
This will be available in next version directly. You can try the dev version if you want |
|
Looks like the feature is not needed. Closed |
|
A few things.
EG, Don't expect you know what the user needs. You don't.
Nope. This app prevents this simple act, something users have been doing for decades, and seemingly on purpose.
What happens when I have 75 files? Hmm. I can't do that! I select the folder.. and, no way to do this. I go into the folder and select all files? This option doesn't exist. In fact, I can't do many things with more than one file for some odd reason... the menu is severely truncated. Now, let's say I want to do a very, very, very, very simple thing -- like sync my Nextcloud folder, and then copy some files to a OTG USB device or my on-board sdcard.. and give it to a friend. How can one do this easily? Without endlessly searching my filesystem for where the files are hidden? Should I select the files one at a time, all 75 of them, and 'send/share'? I see a lot of "but the user should be doing this." Or, "we don't want them to this". Yet, something as simple as all of this, of copying 75 files onto a USB stick? Is an act of pain with the Android Nextcloud app. Why? |
|
Same here, always wanted to use Nextcloud to easily get a file from and to Android phone. So sending via email is still the easiest way, although not really safe. |
|
@nextcloud/android what do you think? @archont00 what exactly would you expect if there is a "download to phone" button:
|
|
If possible, a folder chooser would be better. (Not sure how Android deals with $DOWNLOAD folder path - localisation, various Android versions, etc. It would be unfortunate if it forces absolute path name and creates the folder, if not existing.) |
|
Most apps I know, have the ability to set a path in config.
K-9, for example.
Some apps remember the last saved location, and prompt for it in the
'choose directory dialog'.
I think key here, is just being able to select one-or-many, and being
able to save to a location of choice.\
Minimalistic design doesn't mean the user can't have choices.. for
example, I can already choose file paths for 'instant upload'....
|
That is something that could be considere in the (farer) future maybe but complicates the use of the feature
Android's API offers this folder info and there is no localisation whatsoever since this is simply the underlying filesystem so this folder is always named the same no matter the language of the UI on top of it. Other than that I am not fully convinced I would like to have such a feature. While I understand the use case here I also expect other users (not involved in this discussion) might then expect these files to be kept in sync too (which isn't possible or shouldn't be tried to do) so they will brag about it, raise issues etc. etc. which is something we than need to deal with (as in spending time on it) which you won't have to deal with. But sure we can give it a try. "Any destination" should be the far future if at all since it is rather complicated (checking write access etc. etc.). |
Hmm i understand but... |
No because you can't donwload to "..." via the app at the moment. Like I said I am not against implementing such a feature, I just wanted to make everyone aware that users may have further expectations regarding this feature if it is actually in place. @schnello just having played around with the browser on my phone would you then be fine with a "save to downloads" option? @nextcloud/designers what do you think in general about this feature? Also cc @tobiasKaminsky again for further feedback |
From my point of view: completely sufficient |
|
For me, the 'save to downloads' would be fine, too. |
|
Design-wise I would be fine with a "Save to downloads" element in the share sheet. But not another action in the actions dropdown, as that is yet another thing for an edge-case and would also confuse people. Does that work?
@schnello I would also say that’s a limitation of that app? If you could set a manual path there, it could be set to the Nextcloud folder and then it would automatically be synced, which would be pretty sweet. |
|
@jancborchardt |
|
@schnello well, ideally that app would offer Nextcloud sync, or a proper interface to just "Sync with Nextcloud" which automatically picks the path. :) The goal should be 0 fiddling instead of just fiddling somewhere else. :D |
|
Actually, I see it as sufficient if i find the files in a simple place. |
|
One thing.
No one -- ever, is going to be confused by 'save to downloads'. Ever.
70 year old, new computer users have been 'saving to downloads' with web
browsers since 1998. People have had a 'download' folder in Windows for
decades.
I appreciate concerns about excessive options, but urge people to keep
these sorts of things in context.
…On Thu, 18 Apr 2019 03:20:53 -0700 Jan-Christoph Borchardt ***@***.***> wrote:
Design-wise I would be fine with a "Save to downloads" element in the
share sheet. But not another action in the actions dropdown, as that is
yet another thing for an edge-case and would also confuse people. Does
that work?
--------------
> The app "bitcoinwallet" need the backup under the path /download
@schnello I would also say that’s a limitation of that app? If you could
set a manual path there, it could be set to the Nextcloud folder and
then it would automatically be synced, which would be pretty sweet.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#1192 (comment)
|
|
I just would like to add my comments here. I'm fine to have a 'save to downloads' or 'save as ...' entry here. Maybe i misunderstood something, but - any third party app must not have permission to read/write on nextcloud file basis in android (even with storage permission). Reading and writing to nextcloud must ever be done via intent or content providers. Any other case would untermine androids sandbox concept. Think of your slogan 'Protecting your data'. |
|
As a comment, in Google Drive when I select a file and click "Download", it downloads the file to Internal Storage > Download This allows me to download a file (such as an audiobook) and use it with another app (put it in my audiobook file on my phone). Without the ability to download the file to the phone, I use the browser instead of the phone. I know saving to phone in the app puts the file somewhere, but I can never find it and it's easier to just open it in the browser..... |
|
That is not the Android way of dealing with files, but a common Desktop approach. Sure, we can add "download to device", but then user download it, modify it and wonder why the changed content is not updated… |
Add a big popup... "Content will not synced". ;) |
|
@tobiasKaminsky see Jan's comment #1192 (comment)
So it can be implemented while it isn't a high priority for you/me, so rather a "contributions welcome" issue |
I would push back on this statement a bit. This is exactly how Google Drive deals with files in their mobile app and I would think Google would be the authority on "the Android way of dealing with files" |
|
How can you download something from a prompt if it isn't a file? How about just a download icon, and then a setting that allows asking every time where exactly the user wants it to go? As for logic for always/re-upload this if not changed upstream in the meantime, isn't that a different question? Seems OK with those sane defaults, and toggling a download and upload button to do more things (or doing it some other way), then presenting the prompt if it is unintuitively destructive. Then there is: Oh, but there is no secondary logic like marking files/doubleclicking/hamburger menus that work, or capable users on the Android end, etc. etc. |
|
I mean I think Google Drive does a pretty good job here of having sane options. "Make available offline" and "Download" is a workflow most people are used to.
|
|
How about at least a standard It is not user friendly to
P.S. There is an |
|
This was implemented in #10443 and has been available for a while |
Actual behaviour
A simple action is at the moment not possible.
The app "bitcoinwallet" need the backup under the path /download
So i want so save the backupfile from my nextcloud... to my phone.
Expected behaviour
A menu option: save file to phone location.
The text was updated successfully, but these errors were encountered: