Lagrange

Most browsers try to render more of the web. Lagrange tries to render less of it, and to render it well. It is a client for Gemini, a lightweight internet protocol, and for the wider “smallnet,” a loose set of small, minimalist alternatives to the web. On the App Store it goes by the more literal name Lagrange Smallnet Browser, which describes the job exactly.

The app comes from Jaakko Keranen, and it is free and open-source. That suits the territory. The smallnet is a hobbyist space built on the idea that publishing and reading online can be simpler than the modern web allows, and a closed, paid client would sit awkwardly inside it.

The project reaches beyond iOS: Lagrange also has desktop and terminal editions. There is also an Android build distributed outside Google Play and a text-based terminal version for people who would rather stay in a shell. The iOS app is one front end of a broader project, not an isolated port.

Its market position is easy to state. Lagrange is the typography-first option for people who already know what Gemini is, and a low-risk entry point for anyone curious enough to look. Its App Store footprint shows how specialized that audience is: 4.4 out of 5 from 7 ratings. The rating is high but based on a tiny sample, so it indicates a specialized audience more than broad consensus.

The main caveat is platform parity: the iOS edition is not the full desktop build. With only seven ratings, the sample is too small to support broad conclusions either way.

• Multi-protocol support: Gemini first, plus Gopher and Finger, Titan for uploading content, and the hobbyist protocols Spartan, Nex, Misfin and Guppy.
• Typography and themes: Full Unicode support, several visual themes, and light and dark modes.
• Automatic per-site styling: Every Gemini site gets its own page style and icon, so domains are easy to tell apart.
• Identities: TLS client certificates that Gemini sites use to recognize visitors in place of accounts and passwords.
• Unified sidebar: Page outline, bookmarks, browsing history and identities in one panel.
• Tabs and split view: Multiple tabs, plus split view for reading two pages at once.
• Smart address bar: Suggests matches from bookmarks, history and identities as a URL is typed.
• Feeds and media: Feed subscriptions, inline images, and playback for MP3, Ogg Vorbis and WAV audio.
• Proxy support: Requests can be routed through proxy servers.

One Client, Many Small Networks

Protocol coverage is the first thing that separates Lagrange from a single-purpose reader. Gemini is the headline, but the app also speaks Gopher and Finger, plus several hobbyist protocols: Spartan, Nex, Misfin and Guppy. Supporting experimental protocols with small followings shows intent. It tells smallnet regulars that the developer follows the scene closely, and it makes a link into an obscure corner of the network less likely to dead-end.

For a newcomer, that list reads as jargon. The breadth costs little, though. Protocol support only matters at the moment a link needs it, and a browser that understands more link types sends its user elsewhere less often.

Titan deserves separate credit. It handles uploading content, which turns Lagrange from a reader into a two-way tool. Publishing to a Gemini site from the same app used to browse it removes the need for a separate upload workflow on a phone or tablet. That is a practical advantage for anyone who maintains a site rather than just visiting them.

Identity Without Accounts

Gemini sites do not ask for accounts and passwords. They recognize visitors through TLS client certificates, which Lagrange presents as identities. The design choice here is the right one. Identities sit in the sidebar next to bookmarks and history, and they appear in address-bar suggestions alongside both. Giving a certificate the same place as a saved page goes a long way toward normalizing a concept most people have never met.

It does not remove the conceptual hurdle. A certificate is more abstract than a username and password, and anyone arriving from the mainstream web will face real onboarding friction. Lagrange cannot make the protocol’s model simpler than it is. It can keep that model visible and organized, and the interface is built to do exactly that. For privacy-minded users the trade is attractive: no account to create, no password to reuse, and one clear place to see which identity is which.

Reading and Navigation

The sidebar carries most of the structural weight. It combines a page outline, bookmarks, browsing history and identities in one panel, so the tools for moving within a document and between documents live in the same place. The outline is the most useful of the four on long pages, where it works as a table of contents the author never had to write.

Multiple tabs and split view bring desktop habits to the format. Both suit research-style reading, where one page keeps sending the reader to another. The address bar’s suggestions pull bookmarks, history and identities into a single input, which cuts down on typing, the most expensive interaction on a touch keyboard.

Then there is automatic per-site styling. Every Gemini site gets its own page style and icon, with no work from its author. On a network built around minimalism, pages from different domains can easily look alike. Generated styling gives each site a recognizable face and makes it obvious when a link has crossed into a different domain. This is a useful design decision, because it solves a navigation problem with visual design rather than with more interface.

Feeds, Media and Plumbing

Feed subscriptions give the app a reason to be opened daily, not only when a link arrives from elsewhere, and they make the browser double as a reader. Inline images and playback for MP3, Ogg Vorbis and WAV audio cover the media a minimalist network is likely to carry, without turning Lagrange into a media app. Proxy server support rounds out the toolkit for users who route traffic through an intermediary.

Each of these features is modest on its own. Together they mark the difference between a protocol demo and a daily driver, and Lagrange lands on the daily-driver side.

Lagrange’s look follows from its priorities. Typography leads. Full Unicode support means text in any script should render properly, which is the baseline requirement for a browser built for reading. Several visual themes and light and dark modes let readers tune the page. The styling, color and font options are built for readers who care about typography.

The automatically generated site styles and icons are the most distinctive visual idea. They add variety and a sense of place without asking anything of site authors, and they keep a deliberately plain medium from becoming visually monotonous.

Lightweight protocols mean small pages, and a text-first client of this scope should be light on hardware. Background activity is the main design concern: a reading app has little legitimate reason to do heavy work when not in use, so iOS battery settings are worth checking after setup.

On iOS and iPadOS, Lagrange is a touch app built from a design with desktop roots. The sidebar, tabs and split view fit naturally on an iPad screen. On iPhone, the same sidebar and split view have far less room, so the phone is the more cramped of the two. The address bar’s suggestions earn their keep on touch, where every avoided keystroke counts.

Parity is the main caveat. The iOS edition is a front end of a broader project, not a full desktop replacement. Anyone who depends on a particular desktop capability should confirm it exists on iOS before relying on the mobile edition. Because the app is free, finding out costs nothing.

The App Store listing name, Lagrange Smallnet Browser, is the one to search for. Outside Apple’s platforms, the same project covers Windows, macOS, Linux, an Android build distributed outside Google Play, and a terminal version. iOS users who also browse from a computer can run the same client there.

Lagrange meets a niche demand with appropriate craft. Its protocol coverage is broad. Its identity handling turns an awkward concept into something organized. Automatic per-site styling is a useful fix for a real navigation problem, and the focus on typography is the right priority for a browser built for reading.

The reservations are real but bounded. Background activity is a design concern for a reading app, the iOS edition is not the full desktop build, and client certificates will puzzle anyone arriving from the mainstream web. None of that changes the recommendation for the audience Lagrange serves. For Gemini and smallnet readers on iPhone and iPad, it is free, open-source and designed with care, and we recommend it to that audience. For everyone else, the free price makes it a low-risk experiment, but the narrow focus limits its appeal.