Frigoligo

A Flutter-built read-it-later client, honestly reviewed. Only relevant if you already use wallabag — or are about to.

TL;DR

• What it is: A Flutter-based mobile and desktop client for wallabag, the self-hosted read-it-later service. Frigoligo is the app you install on your phone; wallabag is the server it talks to [3][README].
• Who it’s for: Anyone already running wallabag who finds the official mobile app frustrating. Also: anyone building a Pocket/Instapaper replacement stack who wants a better reading experience than wallabag’s default client [3][4].
• Cost: Frigoligo itself is free (MIT license). Your total cost is the wallabag server — either a self-hosted VPS (~$5–6/month) or a paid wallabag.it account [README][4].
• Key strength: More modern design than the official wallabag Android app, better font control, smoother sync [3].
• Key weakness: It’s a client, not a standalone tool. It does nothing without a wallabag backend. With only 144 GitHub stars, this is a small community project — not a product with a roadmap and a support team [README].
• Honest framing: If you don’t already use wallabag, Frigoligo is the wrong starting point. Start with wallabag. Then come back here.

---

What is Frigoligo

Frigoligo is a wallabag client — a mobile and desktop app — built with Flutter. If wallabag is the server that saves and stores your read-it-later articles, Frigoligo is what you use to actually read them on your phone, tablet, or desktop. The project describes itself as aiming to be “KISS, Universal, Pluggable, Offline first, and Innovative” [README].

The Flutter choice matters: Frigoligo runs natively on Android, iOS, macOS, Linux, and Windows from a single codebase. There’s also an experimental web app. Unlike most self-hosted tools reviewed here, Frigoligo ships on mainstream stores — App Store, Google Play, F-Droid, IzzyOnDroid, and Flathub — so installation on mobile requires no technical setup beyond tapping a button [README].

What it doesn’t do: save articles, run a server, manage subscriptions, or work without wallabag. This is a pure client. Understanding that distinction is the entire framing for this review.

The project has 144 stars on GitHub, 8 forks, 42 releases as of this writing, and accepts community translations via Weblate. It is not a large project. The developer appears to be a single maintainer (casimir) with a small group of contributors. That’s not a disqualifier — it’s a data point [README][1].

---

Why People Choose It

The only first-hand comparison review available [3] comes from a writer who uses wallabag as their primary read-it-later tool and switched from the official wallabag Android app to Frigoligo. Their reasons: “Frigoligo has a more modern design, gives me more control over the fonts that I use, and it works a bit more smoothly than the wallabag app.”

That’s the full competitive case, stated plainly. Frigoligo isn’t competing with Pocket or Instapaper directly — it’s competing with the official wallabag Android app, which has existed since wallabag itself and carries the visual weight of its age. If you’ve used the official wallabag app and found it clunky or spartan, Frigoligo is the upgrade path.

The broader wallabag ecosystem context is relevant here. Source [4] — a wallabag review — notes that Mozilla announced it was closing Pocket, which has pushed more people toward wallabag as a self-hosted alternative. That migration creates a fresh population of wallabag users who haven’t committed to the official app and might prefer Frigoligo’s reading experience from the start.

AlternativeTo lists Frigoligo alongside tools like Karakeep, Readeck, and Linkwarden in the “Read It Later / Open Source” category [1]. On that listing it has only 3 likes, which is an honest indicator of its current reach.

---

Features

Based on the README and available documentation:

Reading experience:

• Clean reading view with user-controlled font settings [3][README]
• Dark mode support (visible in screenshots in README)
• Offline-first architecture — articles sync to the device and are readable without network access [README]

Cross-platform:

• Android, iOS, macOS, Linux, Windows — all from the same Flutter codebase [README]
• Available on App Store, Google Play, F-Droid, IzzyOnDroid, and Flathub [README]
• Experimental web app available (auto-updated from main branch — not for production use) [README]

Deep link integration:

• Custom frigoligo:// URL scheme for OS-level integration [README]
• /save?url= deeplink — lets you pipe URLs into Frigoligo from shortcuts, share sheets, or external automation [README]
• /?articleId= — opens a specific wallabag article directly [README]
• /login — prefills credentials for automated setup [README]
• /logs — opens a log console for debugging [README]

Sync:

• Syncs read/archive/delete states back to wallabag server [3]
• Works offline and reconciles when connectivity returns [README]

