Bug 102222 - Viewer should not show the system's directory structure
Summary: Viewer should not show the system's directory structure
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Android Viewer (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-09-16 09:32 UTC by Tin Man
Modified: 2022-05-03 19:54 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tin Man 2016-09-16 09:32:56 UTC
Right now, after opening up LibreOffice Viewer, the user is presented with the system's entire directory structure and it's up to her/him to find the right ODT files. This flies in the face of the mobile pattern of abstracting the file system structure from the user [1] and makes it hard for people to find their files (as they're generally not accustomed to the directory structure).

The Google Docs apps, Microsoft's Office apps, WPS Office, and most other productivity apps all abstract away the directory structure and only show the files that they can open, leaving complex file management to dedicated file managers.

[1] http://fabfuture.blogspot.cz/2013/05/life-without-files.html
Comment 1 Cor Nouws 2016-09-16 09:55:57 UTC
Good idea, thanks! > New
Comment 2 Heiko Tietze 2016-09-16 11:47:30 UTC
The idea is "UX approved" since Tin Man shared it first over the mailinglist.
Comment 3 Michael Weghorn 2022-05-03 19:54:08 UTC
-Android Viewer now uses the documents provider framework [1], which uses the system file chooser provided by Android.
The app's custom file abstraction layer and documents browsing UI has been dropped in

commit a23bd42e9b2f6401c710ac95afcc3aa8f360d65c
Author: Michael Weghorn
Date:   Tue Apr 6 14:26:06 2021 +0200

    android: Drop custom file abstraction + UI

The custom document browsing mechanism, which was accessing the file system directly would also no longer be in line with security requirements for current Android versions, s.a. [2].
Using the document provider framework also provides consistency with other apps. 

Given the above, my understanding is that any improvements in how file browsing works would not be done in Android Viewer, but either in one of the existing document providers, or by creating a separate app that provides a new document provider or a different way of browsing the file system and opening files from there.

Therefore, I'm closing this as WORKSFORME. (NOTOURBUG or WONTFIX might fit as well.)


[1] https://developer.android.com/training/data-storage/shared/documents-files
[2] https://developer.android.com/about/versions/11/privacy/storage#scoped-storage