Value Proposition

Exceptional zapping & chatting

Interoperable, monetizable communities

Onboards people to Keys, Relays & Money

Premises & Philosophy

Chat is the universal interface

This is true in two ways:

1. Action vs Reaction (or very similarly Input vs Output) is the most basic UX pattern of any software

2. 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.

Nostr is omnivorous

1. It will eat most content types.

2. It gives all those content types a reply section, a way to get zapped, a unique universal identifier, …

Nostr incentivizes owning a relay

Having your own relay (+media server) is the most efficient way to stack an infinite list of desirable features with the simplest UX:

People naturally organize around common interest and goals (i.e. Communities)

Different types of communities use different content types

Interoperability thrives on simple building blocks and big, blurry edges

Quality > Quantity

In terms of Product:

Regarding Customers

Cashflow fast

Mistakes are cheaper on paper

Walk the talk. Eat the dog food.

Win-Lose isn’t profitable without slaves

Design Patterns

Chat UX

Bottom Bars

Tabs

Travel Back

Emoji icons

Audience

Customers

Devs and early Nostr power users that:

Customers of Customers

The No-No lIst

Things Zapchat will not have, do or show:

An official website

Instead: Zapchat Npub + Community + Signed releases + Stories + ...

NIP-05 handles

Instead: Npub and Colour + Imposter warnings

Slave terminology: Accounts, Log In, Sign Up, …

Instead: Profiles, Get Started, Secret Key, Public Identifier, ...

Kind-1 reply sections

Instead: Kind 1111 generic replies

Reposts

Instead: Sharing to different Communities, Quotes, Highlights, …

Non-Nostr Link previews

Instead: Purple URL, that’s it

Lists for Follows, Bookmarks, …

Instead: Labels, Relationship statuses, …

Grants, VC money

Instead: Business model with early cashflow

A global onboard flow

Instead: Focus on Invites (personal and community)

Marketing as a Nostr or Bitcoin app

Instead: Excellent tool for community chat

Monetization

Hosting, Compute & Privacy

Zapcloud

Offer or partner with an all-in-one hosting solution that combines:

Pay per use of:

Charge a high enough price because:

Publication tools

Zapstore

Collaboration with Zapstore as a tool for releasing and monetizing App releases

Zaphunter

Service that computes for you where your publication is probalisticly most valued (i.e. zaps, conversation around it, …)

Community

Zaplab

https://chachi.chat/zaplab.nostr1.com

Publicly readable community where the Zaplab crew walks the talk, gets feedback, builds, markets and ships the app releases (and dev packages).

Write access will have a price list.

App Releases & Other publications

Value-for-Value

Zapwalls

Only releasing X publication after XX amount has been zapped

Merch

Zaphats

Marketing

Community

Building in public in the Zaplab (and other overlapping communities):

Invites

Nothing involves new users like a personal invite to a scoped community.

App Releases

Published on Nostr (zapstore, …) with a monetized conversation around it.

Profile & publications

The Zapchat npub, The Zapcats community, ...

Fun Nostr stuff

Feature Roadmap

General plan

Priotize that which fosters:

Steps

1. Monetizable relays

2. Chat

3. Posts

4. Repos

5. Wikis

6. Articles

7. Stories

8. Products

Tech Stack

Main language & Framework

Dart, Flutter

Logic & Heavy lifting

Golang

Hypernotes: Widgets, Stories, ...

Nostache: {{Mustache}} templating + Nostr functionality

Most prominent NIP’s and event kinds

Team

Get in touch on the zaplab.nostr1.com relay 🎉