Moe Memos

A third-party mobile companion for the memos ecosystem, honestly reviewed. No marketing fluff.

TL;DR

• What it is: A native Android (and iOS) app that connects to a self-hosted ✍️memos server — or works entirely locally on your device with no server required [1].
• Who it’s for: Privacy-conscious users who already self-host a memos instance and want a polished native mobile client, or anyone who wants quick-capture note-taking that lives entirely on their own hardware [1][2].
• Cost: Free, GPL-3.0 licensed. Available on F-Droid, Google Play, or direct APK [1]. The underlying memos server is also free and open source.
• Key strength: Offline-first with automatic sync, Material You design, no data collection of any kind, and it can run fully local with no server [1].
• Key weakness: Version compatibility is a real problem — as of this writing, Moe Memos officially supports only up to memos 0.26.2. Newer memos server versions require a separate compatibility shim called Mortis, which is a meaningful extra step [1].

---

What is Moe Memos

Before the app makes sense, you need to understand the ecosystem. ✍️memos is a self-hosted note-taking server — think of it as a private microblogging platform for your own thoughts. You post short notes to a timeline, tag them, search them, and forget you ever needed Evernote or Notion for quick captures. The server runs as a Docker container and exposes a web UI and REST API.

Moe Memos is not the server. It’s a third-party mobile client written for Android (Kotlin + Jetpack Compose) with a companion iOS/iPadOS app, both built by an independent developer [1][2]. The two projects are explicitly not affiliated [1]. The Android client has 1,041 GitHub stars. The iOS version is available through the App Store; the Android version through F-Droid, Google Play, or direct APK download.

What makes it more than just a web view wrapper: Moe Memos works fully offline and locally, with no server needed at all. You can use it as a standalone note-taking app on your device, with local storage and export, and optionally connect it later to a self-hosted memos server for sync [1]. This is the design decision that sets it apart from just opening memos in a browser on your phone.

The app is a “just for fun, no really” project — the README badge literally links to justforfunnoreally.dev. That’s worth keeping in mind when evaluating its roadmap reliability vs. commercial products.

---

Why people choose it

The third-party review data available for Moe Memos specifically is thin — the app lives in a niche corner of the self-hosting world where the developer community shares opinions in forums and comment threads rather than publishing full reviews. What the available data does tell us comes from the project’s own positioning and the memos ecosystem context.

The case for Moe Memos over alternatives comes down to three things: the native mobile experience, the offline-first architecture, and the privacy stance.

The memos server’s own web UI works in a mobile browser, but it’s not optimized for quick capture on the go. Native apps are faster to open, integrate with the share sheet (so you can share a webpage from Chrome directly into a memo), add home screen widgets, and handle the device’s back button the way Android users expect. Moe Memos provides all of this — Material You theming, dynamic color support, themed icon — while the web UI offers none of it [1].

The privacy stance is zero-compromise: no data collection, no analytics, no crash reporting that phones home. For a self-hosting user who went through the effort of running their own server specifically to avoid third-party data exposure, this is table stakes — but it’s worth naming explicitly because “no data collection” on the App Store is often a marketing line that evaporates in the privacy nutrition label. The GPL-3.0 license means the claim is auditable [1].

The offline-first architecture matters for anyone who takes notes in places with spotty connectivity — on planes, in basements, during commutes through tunnels. The app queues changes locally and syncs when back online [1]. Many note apps claim offline support and then either lose data or require a manual reconciliation step when you reconnect. The README frames this as a deliberate design priority, not an afterthought.

---

Features

Based on the README and website [1][2]:

Core note-taking:

• Write memos in a Twitter-like timeline interface — short, timestamped, scrollable
• Markdown editor and renderer
• Inline images and non-image attachments
• To-do checklist items inside memos
• Tags for organization
• Pinning for important memos
• Full-text search

Mobile-specific integrations:

• Home screen widget (quick-add from the home screen without opening the app)
• Share sheet integration — share text, images, or webpages from any app directly into Moe Memos
• Progress graph showing memo activity over time (useful if you’re using it as a daily journaling habit)

Sync and storage:

• Fully local mode with no server required; data stays on device with export
• Sync with a self-hosted memos server (via REST API)
• Offline-first: writes locally, syncs on reconnect

Design:

• Material You with dynamic theming (your wallpaper colors can drive the app palette)
• Themed icon support

What it does not have:

• No web clipper or browser extension (handled via the share sheet)
• No collaboration or sharing features — this is a personal notes tool
• No end-to-end encryption at the app layer (security depends on your server’s HTTPS setup)

