An unofficial Android companion for Mealie, honestly reviewed. Archived since late 2024, but the context matters.

TL;DR

What it is: An unofficial Android client for Mealie, the self-hosted recipe manager. Mealient lets you browse, create, and manage Mealie recipes and shopping lists from your phone with offline access [README].
Who it’s for: Android users already running a Mealie instance who want a native mobile experience instead of the browser UI.
Critical caveat: Mealient is officially deprecated and no longer maintained. The repository was archived by its author on November 9, 2024. The last release (v0.4.8) shipped August 4, 2024. You can still install and run it, but there will be no more updates [README].
Key strength: Offline-first recipe access — recipe data is cached locally so you can follow a recipe in the kitchen without an active network connection [README].
Key weakness: Archived. Dead. The author explicitly says: “This project is no longer maintained, so feel free to fork and develop it independently.” One direct comparison review calls it “a bit clunky” versus the competing Tandoor app’s mobile client [4].
Stars: 167 on GitHub, 22 forks.
License: MIT.

What is Mealient

Mealient is not Mealie. This is the first thing to understand, because the data is easy to conflate.

Mealie is the self-hosted recipe management server — the thing you deploy on a VPS, the thing that scrapes recipes from URLs, runs the meal planner, and serves the web UI [1][3]. It has 6,000+ GitHub stars, is actively maintained, and is what most third-party articles are actually reviewing when they say “Mealie” [1][5].

Mealient is a community-built, unofficial Android app that connects to a Mealie instance you’re already running. It’s a client, not the product. The relationship is the same as a third-party Twitter app connecting to Twitter’s API — except in this case, the “Twitter” (Mealie) is alive and thriving, while the Android client went dark.

What Mealient specifically offered, per its README and feature history [README]:

Browse your Mealie recipe library from a native Android app
View full recipe details, including ingredients and instructions
Create new recipes on the device
View and modify shopping lists
Offline-first design: recipe data is stored locally and doesn’t require an internet connection to read

It shipped via Google Play and F-Droid, which is a meaningful signal — F-Droid inclusion means the app was fully open source with no proprietary dependencies [README]. For users running a private Mealie instance behind a VPN with no public internet exposure, F-Droid was the only viable distribution channel.

The project reached 37 releases over its active lifetime before going quiet [website_body]. That’s a substantial commit history — 916 commits, a multi-module Kotlin architecture (separate modules for datasource, database, datastore, model_mapper, UI) — this wasn’t a weekend prototype [website_body].

Why people choose it over the Mealie web UI

The two reasons anyone bothers with a native Android app over Mealie’s web interface:

Offline access. Mealie’s web app requires a network connection. If your instance is on a home server and you take your phone into a basement kitchen with spotty Wi-Fi, the web app may not load. Mealient solves this by caching recipe data locally [README]. Several self-hosters specifically cite this as the reason to bother with a dedicated app — you don’t want to be 45 minutes into cooking, hands covered in flour, and have your recipe UI go blank because the VPN dropped.

Native Android feel. Mealie’s web app is responsive and polished [1][5], but it’s still a browser-rendered web app. A native app handles back button behavior, Android intent sharing, system font scaling, and multitasking more naturally on Android. For users on older or slower Android devices, the difference in rendering performance is real.

That said, one reviewer who compared Mealient directly against the competing Tandoor ecosystem’s mobile app (Kitshn) was blunt: “While Mealie has a community-made Mealient app, it’s nowhere near Tandoor’s unofficial app called Kitshn. Kitshn is developed using Jetpack Compose and Material You, which gives a clean, responsive, and aesthetically pleasing interface… In comparison, I often found Mealient to be a bit clunky.” [4]

The Mealie web UI itself wins high praise — “a polished and intuitive user interface”, “rare in the open-source world”, “animations are smooth” [1][5]. The gap between Mealie’s web experience and Mealient’s native app was apparently not large enough to justify the maintenance burden.

Features

What Mealient delivered at its final version (v0.4.8):

Recipe browsing:

List view of all recipes in your Mealie instance
Per-recipe detail view: ingredients, instructions, metadata [README]
Local caching for offline reads [README]

Recipe creation:

Manual recipe entry directly from the app [README]
Note: URL import (Mealie’s signature one-click scraping feature) was partially or not available in the app — the README describes this as a “very early alpha which supports a small subset of the Mealie capabilities” [README]

Shopping lists:

Full shopping list browsing [README]
Modify items in shopping lists from the app [README]

Internationalization:

Crowdin-hosted translation workflow (Crowdin badge in README indicates community translations were active) [README]

