{ "id": "7f951a166bfa7a0c6bf716418ddc72984bba8a98b4b469ab03e2cc0f4128a558", "pubkey": "a9434ee165ed01b286becfc2771ef1705d3537d051b387288898cc00d5c885be", "created_at": 1730103610, "kind": 30818, "tags": [ [ "d", "zapchat-project" ], [ "title", "The Zapchat Project" ], [ "summary", "The Developing Project Description Of Zapchat" ], [ "published_at", "1729592304" ] ], "content": "image::https://cdn.satellite.earth/596850538c6476dae7f4193028de4688eeb24a3928a4b9555fab464f976a03a7.png[]\n\n= Value Proposition \n== Exceptional zapping \u0026 chatting\n* Converse on anything\n* Value-for-Value on anything\n\n== Interoperable, monetizable communities\n* Niches with reach\n* Organic discovery, maximal edge effect\n* Price lists / micropayments all the way down\n\n== Onboards people to Keys, Relays \u0026 Money\n* Engaging, visual Key generation and handling\n* Relays (+ Media servers) as Communities and Hosting solutions\n* Money as Community banks \n\n\n= Premises \u0026 Philosophy \n=== Chat is the universal interface\nThis is true in two ways: \n\n1. Action vs Reaction (or very similarly Input vs Output) is the most basic UX pattern of any software \n2. Chat is the only content type that is by default constrained to the Community / Group only. Other content types can be published in multiple communities/groups at once. This makes Chats the content type that is most universally useful to any Community / Group. \n \n=== Nostr is omnivorous\n1. It will eat most content types. \n2. It gives all those content types a reply section, a way to get zapped, a unique universal identifier, … \n\n=== Nostr incentivizes owning a relay\nHaving your own relay (+media server) is the most efficient way to stack an infinite list of desirable features with the simplest UX: \n\n* speed \n* privacy \n* computation \n* un-ruggabilty and back-ups \n* sharing specific content exclusively with a specific set of profiles \n* … \n\n=== People naturally organize around common interest and goals (i.e. Communities)\n\n=== Different types of communities use different content types \n\n=== Interoperability thrives on simple building blocks and big, blurry edges\n\n=== Quality \u003e Quantity\nIn terms of Product: \n\n* Testing is 50% of the work\n* Prototypes aren’t Products \n\nRegarding Customers \n\n* 100 true fans \u003e 100K uninvolved sheep\n\n=== Cashflow fast\n\n=== Mistakes are cheaper on paper\n\n=== Walk the talk. Eat the dog food.\n\n=== Win-Lose isn’t profitable without slaves \n\n\n= Design Patterns\n\n== Chat UX\n* Swipe left-right + Long press actions\n* Readable, conversational threads\n\n== Bottom Bars\n* Access to main actions \n* Slide-up modals only\n\n== Tabs\n* Displayed under most publications to access different aspects of it (longer content, replies, shares, public bookmarks, details, … )\n* Every tab looks like a button, because it is a button (long-press if needed)\n\n== Travel Back\n* Granular control over what you want to go back to\n* A way to go back all the way to the home screen in one action\n\n== Emoji icons\n* Easiest icons to be interoperable on \n\n\n= Audience\n== Customers \nDevs and early Nostr power users that:\n\n* have sats\n* use Android (mobile) and native chat apps on Mac / Linux / Windows (desktop)\n* need and use chats with swipe actions, reactions, GIF’s, …\n* are readers\n* are excited about Nostr as a communal knowledge base\n* are curators\n* are collaborators, not lone wolves\n* are creators (app builders, writers, designers, ..)\n* don’t fit into a neat little iNfLuEnCoR box of things they publish about\n* value targeted publication\n* want apps to work offline / in airplane mode\n* appreciate beautiful design\n\n== Customers of Customers\n* know how to use chats\n* know how to read their inviter's instructions in the chat (if needed) \n\n\n= The No-No lIst\nThings Zapchat will not have, do or show:\n\n=== An official website\nInstead: Zapchat Npub + Community + Signed releases + Stories + ...\n\n=== NIP-05 handles\nInstead: Npub and Colour + Imposter warnings\n\n=== Slave terminology: Accounts, Log In, Sign Up, … \nInstead: Profiles, Get Started, Secret Key, Public Identifier, ...\n\n=== Kind-1 reply sections\nInstead: Kind 1111 generic replies\n\n=== Reposts\nInstead: Sharing to different Communities, Quotes, Highlights, …\n\n=== Non-Nostr Link previews\nInstead: Purple URL, that’s it \n\n=== Lists for Follows, Bookmarks, …\nInstead: Labels, Relationship statuses, …\n\n=== Grants, VC money\nInstead: Business model with early cashflow \n\n=== A global onboard flow\nInstead: Focus on Invites (personal and community)\n\n=== Marketing as a Nostr or Bitcoin app\nInstead: Excellent tool for community chat \n\n\n= Monetization\n== Hosting, Compute \u0026 Privacy\n=== Zapcloud\nOffer or partner with an all-in-one hosting solution that combines:\n\n* Relays\n* Blossom media servers\n* optionally: Community Lightning node / cashu mint\n* optionally: Private Computation \n\nPay per use of: \n\n* Storage\n* Bandwidth\n\nCharge a high enough price because:\n\n* The infrastructure is independent (i.e. not Amazon/Google/...)\n* Early adopters happily pay extra for scarce products/services\n\n== Publication tools\n=== Zapstore\nCollaboration with Zapstore as a tool for releasing and monetizing App releases\n\n=== Zaphunter\nService that computes for you where your publication is probalisticly most valued (i.e. zaps, conversation around it, …)\n\n== Community\n=== Zapcats\nPublicly readable community where the Zapcats (i.e. Team) walk the talk, get feedback, build, market and ship the app releases. \nWrite access has a price list. \n\n== App Releases \u0026 Other publications\n=== Value-for-Value\n\n=== Zapwalls\nOnly releasing X publication after XX amount has been zapped\n\n== Merch\n=== Zaphats \n\n\n= Marketing\n== Community\nBuilding in public in the Zapcats (and other overlapping communities):\n\n* Targets the exact customers we're going after \n* Proves the value prop of the app \n* Keeps us honest\n\n== Invites\nNothing involves new users like a personal invite to a scoped community.\n\n== App Releases\nPublished on Nostr (zapstore, …) with a monetized conversation around it. \n\n== Profile \u0026 publications \nThe Zapchat npub, The Zapcats community, ...\n\n== Fun Nostr stuff\n* Emoji pack\n* GIFS\n** Zap-cats\n* Memes\n** Visual\n** Tag phrases \n\n\n= Feature Roadmap\n\n== General plan\nPriotize that which fosters:\n\n* Collaboration of the team\n* Early cash-flow\n\n== Steps\n1. Monetizable relays\n2. Chat\n3. Posts\n4. Repos\n5. Wikis\n6. Articles\n7. Stories\n8. Products \n\n\n= Tech Stack \n== Main language \u0026 Framework\nDart, Flutter\n\n* It draws the pixels\n* It’s neat and incentivizes having clear building blocks (widgets) all the way down\n* It has very limited third party dependencies\n\n== Logic \u0026 Heavy lifting\nGolang\n\n== Most prominent NIP’s and event kinds\n* General replies\n** Kind 1111\n* Relationship Status\n** NIP-81, kind 30382 and 31382\n* Relay info, pricing, services\n** NIP-66 and a highly needed new \"Spin up a relay\"-service NIP \n\n\n= Team\n\nGet in touch 🎉\n", "sig": "42af2e6d67b1876fa9d9995ada919cd8458264f7a545bfc471e3304447313cc9cb84831b5ce5c60b0d919447386841876cff81cde82d6c95789b3c1302ab0f64" }