make zapstore language and view friendly again

[alltheseas]

What you'd say to Nostr people: "Decentralized app store"
What a normie hears: "Sketchy, unregulated"
What to say instead: "No single company controls which apps you can install" [this is in the AppStore comparison matrix]

What you'd say to Nostr people: "Zaps"
What a normie hears: "???"
What to say instead: "Tip/pay developers directly" on landing page. Use "zap" inside the app once they're in. [this is in the AppStore comparison matrix]

What you'd say to Nostr people: "Developer signatures"
What a normie hears: "Technical jargon"
What to say instead: "Every app is verified by its creator" [this is in the AppStore comparison matrix]

What you'd say to Nostr people: "No review process"
What a normie hears: "No quality control, malware"
What to say instead: "Publish Instantly" [Idk if the wording is the best, but the concerning read is there]

Also consider: change "User Communities" to "Community Curation"

[alltheseas]

The projects that successfully communicate decentralization to normal people all share one trait: they talk about what the user gains, not what the system lacks.

• "Decentralized" → "No one can shut it down"
• "Permissionless" → "Anyone can publish"
• "Trustless" → "You can verify everything yourself"
• "Open protocol" → "No company controls it"

Every one of those reframings shifts from an architectural description to a user benefit. That's the entire trick. You're not hiding anything — you're just leading
with why it matters to the person reading it instead of how it was built.

Nostr isn't the selling point. What Nostr enables is the selling point.

[alltheseas]

"Infrastructure, not a movement"

Think about the products you use every day that are built on decentralized or open protocols:

• Email — federated, no single company controls it. Gmail never says "built on SMTP." It says "send email."
• The web itself — decentralized, open protocol. Chrome doesn't say "browse the decentralized hypertext transfer protocol." It says "search or type a URL."
• Signal — state-of-the-art cryptography (Double Ratchet, Sealed Sender, SGX enclaves). The homepage says "Say hello to privacy."
• BitTorrent — decentralized file sharing. Transmission's homepage doesn't say "peer-to-peer distributed hash table." It says "a fast, easy, free BitTorrent client."

Every one of these is decentralized, permissionless infrastructure. None of them lead with that fact. They lead with what you can do.

The moment you put the architecture in the headline, you've moved from "product" to "project." Products get users. Projects get followers. Zapstore wants users.

[alltheseas]

Signal's Playbook → Zapstore Actions

1. Headline = emotion, not architecture.
   Signal says "Speak Freely," not "Encrypted messenger." Zapstore should say what the user gains, not what the system is.

2. One button in the hero.
   "Get Zapstore." Not two CTAs competing. Move "For Developers" down the page.

3. Phone mockup belongs in the hero.
   You already have it — it's just below the fold. Move it up next to the headline.

4. Features as verbs, not nouns.
   "Install anything. Verify everything. Support directly. Own your apps."

5. Trust statement in plain English.
   "No gatekeepers. No app tax. No takedowns." — nine words, zero jargon.

6. Identity in one breath.
   "Zapstore runs on an open protocol. No company owns the directory — not even us."

7. Protocol details are second-click content.
   Signal mentions the Signal Protocol once, in parentheses. Nostr, zaps, relays → put on a "How it works" page, not the homepage.

8. Kill the "preview" asterisk.
   Signal doesn't caveat its own download button. Neither should you.

[alltheseas]

on light vs dark mode "crypto bro" projects

[alltheseas]

on spotify dark background comparison:

Spotify's dark mode isn't a "crypto dark" — it's a content dark. Different reason entirely.

Album art is the product. A dark background makes colorful cover art pop. A white background would wash it out and compete with it. Spotify is essentially a gallery — the UI recedes so the content stands out.

Same reason movie theaters are dark, Netflix is dark, YouTube's trending view is dark. When the content is visual media, you dim the frame.

Zapstore's equivalent content is app icons. And looking at the hero screenshot — it actually works. The floating app icons on the dark background do pop. That's the one section where Zapstore's dark theme earns itself the same way Spotify's does.

The difference is everything below the hero. Spotify stays dark because every screen is still a gallery of album art. Zapstore's lower sections are text, comparison tables, testimonials, and roadmaps — none of which benefit from a dark background. They'd actually read better on light.

