Skip to content

Meiso

Minimalist task management app built on the Nostr protocol. Inspired by TeuxDeux's clean design, it provides a simple three-column layout (Today/Tomorrow/Someday) with end-to-end NIP-44 encryption — for your own tasks and, now, for lists you share with others.

Meiso is a minimalist task management app built on the Nostr protocol. Inspired by TeuxDeux's clean design, it provides a simple three-column layout (Today/Tomorrow/Someday) with end-to-end NIP-44 encryption — for your own tasks and, now, for lists you share with others.

Features

  • Three-column task layout (Today/Tomorrow/Someday)
  • Shared collaborative lists: invite people and edit a list together in real time, end-to-end encrypted so relays only ever see ciphertext
  • Collaborator attribution: see who added or edited each shared task
  • Comments on tasks: discuss a task with the people you share a list with, or keep notes on your own tasks that sync across devices, end-to-end encrypted
  • Recurring tasks (daily, weekly, monthly, yearly)
  • Personal custom lists for organization
  • Multi-device synchronization via Nostr relays
  • NIP-44 end-to-end encryption for privacy
  • Amber signer integration for secure key management
  • Tor connection support via Orbot proxy
  • Material 3 design with light & dark mode
  • Multi-language support (English, Japanese, Spanish)
  • Pull-to-refresh sync
  • Drag and drop task reordering

All your tasks are encrypted and synced across devices using Nostr relays, ensuring both privacy and accessibility without any central server.

Summary generated by Zapstore from source.

Original description, as the developer published it.

Latest release

Oct 10, 2026

Claimed app Google servicesSource available · MIT

Includes Google Play services and Firebase components. Uses the camera to scan QR codes for adding collaborators.

Permissions

  • Camera CAMERA Take photos and record video To scan QR codes.
  • Notifications POST_NOTIFICATIONS Send you notifications
  • Always running REQUEST_IGNORE_BATTERY_OPTIMIZATIONS Keep running in the background without limits

Release notes

Added

  • Comments on tasks. Every task now has a COMMENTS thread below SUBTASKS: write a comment, long-press your own to edit or delete it, with an "edited" marker and the author's display name next to their npub. On a shared list it is a conversation with the people you share the list with; on your own tasks it is a notes field that syncs across your devices. Works in secret-key mode and with Amber. Each comment is a separate NIP-44-encrypted addressable event (kind:35002) signed by the list's group key or by your own key, and carries no tag referencing the task, so relays cannot see which task a comment belongs to or how many comments a task has. Deleting a comment republishes an empty tombstone, which replaces the text on the relays. Logging out erases the local comment store. (#157, #159, #160, #161, #163, #164, #165)

    Comments were built in the 1.4.1, 1.4.2 and 1.4.3 trees. None of the three was published to Zapstore, so 1.5.0 is the release that actually brings them to you.

  • A one-time dismissible card on the home screen, shown once (to new installs and updates alike) to anyone who has never authored a comment, explaining that tasks can now have comments and that relays never learn which task a comment belongs to. Not shown to anyone who has already authored a comment (including one synced in from another device). (#219 §6)

  • Unread comments are visible without opening a task. A task tile shows a quiet speech-bubble icon with the comment count once a thread exists, and switches to a filled bubble with the unread count once someone else's comment in it has not been read. The TODAY segment picks up a plain dot (no number) while any day has an unread thread, and SOMEDAY picks one up while any list — or a task with neither a date nor a list — does; a day tab shows a dot for that day, a SOMEDAY or shared list row for that list, and a planning row (THIS WEEK, NEXT MONTH, …) for any unread day inside its range. Opening a thread clears its unread mark immediately on your device, including comments that arrive while you're still looking at it. Screen readers announce the badge as "N unread comments" and the dot as "Unread comments". (#219)

  • A "N new comments" strip when you come back to the app. On launch, and whenever you return to the app, a strip appears above the date pages if other people's comments arrived while you were away. Tapping it opens a "New comments" list: every task with something unread, newest arrival first, each row showing who wrote the latest comment and the start of it. Opening a task from that list is what marks it read; looking at the list does not, and neither does closing the strip, which hides it only until the next time you come back. A "Mark all read" action clears the slate without opening anything. The count is taken once when you return, so it does not shift under your finger while you work. (#219 §2)

Also new since 1.4.0

Everything from 1.4.1 through 1.4.3 is in this build. If you are updating from the Zapstore listing, these are new to you as well:

  • Task-loss protection for synced lists. Publishing waits for at least one successful relay fetch in the session, refuses to publish a list that shrank below half of its last relay-confirmed size unless you run a manual sync, and keeps a change queued rather than reporting success when a send reaches no relay. (1.4.1)
  • Emptying a list reaches your other devices. Deleting the last task in a list was never sent, so the task stayed on every other device. (1.4.2, #182)
  • Tasks are no longer deleted because a sync was incomplete. An interrupted or partial fetch used to remove real tasks. A list that did not arrive at all is now left alone. (1.4.2, #182)
  • Your relay settings are used at startup. A cold start fell back to the built-in public relays even though your own relay was saved, then overwrote your settings with the list it read from those public relays. This is why data could look missing after a reinstall: the app was asking the wrong relays. (1.4.2, #197)
  • Settings screens are readable in dark mode, Secret Key Management is fully translated, and a missing translation now fails the build instead of silently falling back to English. (1.4.2, #183, #189)
  • Comments reach the relays even after a brief network problem. When the app reconnected to a relay it closed the old connection and immediately opened a new one. The library underneath treats that as a shutdown, so the relay stayed dead for the rest of the session. Anything written afterwards, comments in particular, was accepted by the screen, reached no relay at all, and was gone on the next start. The reconnect now waits for the connection to actually come back, and reports how many relays it reached. (1.4.3, #188, #214)
  • A comment that reaches no relay is retried instead of being dropped. Sends that fail are queued locally and flushed on the next connection, so a comment written while offline survives. The queue is erased on logout. (1.4.3, #201, #212)
  • Sending reconnects first when the connection is known to be down, rate-limited so that flushing a backlog pays for one reconnect rather than one per message. (1.4.3, #215)
  • The relay status row says what actually happened. Tapping reconnect used to look identical whether every relay came back, none of them did, or nothing was attempted. It now reports the number of relays reconnected, says so plainly when none could be reached, and stays silent when there was nothing to do. (1.4.3, #215)
  • The Notifications settings entry no longer appears in release builds. The screen is unfinished UI with no service behind it, so its switches did nothing. It stays available in debug builds and will return together with the notification service. (1.4.3, #201, #210)

Full lists: v1.4.1, v1.4.2, v1.4.3.

Comments

Loading comments…

See more

Get Meiso the private way

Updates checked on your device, and every release verified before it installs.