Sharing an offline-first Android client I built for Memos — MemoFlow

[hzc073]

MemoFlow

MemoFlow is an open-source Android client for Memos, designed for people who love lightweight, self-hosted note-taking and personal knowledge recording.

It brings the power of the Memos ecosystem to mobile devices while adding additional productivity and AI-assisted features.

✨ Key Features

• 📱 Native Android experience for the Memos platform
• 🤖 AI-powered summaries to quickly review your notes and activity
• 📊 Statistics and insights to help you understand your writing habits
• 🎲 Random walk browsing to rediscover past memos
• 🔒 Privacy-first: works with your self-hosted Memos server
• 🔐 App lock support to protect your personal notes
• ☁️ Encrypted WebDAV backup for secure data synchronization
• 🔄 Supports multiple Memos API versions (0.21–0.26)
• 🎤 Voice notes for quickly capturing ideas
• 🖼 Media browsing for photos, videos, and attachments
• ⚡ Fast and lightweight design focused on daily use ⚡ Fast and lightweight design focused on daily use

🎯 Why MemoFlow?

The official Memos project focuses on the backend and web interface.
MemoFlow aims to provide a smooth and modern mobile experience for Memos users who prefer capturing thoughts anytime, anywhere.

GitHub:
https://github.com/hzc073/memoflow

[HarryBMa]

It doesn't work with newest server version. V0.26.2

[hzc073]

Thanks for the feedback. MemoFlow does support v0.26.2, and I’ve already handled a compatibility issue related to 0.26.x before.

Could you share more details about what exactly is not working?
For example: sync failure, memo creation issue, timestamp issue, login problem, etc.

If possible, please also include:

• exact Memos version
• database type
• error message or screenshot

That will help me troubleshoot it more accurately.

[HarryBMa]

Memos server is v0.26.2
Memoflow drop-down in server mode only allows v0.26.0

Connection failed: DioException [unknown]: null Error: HandshakeException: Handshake error in client (OS

WRONG_VERSION_NUMBER(tls_record.cc:127))

[hzc073]

Thanks for the report!

This may not be caused by Memos v0.26.2 itself. If the error is a handshake failure, it could also be due to HTTP/HTTPS mismatch, TLS certificate issues, or reverse proxy configuration.

If possible, please share:

• whether your server is HTTP or HTTPS
• whether login fails directly
• any error message / screenshot

That will help me determine whether this is a connection issue or a real API compatibility issue.

[hzc073]

Also, please try tapping the shield icon on the right side of the server address field to switch between HTTP and HTTPS, in case the issue is caused by a protocol mismatch.

[HarryBMa]

I thought I tried that but that was it. It was a protocol mismatch.

…

On Thu, 19 Mar 2026, 05:25 hzc073, ***@***.***> wrote: Also, please try tapping the shield icon on the right side of the server address field to switch between HTTP and HTTPS, in case the issue is caused by a protocol mismatch. — Reply to this email directly, view it on GitHub <#5698 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BG65KOJ47SRP4ZT6E45GGC34RNZB3AVCNFSM6AAAAACWKIYZZKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMMRQGIYTEMI> . You are receiving this because you commented.Message ID: ***@***.***>

[hzc073]

Glad to hear it’s working now
I’ve added a retry option for HTTP after the first failed attempt, which should make this kind of protocol mismatch easier to handle.
Hope you enjoy using MemoFlow!