Translations:

• Community-managed via Weblate; languages must reach 80% completion to ship [README]

What it doesn’t have (and likely won’t, by design): article saving from a browser extension (that’s wallabag’s job), tagging UI, RSS feed management, or any server-side features. Frigoligo deliberately offloads all of that to wallabag.

---

Pricing: SaaS vs Self-Hosted Math

Frigoligo itself costs nothing. MIT license, no subscription, no in-app purchases [README].

The cost conversation here is about the full stack: wallabag (server) + Frigoligo (client).

The self-hosted path:

• Frigoligo: $0
• wallabag server on a VPS (Hetzner, Contabo): ~$5–6/month
• Your time to set up and maintain wallabag

Hosted wallabag via wallabag.it:

• Frigoligo: $0
• wallabag.it hosted service: pricing not available in reviewed sources — check wallabag.it directly

What you’re replacing:

• Pocket (now shut down per [4]) — was free with limitations, Premium tier existed
• Instapaper — freemium, paid tier for offline access and text-to-speech
• Readwise Reader — $7.99/month

If you’re building the case for self-hosting your read-it-later setup, the math favors a $5–6 VPS plus free client apps. But that math belongs to the wallabag decision, not the Frigoligo decision. Frigoligo adds no cost to whatever wallabag setup you already have or are building.

---

Deployment Reality Check

Frigoligo has essentially zero deployment friction — it installs from standard app stores. The real deployment work is wallabag.

To use Frigoligo, you need:

1. A running wallabag instance (self-hosted or wallabag.it)
2. wallabag API credentials (client ID, client secret, username, password)
3. Frigoligo installed on your device

