NoteGuildCraft the note graph
Sign inCreate account
NoteGuildOne note graph, multiple release surfaces.
Release surfaces

One product. Three surfaces. One shared identity.

NoteGuild is structured as a desktop-first writing workspace with mobile clients for feed, groups, and messages. The web app remains the full product surface, while iPhone and Android focus on fast social interaction.

Desktop webiPhoneAndroid
Create accountExplore thought groupsPrivacy
Launch posture

Release web first, then ship the social loop on mobile.

Desktop is the source workspace

Author notes, upload files, moderate content, manage groups, and operate the graph from the full web app.

Mobile keeps the network active

Users check the feed, join thought groups, follow messages, and stay engaged away from the desktop.

One backend, shared policy surface

Next.js, Postgres, Prisma, MinIO, and the worker remain the common backend for every client.

Desktop web

Full workspace

Next.js desktop surface for writing, editing, uploads, moderation, analytics, and administration.

Primary authoringModerationAdmin ops
Open web app
iPhone

Feed, groups, messages

Expo-powered native client using token auth and mobile API routes for social activity on iOS.

Expo appBearer authTestFlight next
TestFlight path
Android

Same client, Android build

Shared Expo codebase for Play internal testing, social browsing, group flows, and inbox behavior.

Play internal testSame APIShared release flow
Play Console path
Surface boundaries

What each client is built to do

Desktop web responsibilities

Long-form authoring, markdown and file uploads, publication controls, moderation, and graph exploration.

Mobile responsibilities

Fast account creation, feed refresh, group join/create flows, inbox access, and lightweight social actions.

Next release steps

What still needs to happen before launch

1
Stabilize staging with real domains and TLS

Run the web app, worker, Postgres, MinIO, SMTP, health checks, and backups under staging first.

2
Test native flows on real iPhone and Android devices

Verify sign-up, sign-in, feed, thought group creation, join requests, and message refresh against staging.

3
Prepare store metadata and compliance answers

Finalize screenshots, age rating, privacy disclosures, support URLs, and account-deletion support.

4
Launch in phases

Desktop private beta, then TestFlight/Play internal, then invite-only release, then public launch after moderation and crash signals are stable.