Treeger - UI Screens, Navigation, UX Behaviour

The Home dashboard contains application-wide Spaces, Recently Used, Pins, and Storage sections. Spaces, Pins, and Storage use compact two-column destination cards; Recently Used remains a full-width list so filenames and file metadata retain enough horizontal space.

All destination cards share the same subtle surface treatment. Folder destinations use a bare 20 dp folder icon rather than nesting a second icon surface inside the card. Space and Storage labels use a larger semibold single-line style; Pin labels use the more compact semibold body style to leave room for the reorder control. Space icons use the same 20 dp size. The Pin reorder affordance keeps a comfortable touch target while drawing a low-contrast 20 dp four-direction icon.

Storage is available when all-files access is granted and does not need pinning.

If all-files access is not granted, Storage shows a short permission row with an action to open Android’s all-files access settings for treeger.

List rows show a compact thumbnail or fallback artwork, name, and one supporting line. In Grid, folders use neutral compact horizontal cards, two per row, with a bare 20 dp folder icon and semibold name. Files remain three-per-row artwork tiles with up to two filename lines and one supporting line. Ordinary files use size as the supporting value; folders do not repeat a Folder label. Recursive search results use their location when that context is more useful than size.

DCIM, Pictures, and their local descendants default to Grid. Every other folder defaults to List. Choosing the other mode creates an override for that exact folder; Use default removes it. View-mode overrides follow renamed and moved folders.

Grid uses six virtual columns at the reference phone width: folder cards span three columns and file artwork spans two. Images use bounded, memory-cached thumbnails; other files use low-chroma extension tiles. Folder cards intentionally omit size, creation time, and direct-child count because the current file-provider abstractions cannot supply those values reliably without additional traversal. List and Grid share selection, properties, Search, Sort, and operation behavior. Sort remains global in this delivery.

Search opens beneath the existing breadcrumbs. Sort applies to both ordinary folder contents and search results and is selected from chips in the Browse options sheet; there is no second dropdown layer or persistent sort label in the content area.

Sort also determines the visible sections in both List and Grid. Date uses Today, Yesterday, and individual days; Name uses locale-aware initial letters plus #; Type uses friendly file types; Size uses stable size ranges. Sort direction sets section order. Folders remain in one leading section because their size and modified metadata are not reliable grouping signals. Users without a stored Sort start with Newest; an existing stored choice is preserved.

The default scope searches the current folder. Scope can expand explicitly to subfolders or all internal storage. Type, modified-date, and size filters appear as a horizontally scrollable chip row. Recursive results show their source location and retain normal selection, properties, copy, move, share, and Delete behavior.

Non-default filters use the active identity’s low-chroma primary container. Search result summaries use semibold primary ink; partial-search and unavailable-folder details remain in secondary ink.

Content Spaces derive a temporary Format menu from the formats actually present in their retained result snapshot. Available PDF, Plain text, HTML, Markdown, Rich text, Word, Spreadsheet, Presentation, Ebook, AsciiDoc, JSON, and XML entries show result counts. Unknown text formats remain under All formats rather than being grouped into Plain text. The selection is retained with the Space session and combines with query, broad type, location, modified-date, and size filters. This is a generic Content-browser facet and does not depend on a Documents Space ID.

Recursive search is incremental, cancellable, and local. It does not require or create a permanent content index.

If no app can open a file, show a Snackbar: "No app found to open this file."

When handing AsciiDoc files to Android, .adoc, .asciidoc, and .asc use text/plain. This avoids the unrelated and duplicated handlers produced by a / fallback while remaining compatible with editors that accept ordinary text files.