---

Pricing: SaaS vs self-hosted math

Moe Memos itself costs nothing. The app is free on every distribution channel [1]. The memos server it syncs with is also free open-source software.

Your actual cost is infrastructure:

Self-hosted memos + Moe Memos:

• VPS to run the memos server: $4–8/month on Hetzner, Contabo, or Oracle (which has a permanent free tier that can run memos comfortably)
• Moe Memos app: $0
• memos server license: $0 (MIT license on the server)
• Total: $0–8/month depending on whether you already have a VPS

What you’re replacing:

Service	Monthly	Annual
Evernote Personal	$14.99	$179.88
Notion Personal Pro	$10	$120
Obsidian Sync	$10	$120
Standard Notes Productivity	$9.99	$119.88
Bear (iOS)	$2.99	$35.88

For a solo founder using Evernote or Notion primarily for quick-capture notes and daily memos, the math on self-hosted memos + Moe Memos is straightforward: $0/month on an existing VPS, or ~$5/month on a new one, versus $10–15/month for a comparable SaaS tier. Over three years that’s $360–540 saved, not counting the years Evernote spends raising prices.

The caveat is that this comparison only holds if the memos use case actually matches what you need — memos is optimized for quick, atomic captures in a timeline, not for long-form documents, wikis, or databases. If you need Notion for its database features, memos doesn’t compete there.

Data not available: specific revenue, user counts, or infrastructure cost benchmarks from independent sources for Moe Memos specifically.

---

Deployment reality check

Moe Memos the app is trivial to install — it’s on F-Droid and Google Play [1]. The deployment complexity is entirely on the server side.

If you already run a memos server: Install the app, enter your server URL and credentials, done. Five minutes.

If you don’t have a memos server yet: You need to:

1. Provision a VPS (Hetzner, DigitalOcean, or similar) — 15 minutes
2. Install Docker — 10 minutes on a fresh Ubuntu VPS
3. Run the memos Docker container with a compose file — another 10 minutes
4. Point a domain and set up HTTPS (Caddy makes this near-trivial) — 20 minutes
5. Install Moe Memos and connect — 5 minutes

Realistic total for someone who’s done Docker before: under an hour. For a first-timer following a guide: 2–4 hours including the domain and SSL setup.

The compatibility warning you need to know: Moe Memos only officially supports memos server versions 0.21.0 and 0.26.0–0.26.2. The memos project has had breaking API changes between versions, and if you’re running a newer server version (above 0.26.2), Moe Memos may not work correctly [1]. The README’s recommended fix is to deploy Mortis — a separate proxy that translates the newer memos API back to the 0.21.0 format — and then re-login in Moe Memos [1]. This is a real operational burden. It means you can’t simply update your memos server to the latest version and expect Moe Memos to keep working. You need to either pin your server version or run the Mortis shim.

What can go wrong:

• Server version drift is the most likely pain point for existing users who update their memos instance
• The app is a one-person or small-team open-source project; if the developer loses interest, updates stop
• No push notifications for sync — the app syncs when you open it or when network recovers, not in real-time background

What works well:

• The local mode means you can use the app indefinitely even if your server goes down
• F-Droid availability means you can install it without Google services on a de-Googled Android device

---

Pros and cons

Pros

• Fully local mode. No server required to use the app. Your notes can live entirely on your device, with export. This is unusual for sync-capable apps [1].
• Zero data collection. GPL-3.0 and no analytics, no crash reporting, no phone-home. Self-hosting users will appreciate this being structural, not just a policy claim [1].
• F-Droid available. De-Googled Android users can install it through F-Droid without any Google dependency [1].
• Offline-first with real sync. Notes written offline queue locally and sync automatically — not “works offline if you enabled cache mode in settings three weeks ago” [1].
• Native Android quality. Material You, dynamic themes, home screen widget, share sheet integration. These are the integrations that make a mobile app actually useful versus a responsive web wrapper [1].
• No cost. Free app, free server software, you pay only for your VPS [1][2].

Cons

• Version compatibility is fragile. Officially supports memos only up to 0.26.2. Newer server versions require the Mortis proxy workaround. This is the biggest operational risk for anyone who wants to stay current [1].
• One-person project. The README badge literally says “justforfunnoreally.dev.” Maintenance pace and longevity depend on a single developer’s continued interest. There’s no company backing it.
• No iOS/Android parity guaranteed. The GitHub repo is explicitly the Android app; the iOS app is separate and may lag in features or updates.
• No end-to-end encryption at the app layer. Security depends entirely on your server’s HTTPS configuration and network setup.
• No rich search or backlinks. If you’re used to Obsidian’s graph view or bidirectional links, memos (and by extension Moe Memos) is not that tool. It’s a timeline, not a knowledge graph.
• Small community. With 1,041 stars, this is a niche app. Bug reports may sit longer; documentation is sparse.

