Skip to Content
Pocket Notifier

Decision log

Every v1 design decision, whether it is settled, and where it is explained.

Decided

AreaDecisionDetails
ProductOur own ntfy-like service, not a layer on top of ntfyScope
AudienceYou plus invited users on one deploymentAccess
Sign-upInvite links only; public sign-up is offAccess
ModelProject → Feature → Notification model everywhere: database, API, push payload (version 2), app and docs. Every conversation is a feature; messages without one go to the project-level threadData model
SharingMembership per project with owner, publisher, subscriber rolesAccess
Publish authBearer access tokens, scoped to all projects or a listAccess
Token storagenotifier's own access_token table, not the better-auth api-key pluginAccess
API styleOur own API, not compatible with ntfyAPI overview
v1 featuresHTTP publish and history, phone push, action buttons, attachmentsScope
Live web viewNot in v1, so no Durable Objects yetScope
Retention30 days by default, configurable per projectRetention
ActionsOpen URL, HTTP request, reply / acknowledgePublish
PlatformAndroid first; iOS kept possibleMobile
App stackExpo + React Native with native pieces where they matterMobile
UIHeroUI Native components only, the same on both platformsMobile
Push pathThe Worker calls FCM HTTP v1 directly with data-only messagesPush delivery
App IDcom.bartuozel.pocketnotifier for the Android package and iOS bundleAndroid setup
Background receivingA small Kotlin FirebaseMessagingService in an Expo module, not a JS background taskPush delivery
ChannelsOne Android channel per priority, five in totalNotifications
GroupingNotifications stack per projectNotifications
TapOpens the message's thread: its feature, or the project-level threadNotifications
NavigationThree native tabs: Inbox, Projects, SettingsNavigation
Main use caseCoding agents in T3 Code notify when done, blocked or failingCoding agents
Agent entry pointA remote MCP server at /mcp is the primary path; agent-notify over REST stays as the fallbackMCP server
Project and featureA project is a product or repository; a feature is a workstream in it, shown as a conversation; feature status active, done, archivedMCP server
General projectNotifications without a project go to a private, per-user General project, created on first needMCP server
Feature auto-createSending to a feature that does not exist creates it from the given nameMCP server
MCP sign-inOAuth 2.1 with PKCE and dynamic client registration, from better-auth's MCP provider; sign-in and consent pages served by the WorkerMCP server
Agent layoutWith MCP each repository is a project and each feature a conversation; with REST, one agents projectCoding agents
AvatarsProject avatar with agent badge, chat-style (MessagingStyle)Notifications
Avatar sourceGenerated initials and color; an HTTPS iconUrl overridesNotifications
Answering agentsAgents can ask with a reply action; they cannot read replies through MCP yetMCP server

Open

Proposals that are written into the contract or the docs but still need a yes or no.

QuestionProposalDetails
Attachment size cap15 MB per filePublish
Secrets in HTTP actionsNot supported: HTTPS URL, method and body only, no headersPublish
Waiting for a replyNot in v1; scripts poll GET /v1/messages/{id}/responsesMessages
Publishing to a missing projectRejected with 404; projects are created in the appPublish
Project namesUnique across the whole deploymentData model
Actions per messageUp to 5; the first 3 appear on the notificationNotifications
Read syncA dismiss push clears notifications on other devices after a message is readPush payload
Rate limitsPer token: 60 messages a minute, 1,000 a dayErrors
Agent thread URLHow agents get their T3 Code thread URL for clickUrlCoding agents
Project iconsWhere real project icons come from (GitHub avatar, favicon)Coding agents
iOS pushFCM to APNs, or APNs directly, decided when iOS work startsPush delivery

Later

  • Live delivery to the web dashboard (Durable Objects and WebSocket).
  • An always-on connection for phones without Google Play services.
  • Server-side HTTP actions that can hold secrets.
  • Teams or workspaces above projects.

On this page