Linkdy

A companion app for Linkding, honestly reviewed. What it is, what it isn’t, and whether the setup is worth it.

---

TL;DR

• What it is: A Flutter-based mobile client (Android + iOS) for Linkding, the self-hosted bookmark manager. Linkdy is not a standalone service — it requires a running Linkding instance [README].
• Who it’s for: People already running Linkding who want a native mobile interface instead of using the Linkding web app in a phone browser [README].
• Cost: Free and Apache-2.0 licensed. The app itself costs nothing. The cost is the VPS to run Linkding [README][1].
• Key strength: Cross-platform Flutter app with Material You theming on Android 12+, available on both Google Play and the App Store — most open-source self-hosted clients only ship one or the other [README].
• Key weakness: It’s a client app with 165 GitHub stars and a single contributor. Linkdy is one layer on top of Linkding — if Linkding changes its API, Linkdy has to keep pace, and there’s limited community to guarantee that [README].
• Important caveat: Third-party review coverage for Linkdy specifically is sparse. Most articles about “Linkding” mobile access are actually about the Linkding web app, not this Flutter client. This review works primarily from the README and GitHub data, and draws on Linkding-ecosystem writing for context.

---

What is Linkdy

Linkdy is a Flutter mobile application that connects to a self-hosted Linkding instance. Linkding is a bookmark manager — think Pinboard or Raindrop.io, but running on your own server [1]. You install Linkding on a VPS or home server, point Linkdy at that server’s URL with your credentials, and you get a native mobile app to manage your bookmarks from your phone.

The project was created by JGeek00 and sits at 167 GitHub stars with 10 forks, 23 releases, and a latest version of v1.7.0 released March 22, 2026 [README]. It’s written almost entirely in Dart (99.1%), uses Riverpod for state management, and slang for translations — a reasonably modern Flutter stack [README].

What Linkdy is not: a bookmark syncing service, a cloud product, or a standalone app. It’s a thin client. Everything it does is against a Linkding API you’re hosting yourself. If you don’t already have Linkding running, Linkdy does nothing.

---

Why people choose it

The appeal is in the underlying tool, not the client layer. Linkding itself has a dedicated following in the self-hosting community, and the reason comes through clearly in first-hand accounts.

One blogger at noted.lol describes spending four years cycling through dashboards — Heimdall, then Homer — before switching entirely to Linkding: “Linkding made more sense to me because it’s an app for bookmarks on steroids. You can add your services and put everything into categories using a simple tagging system. The Firefox bookmarklet makes it a breeze to quickly add links.” The appeal is operational simplicity: tags over visual dashboards, fast search over maintenance-heavy config files [1].

The common thread is data ownership. People running Linkding aren’t paying Pinboard $22/year or Raindrop’s $28/year Pro tier — and more importantly, they’re not trusting a third-party service with years of curated bookmarks that could disappear behind a paywall or a shutdown announcement. The self-hosted stack stays up as long as your VPS does [1][5].

Linkdy exists because Linkding’s native mobile experience is a responsive web app, not a native app. For people who use Linkding heavily, opening a browser, navigating to their Linkding URL, and logging in gets old. Linkdy solves exactly that: saved credentials, a native interface, and a deep link into Linkding’s bookmark list from the phone’s home screen.

The Material You dynamic theming on Android 12+ is a legitimate differentiator among self-hosted bookmark clients — it’s the kind of detail that signals an author who cares about the product on Android, not just the backend [README].

---

Features

Based on the README (there are no independent feature reviews of Linkdy specifically):

Bookmark management:

• List all bookmarks from your Linkding instance [README]
• Search bookmarks [README]
• Create new bookmarks directly from the app [README]
• Create new tags [README]
• View bookmarks by tag — browse your full tag list and see what’s under each [README]

Browsing:

• Built-in browser for opening links without leaving the app [README]

UI:

• Material You dynamic theming on Android 12+ [README]
• Available on both Google Play and the App Store — cross-platform from a single Flutter codebase [README]