What it did NOT have at archive time:

Meal planning (the weekly calendar drag-and-drop feature that reviewers praise in Mealie’s web UI) [1][README]
Full recipe URL import — Mealie’s recipe scraper, NLP parsing, and ChatGPT fallback are all server-side features, but the Android client doesn’t appear to have exposed the URL import flow [5][README]
The “cookbooks” organizational feature in Mealie [1]
Group/multi-user account management [README]

This is a meaningful gap. Mealie’s headline features are its recipe scraper and meal planner [1][3][5]. The mobile app was primarily a reader and shopping list manager, with basic recipe creation — not a full Mealie experience on glass.

Pricing: SaaS vs self-hosted math

Mealient itself is free software (MIT). But since it’s a client app, the pricing conversation is really about Mealie (the server):

Mealie self-hosted:

Software: free, MIT-licensed [README of Mealie]
Hosting: $5–20/month on a VPS (Hetzner, Contabo, DigitalOcean)
This is the only path that makes Mealient relevant — you have to be running a Mealie instance first

Mealie managed hosting (Elestio):

Starting at $14/month, includes automated backups, SSL, updates, and monitoring [2]
Elestio rates 4.6/5 on Trustpilot, 4.8/5 on G2 [2]

Competing apps (what you’re replacing):

Paprika 3: $4.99 one-time on Android, $29.99 on Mac, $19.99 on iOS — no self-hosting, no open source, data stays in their cloud [3]
Plan to Eat: $6.99/month or $69.99/year — subscription, closed source, SaaS [3]

The honest math: If you’re already self-hosting Mealie on a $6 VPS, the total monthly cost of “Mealie + Mealient” is $6/month versus $7/month for Paprika subscription or $70/year for Plan to Eat. The savings are real, but the utility gap is also real — Paprika and Plan to Eat are actively maintained, Mealient is not.

Deployment reality check

Installing Mealient is a three-click operation — Google Play, F-Droid, or download the APK from the GitHub releases page [README]. There’s no server-side setup specific to Mealient. You point it at your Mealie instance URL and authenticate.

The prerequisite is Mealie itself. If you don’t have a running Mealie instance, Mealient is useless. Setting up Mealie is a Docker Compose deployment — manageable for someone comfortable with a terminal, but not a five-minute job if you’re starting from scratch [1][3].

What can go wrong:

Mealient was built against specific Mealie API versions. As Mealie continues to update its API (the project is actively developed), there is an increasing chance that future Mealie versions will break Mealient in ways that will never be fixed [README].
The README itself warns the project is in “very early alpha” status at archive time [README]. This means the app was already limited before it was abandoned — it was never feature-complete.
Since the project is archived, bug reports go unanswered. If you hit a crash on your specific Android version or Mealie version, you’re on your own or forking [README].

Realistic expectation: If you install Mealient today against a recent Mealie instance, it may work fine for basic recipe browsing and shopping list management. It may also have auth or API compatibility issues depending on which Mealie version you’re running. There are no guarantees and no support path.

Pros and Cons

Pros

Offline-first architecture. Local caching of recipe data means you can cook from your phone without a network connection — the one feature the Mealie web app can’t match [README].
F-Droid distribution. Fully open-source, no proprietary components, available through F-Droid for privacy-conscious users who avoid Google Play [README].
MIT license. Anyone can fork and continue development — the author explicitly invites this [README].
Well-structured codebase. Multi-module Kotlin architecture, 916 commits, Jetpack patterns — not the kind of project that’s trivially hard to fork and maintain [website_body].
Shopping list editing. The one feature beyond read-only that Mealient delivered, and for meal-prep workflows it’s genuinely useful [README].
Free. Mealient costs nothing, and Mealie costs nothing beyond hosting [README].

Cons

Archived and unmaintained. This is not a minor caveat — it’s the headline. The project is dead. [README]
Called out as clunky. The one direct head-to-head comparison with another self-hosted recipe app’s mobile client rated Mealient lower on UX quality [4].
Missing Mealie’s signature features. No URL recipe import, no meal planner, no cookbook organization in the app — the features that make Mealie worth setting up in the first place are not in Mealient [1][README].
API compatibility risk. As Mealie evolves its API, an unmaintained client will drift toward incompatibility with no fix path [README].
“Very early alpha” at archive. The project was explicitly described as early alpha when it stopped being developed — it wasn’t feature-complete when it was abandoned [README].
No iOS version. If your team or family has a mix of Android and iPhone users, Mealient only covers half the devices [README].