So the honest answer: dark mode isn't inherently bad for consumer apps. It's good when your content is colorful and the UI should disappear behind it. It's bad when your content is text and the UI is the experience.

Zapstore could keep the dark hero (app icons floating on dark = works) and shift lighter as the page scrolls into text-heavy sections. That's not unusual — plenty of sites do a dark hero into a lighter body.

[alltheseas]

Adding a credible third party organization assessment on the google play 2026 imepending lockdown, we have at least a couple of ways of adding this external proof/validation of the problem ZS is attempting to solve

Option A - newsroom (i.e. objective):

Your apps. Google's permission.

Starting September 2026, Google will block apps on Android devices unless the developer registers with Google and submits a government ID.

That includes apps you sideload. Apps from F-Droid. Apps shared between friends.

37 organizations — including the Electronic Frontier Foundation and the Free Software Foundation — are fighting it.

"This converts sideloading from a right into a privilege that Google administers."

Zapstore doesn't need Google's permission. Neither should you.

[Get Zapstore]

Option B - The Countdown (makes this a real, tangible GULAG event, and instills urgency)

In six months, Google decides what you can install.

New Android rules require every app developer — even hobbyists, even open-source projects — to verify their identity with Google before you can install their work.

No verification? The app won't install.

"No single company should control which software you can run on your own device."
— Electronic Frontier Foundation

3,000+ apps. No gatekeepers. No deadline.

[Get Zapstore]

The countdown can include a live countdown timer!!

[alltheseas]

@NielLiesmons

👀

https://codepen.io/jdubtheegreat/pen/eYQaxjv

https://codepen.io/shshaw/pen/vKzoLL

https://youtu.be/yCpI3WqhJvg

[NielLiesmons]

Looking into how to include the Google shut down thing, yes.

[alltheseas]

@NielLiesmons mentions this as a loose framework: https://medium.com/the-mission/the-greatest-sales-deck-ive-ever-seen-4f4ef3391ba0.

I suggest making it clear we are pitching a prospective B2C Zapstore user on main page.

Flow should consist of

1. problem statement (google rugpulls, and corporatizes the android app store)
2. how is this problem solved ("what if there was no central authority"/"what if you could ask your friend instead"/"what if your friends asked you about which app to use")
3. how does Zapstore bridge 1. to 2. above (show beautiful @NielLiesmons in app screenshots of dev-user interaciton, zaps, friend-friend curation/WOT/recommendation etc.)

[alltheseas]

I agree with Fran in that product shouldn't be sold/communicated until the problem it solves is established. Basically 1, and 2 above should set the stage.

[NielLiesmons]

Just putting relevant screenshots here too:

Trying to find:

• The global shift Zapstore is riding on
• The situations most people have been in already
• Obvious pain points of big tech app stores

[NielLiesmons]

I'm liking this contrastual set up here. Better story flow, I think.

Copy and visuals not on point yet.

[NielLiesmons]

Elsat feedback:
a few comments for consideration:

• "Big Tech is Closing Down" -> make it more explicit "Big Tech is Disappearing Great Apps"
• "Creating Apps is Easy Now" -> reframe from user perspective (this is the core audience for the main page; dev ideally we have a distinct landing page for) -> "Great Apps Exist. You Just Can't Find Them."
• "You're Missing Out" reads vague/undefined to me -> rename to e.g. "Google Play is missing the best apps." (this serves as value prop to ZS users, and also serves as marketing to ZS target indie devs)
• Love the self-published & curated by communities 💪
• Jane is providing positive feedback, and asking for a thing to the dev 💪
  5m

Also thinking through this, we have an opportuntiy to make the exploration fun - "Make Finding Great Apps Easy & Fun Again"
4m

maybe hero headline?
3m

does a few jobs: 1) suggests the current status quo is broken (without naming google play), 2) promises/claims a better experience, 3) "Again" suggests this is how it always should have been and should be

[alltheseas]

"Fullly Transparent & Secure" reads vague, and is what I imagine other app stores also have.

Suggest making it more explicit and defined:

"Know Exactly What You're Installing"
Keep the same subtext - "You install exactly what the dev signed ..."