What’s not in the README and likely not in the app:

• No offline sync — bookmarks require a live connection to your Linkding instance
• No share-sheet integration for saving URLs from other apps (not mentioned; absence matters for a bookmark manager)
• No bulk edit or archive operations
• No Linkding v2 API features beyond basic CRUD

The feature list is short. That’s intentional — this is a mobile interface for a minimal bookmark manager, not a feature-complete Pocket replacement. The question is whether the features Linkding exposes are the ones you actually use.

---

Pricing: SaaS vs self-hosted math

Linkdy itself is free. Apache-2.0, no subscriptions, no ads, no paywalls [README].

The cost equation is entirely around Linkding — the backend Linkdy requires:

Linkding (self-hosted):

• Linkding software: free, MIT-licensed
• VPS to run it: $4–6/month on Hetzner or Contabo handles Linkding comfortably — it’s a Django app, not a resource hog
• Domain (optional): $10–12/year if you want a clean URL instead of an IP address

Commercial alternatives to the whole Linkding + Linkdy stack:

• Raindrop.io: $28/year Pro ($2.33/month) for unlimited collections, highlights, full-text search
• Pinboard: $22/year flat, no mobile app (browser-only)
• Pocket (now Faves): Included in Mozilla subscriptions; was discontinued as standalone in 2024

The math: A $5/month Hetzner VPS running Linkding costs $60/year — about the same as Raindrop Pro or more than Pinboard. Self-hosting doesn’t win on cost alone here unless you’re already running a VPS for other services (Jellyfin, Nextcloud, Vaultwarden). When you’re splitting a $6/month VPS across five self-hosted apps, Linkding’s share drops to essentially nothing [1][5].

The stronger argument isn’t cost — it’s permanence and ownership. Raindrop could raise prices or shut down; your Linkding instance doesn’t.

---

Deployment reality check

Before installing Linkdy, you need Linkding running. That’s the actual deployment work.

To get Linkding running:

• A Linux VPS or home server with Docker
• Docker Compose install is the standard path
• A domain and reverse proxy (Caddy or nginx) for HTTPS access from outside your home network
• Basic familiarity with port forwarding if you’re running it at home

The noted.lol author includes the full docker-compose snippet in their post: it’s a two-service stack (the app + a data volume), takes about 10 minutes to deploy, and requires a manual docker exec command to create the first admin user [1].

To set up Linkdy after that:

• Download from Google Play or the App Store [README]
• Enter your Linkding instance URL and credentials
• Done

There’s no server-side config needed for Linkdy specifically. The client is stateless from the server’s perspective — it’s just calling Linkding’s REST API.

Where things can go wrong:

• HTTPS is required for the mobile app to connect. If your Linkding instance is HTTP-only or has an invalid certificate, Linkdy won’t connect.
• If your Linkding instance is on a local network (no external domain), Linkdy only works on that network or over VPN.
• The app is a one-person project. There’s no SLA, no issue response guarantee, and no funded team to handle an API-breaking change in a future Linkding update.
• Android 12+ is required for the Material You theming feature. Older Android versions should work for core functionality but the dynamic theming won’t apply [README].

Realistic setup time for someone technically comfortable: 15–30 minutes for Linkding from scratch, 5 minutes for Linkdy. For someone following a guide with no prior Docker experience: 2–3 hours for Linkding, then Linkdy is trivial.

---

Pros and Cons

Pros

• Free and Apache-2.0. No license complexity, no commercial tier, no surprises [README].
• Available on both app stores. Most self-hosted mobile clients are Android-only APKs. Linkdy ships to both Google Play and the App Store, which matters if you have users on iOS [README].
• Material You theming. Integrates with Android 12+ dynamic color, which means it picks up your wallpaper’s color palette. A small thing, but shows care for the platform [README].
• Actively maintained. 23 releases as of this review, with v1.7.0 landing March 22, 2026 — not abandoned [README].
• Zero recurring cost once Linkding is deployed [README].

Cons