Who should use this / who shouldn’t

Use Mealient if:

You’re already on Mealie, your Mealie instance is on a version that Mealient supports, and you primarily need offline recipe reading and shopping list access.
You’re comfortable with the possibility of breakage as Mealie updates, and you’re willing to either fork or live with whatever version you have.
You’re a developer who wants to fork and maintain a Mealie Android client — the codebase is a reasonable starting point and the MIT license is clear [README].

Skip it (use Mealie’s web app instead) if:

You have reliable Wi-Fi or a VPN on your phone when cooking. The web app is polished and well-reviewed [1][5] — if offline access isn’t your blocker, there’s no reason to add the complexity of a separate app.
You want the full Mealie feature set on mobile. The web app gives you URL import, meal planning, cookbooks, and everything else. Mealient gives you a subset [1][README].

Skip it (use a different tool) if:

You’re evaluating mobile recipe management from scratch and haven’t committed to Mealie yet. Look at Tandoor + Kitshn, which a reviewer explicitly prefers over Mealie + Mealient [4].
You need a supported, maintained mobile app. No version of “it was working last year” is a substitute for active maintenance in mobile software.
You have iPhone users in the household [README].

Alternatives worth considering

Mealie web app (browser on Android): The obvious alternative that requires no additional installation. Mealie’s web UI is repeatedly praised for its quality [1][5]. Unless offline access is a hard requirement, the web app is the more reliable path.

Kitshn (for Tandoor users): The Tandoor recipe server’s unofficial Android client, built with Jetpack Compose and Material You. One reviewer who switched from Mealie to Tandoor specifically cited Kitshn’s superiority over Mealient as part of the decision [4]. If you’re evaluating which self-hosted recipe server to run, the mobile app ecosystem is worth factoring in.

Tandoor Recipes: The alternative self-hosted recipe server worth benchmarking against Mealie. One reviewer who used Mealie for years switched to Tandoor and hasn’t looked back — citing better UX for manual recipe entry, more flexible import (including direct Mealie migration), and the Kitshn mobile app [4].

Nextcloud Cookbook: If you already run Nextcloud, it’s a built-in plugin. One reviewer tried it, found Mealie’s recipe parsing dramatically superior, and switched back [5]. It integrates with your existing Nextcloud file system but its UI is basic.

Paprika 3: The commercial comparison. $4.99 one-time on Android, full-featured, actively maintained. Not open source, not self-hosted, but it works and doesn’t require server management [3]. If the appeal of Mealie is the features rather than the self-hosting philosophy, Paprika is a clean alternative.

Plan to Eat: SaaS, $6.99/month. Meal planning focused, solid import, no self-hosting. If you don’t care about data sovereignty, it’s a viable option [3].

Bottom line

Mealient was a decent starting point for a problem that genuinely needs solving: Mealie is excellent self-hosted software, but its mobile story relies entirely on the browser. An offline-capable native Android client makes real sense for kitchen use. Mealient had the right idea and got further than most hobby projects do — 37 releases, 167 stars, F-Droid distribution, a solid multi-module Kotlin codebase.

But it’s archived. The author archived it in November 2024, and the last release was four months before that. If you install it today, you’re installing software that will never be fixed, against a Mealie server that keeps getting updated. The gap will only widen.

If you want Mealie on your phone, use the web app. If you want a native app experience badly enough that you’re willing to maintain a fork, the MIT license and the codebase are there for you. If you’re still evaluating which self-hosted recipe server to run, compare Tandoor + Kitshn alongside Mealie before committing.

Sources

Parth Shah, XDA Developers — “I use this open-source self-hosted app to manage my kitchen like a pro” (Sep 3, 2025). https://www.xda-developers.com/open-source-app-to-manage-kitchen/
Elestio — “Managed Mealie as a Service”. https://elest.io/open-source/mealie
OctaByte Blog — “Mealie: The Ultimate Open-Source Recipe Management App”. https://blog.octabyte.io/posts/applications/mealie/mealie-the-ultimate-open-source-recipe-management-app/
Parth Shah, XDA Developers — “I replaced Mealie with this open-source recipe management tool and couldn’t be happier” (Sep 16, 2025). https://www.xda-developers.com/reasons-tandoor-replaced-mealie-for-managing-my-recipes/
Adam Conway, XDA Developers — “I tried Nextcloud Cookbook, but Mealie is just so much better for tracking my recipes” (Apr 5, 2025). https://www.xda-developers.com/tried-nextcloud-cookbook-mealie-much-better/