---

Who should use this / who shouldn’t

Use Moe Memos if:

• You already self-host a memos server (version ≤0.26.2 or willing to run Mortis) and want the best mobile experience for it.
• You’re running a de-Googled Android device and need an F-Droid-available note app with optional server sync.
• You want quick-capture notes that are fully local-first — no accounts, no cloud dependency, no subscription.
• You’re replacing Evernote or Notion specifically for the “quick thoughts” use case and you’re comfortable deploying a Docker container.

Skip it if:

• You want long-form document editing, wikis, or database views — use Obsidian, Notion, or Joplin instead.
• You need push notifications and real-time sync across devices — the sync model requires opening the app.
• Your memos server is newer than 0.26.2 and you’re not willing to deploy Mortis.
• You’re a non-technical founder with no Linux/Docker experience and no one to help with the server setup. The app is easy; the server setup is not trivial for a first-timer.
• You need iOS-first — verify the iOS app’s current maintenance status independently before committing.

---

Alternatives worth considering

For the mobile client specifically:

• memos web UI in a browser — works, but no native integrations, no widget, no offline mode.
• Memos for Android — other third-party clients exist; search F-Droid for “memos” to see the current options.

For the overall “quick-capture self-hosted notes” use case:

• ✍️memos (usememos/memos) — the server itself, which has a mobile-responsive web UI. If you’re comfortable using a browser on mobile, you may not need Moe Memos at all.
• Standard Notes — full end-to-end encryption, cross-platform native apps, self-hostable sync server, paid tiers for extensions. More polished than memos but not free for the sync server.
• Joplin — Markdown notebooks, E2E encryption, self-hostable sync (Joplin Server or via WebDAV/S3). Better for long-form notes than memos; native Android app included.
• Obsidian — local-first, no server required, extensive plugin ecosystem including self-hosted sync. No official self-hosted sync; community plugin LiveSync fills the gap. The strongest option if you want a knowledge graph rather than a timeline.
• Silverbullet — newer self-hosted wiki/notes hybrid, web-based with offline PWA support. Worth evaluating if you want something between memos and Obsidian.
• Logseq — outline-based, bidirectional links, local-first. Heavy for quick capture but powerful for structured thinking.

For a non-technical founder who just wants to escape Evernote pricing, the realistic path is either Standard Notes (easier, has commercial apps) or Joplin (more control). Moe Memos + memos server is the right choice only if you specifically want the microblogging timeline format and are comfortable with a bit of server administration.

---

Bottom line

Moe Memos is a well-built Android client for a specific niche: users who run a self-hosted memos server and want a native mobile experience that’s offline-first, zero-data-collection, and available on F-Droid. For that audience, it’s the obvious choice. The app’s quality and feature set are solid for a “just for fun” project: Material You design, widget support, share sheet integration, and genuine offline capability are things many paid apps get wrong.

The version compatibility problem is the honest blocker. If you’re keeping your memos server up to date, you will eventually hit the 0.26.2 ceiling and need to decide whether to freeze your server version or maintain the Mortis proxy. That’s a real operational cost on a tool that’s supposed to reduce friction.

For the broader audience — non-technical founders who haven’t yet set up a memos server — the question is whether the memos paradigm (Twitter-for-yourself timeline of short notes) matches how you actually think. If it does, the math is straightforward: a $5 VPS, a free app, and no subscription ever again. If you need rich documents, databases, or backlinks, look at Joplin or Obsidian instead.

If the server setup is the blocker, upready.dev deploys self-hosted tools for clients as a one-time engagement — you get the infrastructure without the afternoon of command-line work.

---

Sources

1. Moe Memos — GitHub README (Android) — mudkipme/MoeMemosAndroid. https://github.com/mudkipme/MoeMemosAndroid
2. Moe Memos — Official Website — memos.moe. https://memos.moe
3. Moe Memos — F-Droid Listing — F-Droid package me.mudkip.moememos. https://f-droid.org/packages/me.mudkip.moememos/
4. ✍️memos — Self-hosted server project — usememos/memos on GitHub. https://github.com/usememos/memos