• Single-contributor project with 165 stars. The bus factor is 1. If the author moves on, you’re maintaining the fork or switching clients [README].
• No share-sheet integration documented. Saving a URL you found in Safari or Chrome directly to Linkding via the share menu isn’t mentioned in the README — a significant omission for a bookmark manager [README].
• Requires Linkding already running. This isn’t a “install one app and go” tool. It’s a second installation step on top of an already non-trivial setup [README].
• No third-party review coverage. Every major review we found of “Linkding mobile” is either about the web interface or doesn’t mention Linkdy at all. There’s no sustained community feedback loop.
• Feature surface is minimal. No offline mode, no bulk operations, no read-later workflow beyond what Linkding’s own schema supports.
• Source [3] note: Search results for “Linkdy” surface articles about “Lindy AI” (an unrelated AI automation platform). This name confusion is a real discoverability problem and worth knowing before you search for support answers.

---

Who should use this / who shouldn’t

Use Linkdy if:

• You already run Linkding and you want a native mobile interface for it instead of a browser tab.
• You’re on Android 12+ and care about Material You integration.
• You need iOS and Android support from a single client.
• You’re comfortable with the risk profile of a one-person open-source project.

Skip it if:

• You don’t already have Linkding running — solve the Linkding deployment first, then revisit.
• You need a share-sheet integration (saving links from other apps mid-browsing) as your primary workflow — verify this works before committing.
• You’re evaluating a bookmark manager for a team where reliability and support matter — Linkdy is not that product.
• You want a standalone bookmark manager — try Linkding’s web interface directly, or consider Raindrop.io if self-hosting is too much friction.

---

Alternatives worth considering

For Linkding mobile access specifically:

• Linkding web app on mobile — the fallback. Linkding’s web interface is responsive and works in a mobile browser. Less convenient, but zero additional setup and zero dependency on Linkdy staying maintained.
• Shiori — a different self-hosted bookmark manager with its own Android client. More opinionated about archiving full page content.

If you’re reconsidering the whole stack:

• Raindrop.io — the polished commercial option. $28/year Pro, solid iOS and Android apps, full-text search, highlights. If the self-hosting overhead isn’t worth it to you, Raindrop is the honest alternative.
• Omnivore — open-source read-later service (MIT). More focused on article saving and reading than pure bookmarking. Has a proper cross-platform mobile app.
• Wallabag — self-hosted read-later, similar to Pocket. More feature-complete than Linkding for long-form reading, with a dedicated mobile app.

---

Bottom line

Linkdy is a straightforward tool that does one thing: gives Linkding a native mobile interface. If you’re already running Linkding and finding yourself opening a browser to access it on your phone, Linkdy solves that problem cleanly — it’s on both app stores, it’s actively maintained, and it integrates with Android’s Material You system on modern hardware. The trade-off is the single-contributor project risk and the notable absence of share-sheet integration in the documented feature set, which is a real gap for a bookmarking app.

If you’re not already running Linkding, Linkdy isn’t the entry point to evaluate. Start with Linkding itself; the self-hosting community around it is significantly larger and better documented. Once Linkding is running and you find yourself wanting a native app instead of a mobile browser tab, Linkdy is the obvious first download.

---

Sources

1. noted.lol — “LinkDing - Why I Gave Up Fancy Dashboards For A Simple Bookmark Application”. https://noted.lol/linkding-why-i-gave-up-fancy-dashboards-for-a-simple-bookmark-application/
2. Ismar Hrnjicevic, How-To Geek — “These 5 apps proved to me that self-hosting was worth the effort” (Apr 16, 2026). https://www.howtogeek.com/im-new-to-self-hosting-these-are-the-apps-that-changed-everything-for-me/

Primary sources:

• GitHub repository and README: https://github.com/JGeek00/linkdy (167 stars, Apache-2.0 license, 23 releases)
• Google Play listing: https://play.google.com/store/apps/details?id=com.jgeek00.linkdy
• App Store listing: https://apps.apple.com/us/app/linkdy/id6479930976