The login deeplink (frigoligo://x/login?server=...&clientId=...) exists specifically for scripted or automated setup, which suggests the developer has thought about configuration at scale [README].

The wallabag setup reality (from source [4]): “Setup is a bit clunky, even using the hosted service at wallabag.it.” That’s for the hosted version. Self-hosting wallabag requires a server with PHP, a database, and standard webserver configuration. It’s not Docker-Compose simple — wallabag’s self-host path is heavier than many modern Go or Python tools [4].

What can go sideways:

• Frigoligo’s experimental web app is auto-updated from the main branch — treat it as a development preview, not a production client [README]
• Translation completeness varies; some languages may be partially translated [README]
• Linux deeplink support is explicitly missing (all platforms except Linux are supported for deeplinks) [README]
• The /login deeplink prefills credentials — the README explicitly flags that sharing such a link “weakens the security of your account” [README]

If you’re already running wallabag, getting Frigoligo working is an afternoon at most. If you’re not running wallabag yet, the path is: set up wallabag (longer, separate task), then install Frigoligo (minutes).

---

Pros and Cons

Pros

• Better reading experience than the official wallabag app. The one first-hand comparison available [3] is clear: more modern design, better font control, smoother performance. If you use wallabag on mobile, this is an upgrade with zero additional cost.
• True cross-platform via Flutter. Single codebase covers Android, iOS, macOS, Linux, Windows. This is unusual — most read-it-later clients are mobile-only or have weak desktop equivalents [README].
• Standard store distribution. App Store, Google Play, F-Droid, Flathub — no sideloading, no manual APK installs required [README].
• Offline first. Articles sync to the device and work without a connection. This is the core value of any read-it-later tool and Frigoligo treats it as a first-class requirement [README].
• Deep link integration. The /save deeplink is genuinely useful for power users who want to route URLs from iOS Shortcuts, Android intents, or automation tools directly into their reading queue [README].
• MIT licensed. No license restrictions, no usage limits [README].
• Actively maintained. 42 releases, 925 commits, and community translations suggest this isn’t abandoned [README].

Cons

• Requires wallabag. This is the entire limitation. Frigoligo does nothing standalone. Non-technical founders who want a read-it-later tool can’t start here [README][3].
• Very small community. 144 GitHub stars and 8 forks is tiny. One developer appears to carry most of the project. If development stalls, there’s no large community to fork and continue it [README].
• No browser extension. Saving articles still requires wallabag’s browser extension or bookmarklet, a separate setup step [4].
• wallabag itself has rough edges. Source [4] notes the service is “not quite as good as Pocket at extracting the content of an article” and “Setup is a bit clunky.” Frigoligo inherits any of wallabag’s extraction failures at the reading stage — if wallabag parsed an article poorly, that’s what you read in Frigoligo [4].
• Linux deeplink support is absent. If your workflow depends on piping URLs in from the desktop via deeplinks, Linux is excluded [README].
• Experimental web app. The web version is explicitly unstable (auto-deployed from main branch) — not for daily use [README].
• No standalone feature set. There’s no tagging UI, no article organization, no RSS feeds, no annotation system — all of that is wallabag’s domain. Frigoligo is read-only plus archive/delete [3][README].

---

Who Should Use This / Who Shouldn’t

Use Frigoligo if:

• You already run wallabag and use the official mobile app; you find it dated or sluggish.
• You’re setting up a new wallabag stack and want the best available mobile client from day one.
• You want offline reading on multiple platforms (Android, iOS, desktop) without paying per device.
• You run automation workflows that save URLs from external tools — the /save deeplink is purpose-built for this [README].

Skip it (stay on the official wallabag app) if:

• The official app works fine for you. Frigoligo is better, but “better” may not justify learning a new tool if your current setup isn’t broken.
• You need features the official app has that Frigoligo might not yet — check the Frigoligo issues for missing features before switching.

Skip it entirely (start with a different tool) if:

• You don’t use wallabag and aren’t planning to. There’s no path to Frigoligo without wallabag.
• You’re a non-technical founder who wants a simple read-it-later setup with no servers. Start with Omnivore, Readwise Reader, or wait for a hosted wallabag.it account — then come back to Frigoligo.
• You need a browser-native reading experience; Frigoligo is a mobile/desktop app, not a browser extension [README].

---

Alternatives Worth Considering

Official wallabag Android app — the direct comparison. Exists, works, free. The [3] review prefers Frigoligo for design and font control, but if you’ve never tried the official app, start there since it’s the same install complexity.

Karakeep (formerly Hoarder) — AGPL-3.0, self-hostable bookmark + read-it-later with AI tagging and full-text search. More featureful than wallabag as a server, but no dedicated mobile client to match Frigoligo [1].

Readeck — simple, self-hosted, AGPL-3.0, focused on saving “precious readable content.” Smaller than wallabag, no dedicated mobile client [1].

Obsidian Web Clipper — MIT, clips web content directly to your Obsidian vault. Different use case (note-taking integration) but overlaps with read-it-later for long-form content [1].

Instapaper — closed-source SaaS. If you want zero setup and don’t care about self-hosting, it’s still running and the free tier covers basic use.

The realistic comparison for someone evaluating Frigoligo specifically is: Frigoligo vs. official wallabag app, not Frigoligo vs. Pocket. Get that framing right before making a decision.

---

Bottom Line

Frigoligo is a narrow, well-executed tool doing exactly one thing: giving wallabag users a better reading experience on their phones and desktops. It doesn’t try to replace wallabag or compete with Pocket directly. For the audience it targets — people already in the wallabag ecosystem — it delivers on its promise: cleaner design, better font control, smooth offline reading across every platform. The 144-star count is honest about its reach; this isn’t a project with a marketing budget or a growth team. But 42 releases and active translation management suggest a developer who ships and maintains. If you’re running wallabag and haven’t tried Frigoligo, the install cost is zero and the upside is a meaningfully better reading experience. If you’re not running wallabag yet, solve that problem first — and when you do, Frigoligo is waiting on the App Store.

---

Sources

1. AlternativeTo — Open Source Read It Later Tools (category listing). https://alternativeto.net/category/books—news/read-later/?license=opensource
2. AlternativeTo — Reminiscence: Self-Hosted Bookmark and Archive Manager (read-it-later ecosystem context). https://alternativeto.net/software/reminiscence/about/
3. opensourcemusings.com — “4 More FOSS Android Apps” (first-hand Frigoligo review). https://opensourcemusings.com/posts/android2.html
4. hyperborea.org — “Wallabag Review” (wallabag server review, context for client evaluation). https://hyperborea.org/reviews/software/wallabag/
5. androidfreeware.net — wallabag Free Download for Android (official wallabag Android app, comparison baseline). https://www.androidfreeware.net/download-wallabag-apk.html

Primary sources:

• GitHub repository and README: https://github.com/casimir/frigoligo (144 stars, MIT license)