Source-code rendering — highlighting plus line numbers — is one of the four things verified on a clean device. This page is the procedure end to end: getting a codebase onto the phone, opening a file, and the two search surfaces that turn a file tree into something you can actually navigate rather than scroll.
FoldRender is on the Play Store as FoldRender: Git Repo Reader, package id dev.foldrender.app, free and distributed worldwide. Install it the ordinary way — no allow installs from this source prompt to approve, and updates arrive on their own. The app declares minSdk 30, so it needs Android 11 or newer; Play will tell you if a device is below that rather than letting you install a build that cannot run.
Either clone it, or point at a folder you already have. To clone: branch glyph in the top bar, paste into Clone an HTTPS repository URL, tap Clone; public repositories clone anonymously with no account. To use a folder already on the phone: Open a folder and grant it through the Android folder picker. The grant persists across restarts, and the folder becomes a workspace either way — the difference is that a picked folder gets no git integration.
The first listing of a large repository — around 4,600 files — takes a long time and shows only a spinner, with no progress bar and no file counter. Subsequent navigation is lazy: each directory lists its children when you expand it, with its own small spinner on the row.
In the Files tab, source files are badged with their uppercased extension. Files matched by the repository's .gitignore are hidden by default — build output, node_modules, virtualenvs — with a Show ignored chip to bring them back when you actually want to look at a lockfile or a generated artefact.
Above the file sits <Language> · N lines — the detected language label and the line count — with · truncated appended if the file was cut at the 32 MB limit. About sixty language labels are recognised by extension, from Kotlin, Java, TypeScript, Python, Go and Rust through to Terraform, Protobuf, Nix and Zig. Highlighting is lexical and applied to the whole file, with line numbers down the gutter.
A Wrap chip sits next to the header. Off, long lines scroll horizontally and the line numbers stay aligned; on, they wrap into the reading column. Folded, wrapping is usually what you want; unfolded, horizontal scroll usually reads better.
The magnifier in the top bar opens the find bar — placeholder Find in document…, a current/total counter and up/down chevrons. Source, logs, plain text, Markdown, notebooks, CSV and JSON/YAML/TOML all support it.
The left pane's Search tab searches every file in the workspace, not just the open one. Type into Search in workspace…, optionally flip the Regex chip, and results stream in as path:line rows with a preview; tapping one opens the file and jumps to that line. It respects .gitignore, skips binaries, skips files over about 1.5 MB, and stops at 500 hits — the status line then says the result set was capped, so you know to narrow the query.
The Recent tab collects what you have opened. Long-pressing a file in the tree pins it as a favourite, which is what you want for the three or four files you actually re-read in a codebase.
JSON, YAML, TOML and lockfiles open as a collapsible tree with ▸/▾ expanders, child counts on each node ([3] for an array, {5} for an object), a path breadcrumb and a Copy path button — plus a Raw chip when you want the original text back. Cargo, Poetry, PDM and uv lockfiles are parsed as TOML.
CSV and TSV render as a virtualized table with a frozen header row, row numbers, and column sorting that understands numbers, so 42 sorts before 100 rather than after it.
.log files and logcat dumps get severity colouring — ERROR, SEVERE, FATAL and PANIC one colour, WARN and WARNING another, DEBUG, TRACE and VERBOSE a third — including the bare E/, W/, D/ and V/ prefixes logcat writes.
The honest list — shipped-but-unverified behaviour included, so you can tell before installing whether this build does the thing you came for.
Four apps people actually reach for, and the one axis that separates them: whether the repository ends up on the phone, and whether anything renders it once it is there.
| Tool | Download price | Where you get it | Clones to the device | Renders PDF / notebook / Markdown | Editor or shell |
|---|---|---|---|---|---|
| FoldRender 0.8.2 | US$0 | Google Play, worldwide | Yes — HTTPS, anonymous for public repos | Yes — native Compose renderers | No, deliberately: a reader, not an IDE |
| GitHub Mobile | US$0 | Google Play and the App Store | No — it reads repositories hosted on GitHub | Only what GitHub itself renders, online | Edits files inside a pull request |
| Termux + git | US$0 | F-Droid or GitHub | Yes — the real git CLI | No — terminal text only | Yes, a full shell and any CLI editor |
| MGit 1.7.0 (2023) | US$0 | F-Droid only | Yes — clone, pull, push, HTTPS or SSH keys | No | No — its own listing says it ships no text editor |
Prices are for the download. GitHub Mobile’s capabilities follow your GitHub plan; Termux and MGit are both free software. MGit’s version and date are from its F-Droid listing.
Every figure here is read out of the shipping build or off a primary source listed at the foot of this page — nothing is rounded up for effect.
0.8.2, build 16, last reviewed on 27 August 2026.minSdk 30 — the API level Android 11 shipped with in 2020 — compiled and targeted against API 36.The primary documents behind the figures above, so you can confirm any of them without taking our word for it.
git-clone reference — the operation the app's clone button performs, in the words of the project that defines itminSdk names as its floorPage last reviewed 2026-08-27, against FoldRender 0.8.2.