chat-globe is a consumer social application for chatting with people from across the globe. Its product intent is twofold and inseparable: it must let a person start and hold real two-way conversations with other people located elsewhere in the world, and it must present that experience through graphics that are genuinely unique — a generative, motion-first visual identity rather than a styled chat template.
The audience is globally curious people: students, remote workers, language learners, and night-owl insomniacs who want a stranger in another timezone. The emotional register is playful discovery and wonder, not utility or enterprise trust. The single hard constraint stated by the user — "this app will have a very unique graphics" — is treated as a mandate for procedural, cursor-reactive visuals that no competitor can screenshot-and-copy.
This document defines the current delivery: a first-party web application with application-owned identity, six pages, two accepted human personas, and a procedural visual system built on a wireframe globe, kinetic typography, and generative avatar sigils.
chat-globe is delivered as a custom first-party web application with a backend service. The current scope contains:
Narrow exclusions. This document does not define group conversations, media attachments, voice or video calling, contact import, social feeds, or moderation tooling; none were accepted by the source. The visual system excludes blue and indigo entirely, photography and illustrated characters, gradient-blob heroes, glassmorphism, soft-shadow hover-lift cards, centred SaaS hero composition, autoplay motion the user cannot interrupt, large soft radii, and emoji-heavy copy.
Delivery ownership. chat-globe is a first-party application. The application owns its own identity: a person establishes an account through self-service enrollment on Sign Up, and a returning person verifies identity on Login. Landing, Sign Up, and Login are reachable without an established session; People, Chats, and Chat require a verified session because they carry durable, person-specific conversation state that must remain bound to the correct participant. There is no provider-owned or external-only surface in the current scope, and no headless delivery mode.
Current boundary. Everything described in Sections 2c, 3, and 5 is current. The two-way conversation lifecycle — discover a person, open a chat, send a message, have the other person read and reply, return later to continue — is complete within the six pages.
Future boundary. Nothing beyond the current scope is committed. Ideas that were not accepted by the source (group chats, media sharing, calling, feeds, moderation) are not planned work and are not represented in any page, requirement, or flow.
Access boundary. Identity establishment is anonymous at its entry: a person reaches Landing, then Sign Up or Login, without a session. A protected destination never owns the interaction that establishes access to itself. Once identity is verified, the session persists so that conversations and messages remain attached to the right person across visits.
Not applicable. No reference directive in this project declares a content_source, so no verified factual inventory is carried into this document.
FR-1 — Chat with people from across the globe (explicit) As a Global Chatter, I should be able to hold a two-way conversation with a person located elsewhere in the world, so that I actually talk to someone across the globe.
FR-2 — Very unique graphics (explicit) As a Global Chatter, I should experience the app through graphics that are genuinely unique, so that the product feels unlike any other chat app.
FR-3 — Self-service enrollment (required_inference) As a Global Chatter, I should be able to enroll myself before creating or entering durable chats, so that my conversations belong to me.
FR-4 — Returning verification (required_inference) As a Global Chatter, I should be able to verify my identity when I return, so that I can continue my conversations and messages.
FR-5 — Discover people elsewhere in the world (required_inference) As a Global Chatter, I should be able to see other people located elsewhere in the world and choose one, so that I can start a conversation with someone new.
FR-6 — Revisit ongoing conversations (required_inference) As a Global Chatter, I should be able to see my ongoing conversations in one place and reopen any of them, so that I can continue where I left off.
FR-7 — Read and reply as the Conversation Partner (required_inference) As a Conversation Partner, I should be able to read an incoming message and reply to it, so that the exchange is genuinely two-way.
FR-8 — Send feedback along the meridian (required_inference) As a Global Chatter, I should see my send acknowledged in the thread's own visual language, so that I know the message left me.
Product context. The Global Chatter is a globally curious person — a student, remote worker, language learner, or night-owl insomniac — who wants a stranger in another timezone to talk to. They arrive at chat-globe without an account and without a specific person in mind. Their interest is discovery first and conversation second: the appeal is that the world is populated and reachable right now.
Primary goal. To start and hold real conversations with people in other parts of the world, and to come back to those conversations later.
Distinct accepted responsibilities. The Global Chatter is the initiator in this product. They enroll themselves on Sign Up, verify on return at Login, browse the People grid to choose someone, open or reopen a conversation from Chats, and compose and send messages in Chat. They are the actor who decides who to talk to and when to begin.
Relevant inputs and decisions. Their handle and credential at enrollment and return; their pointer movement across the People grid, which is itself the selection instrument; their choice of which conversation row to reopen; and the message text they compose and commit with the send pill.
Interactions with other accepted participants. Every action the Global Chatter takes is aimed at a Conversation Partner somewhere else in the world. The Global Chatter's send is only half of the exchange — the outcome they care about depends on the Conversation Partner reading and replying.
Observable success. A conversation exists in Chats with a real reply in it, and the Global Chatter can leave and come back to find it still there.
Product context. The Conversation Partner is the counterpart human in the exchange — also a globally curious person, also a chat-globe user, but arriving at a conversation that someone else started. Their context is reactive rather than initiatory: a message is waiting, or arrives while they are present.
Primary goal. To read what someone in another part of the world wrote and answer them, so that the exchange is genuinely two-way rather than one-sided.
Distinct accepted responsibilities. The Conversation Partner reads incoming messages in Chat, replies in the same thread, and returns to Chats to find conversations that have moved. They also carry the same enrollment and returning-verification responsibilities as any user, because their replies must remain attached to them across visits.
Relevant inputs and decisions. The incoming message content; the decision of whether and how to reply; the reply text they compose and send.
Interactions with other accepted participants. The Conversation Partner's reply is what completes the Global Chatter's goal. Their node marker sits on the meridian of the thread, and the Global Chatter's sent particle travels toward it.
Observable success. Their reply appears in the thread and reaches the original sender, and the conversation continues rather than ending after one message.
No completed page designs yet.
Completed design pages will appear here when they are ready to preview.
No completed page designs yet.
Completed design pages will appear here when they are ready to preview.
No comments yet. Be the first!