A Fold 7 unfolded next to a laptop, for the specific job of reading a codebase: the phone with FoldRender wins on portability, focus and offline reading, and loses on editing, navigation depth and anything that runs code. This page is the comparison nobody pads out — only behaviours that are in the shipped build, with the unverified ones labelled as such.
FoldRender is on the Play Store as FoldRender: 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.
Unfolded, FoldRender puts the file tree on the left and the rendered document on the right — the two-pane layout a laptop IDE gives you, on a screen that fits in a pocket. Source files render with whole-file lexical highlighting and line numbers across around sixty languages, Markdown renders as Markdown (tables, task lists, callouts, mermaid, LaTeX), PDFs get a page counter and thumbnails, notebooks show their cells and saved outputs. Scroll position is stored per document, the Recent tab collects what you opened, and a long-press pins favourites. For reading — on a train, in a hallway, on a plane — it is not a compromised laptop; it is a better hallway monitor.
Navigation depth. Highlighting is lexical, not semantic — there is no language server, no go-to-definition, no find-references, so answering “who calls this?” means grep, not a keystroke. Workspace search caps at 500 hits and skips files over about 1.5 MB, and in-document find does not exist for PDFs, images or HTML. The first listing of a large repository — on the order of 4,600 files — takes a long time behind a bare spinner with no progress indicator. Files over 32 MB are truncated. None of this is fatal; all of it is slower than the laptop equivalent.
There is no editor, no terminal, no build, no run. FoldRender reads a codebase; it does not change or execute one. On-device git covers clone and read: committing and pushing are in the build but have not been verified end to end — and since the app has no editor, there is nothing in-app to commit. The diff viewer is likewise present but unexercised. A folder opened through the Android picker gets no git integration at all; git belongs only to repositories the app cloned itself, over HTTPS (no SSH).
Offline and always-with-you. Once a public repository is cloned — anonymously, no account — every renderer works with the radio off, diagrams and equations included, because mermaid and KaTeX ship inside the APK. The Reading sheet's Line width control (480–1200 dp) does something most desktop setups never bother with: it caps the measure, so prose on a big unfolded screen reads like a page instead of a banner. And the device that is always in your pocket beats the laptop that is home in a bag, every time the choice is read-now versus read-later.
The pattern that works: laptop for writing, Fold for reading. Code review reading on a commute; docs and design discussion between meetings; a paper and its implementation on a flight. Pull out the laptop when the task becomes editing, debugging with a language server, or running anything. The Fold is not trying to win that fight — it is trying to make the reading half of the loop happen where the laptop isn’t.
Everything on this page comes from the build or the clean-device test pass. Markdown, source, PDF and notebook rendering are the verified four; commit, push and the diff viewer are described as shipped-but-unverified, because that is their actual state.
The activity handles orientation, screen-size and posture changes itself, so folding is a layout change rather than an app restart — tree and document reflow between two panes and one, and the activity declares exactly the configChanges that make this true by construction. We have not measured fold/unfold smoothness on retail Fold hardware and make no claim about it.
In-document find for text formats, and workspace-wide grep with path:line results you can tap. On a phone this pair does the work that go-to-definition does on a laptop — with more typing and zero setup.
The honest list — shipped-but-unverified behaviour included, so you can tell before installing whether this build does the thing you came for.