Zapstore

Decentralized Application

An open app store built on Nostr where app releases are cryptographically signed by developers and curated through social trust networks. Users discover apps through people they trust — anyone can run a catalog, and users choose which catalogs to follow. Developers publish directly to users with Bitcoin zap tipping and a direct communication channel. Over 3,000 apps available. Android app live with iOS planned Q3 2026. Zapstore Studio in development for developer publishing tools and analytics.

Community
Links
Visit Community

Details

License Open source (Nostr-based; unconfirmed license); https://github.com/andotherstuff (AOS org)
Dev Status 🟢 Active
Dev Status Detail Released (Android 1.0 completed; 3,000+ apps; web app in development; iOS Q3 2026; Zapstore Studio and Decentralize Catalogs next 2-3 months)
Owner Franzap (founder); AOS Foundry (incubation); OpenSats and HRF (donors); https://zapstore.dev
Country USA (AOS collective)
Start Year 2024
Stack TypeScript/JavaScript (Nostr-based); Nostr relays (catalog and release events); cryptographic signing (developer keypairs)
Funding AOS Foundry (incubation); OpenSats (donor); HRF (donor); Freedom Tech Co. (donor)
Last Investigated Jul 1, 2026

Use Case Domains

Co-Creation & Knowledge

Decentralized Application Attributes

Origins App distribution / Freedom tech (motivated by Apple/Google duopoly over app distribution; cryptographic signing ensures tamper-proof releases; Nostr social graph replaces centralized curation)
Database Nostr relays (app catalog events; signed release metadata)
Query Language Nostr event subscription filters
Data Formats Nostr events (signed app release metadata; NIP-compliant); APK files (app binaries); cryptographic signatures (developer Ed25519 keypairs via Nostr)
Collaborative Live Editing N/A
Rich Text Editing N/A
Mobile Support Yes (Android — primary; iOS Q3 2026)
Web Support Yes (zapstore.dev web app in development)
Native Apps Yes (Android native app — 1.0 released)
Terms Free (no fees; direct Bitcoin zaps to developers)
Funds Undisclosed
Based On Nostr (Fed Pro — catalog events and developer identity); Bitcoin/Lightning (NIP-57 zaps — direct developer payment)
Use Case Category App distribution / Developer tooling / Open infrastructure
User Interface Type App catalog / Store (browse by trust catalog; app details; zap developers; community comments)
Offline Capabilities Partial (app catalogs cached; relay-dependent for new releases)
Collaboration Features Social trust catalogs (user-curated app lists); community comments and zaps on apps; direct developer messaging
Data Portability High (Nostr keypair identity; app releases cryptographically signed; catalog data portable)
Integration Ecosystem Nostr ecosystem; Bitcoin/Lightning (developer payments via zaps); any APK-compatible Android device
Web2 Data Export No
Prosocial Coherence Very high (eliminates app store gatekeeping; cryptographically verified releases; direct developer-user relationship; no platform permission required; Bitcoin zaps enable direct developer support)
Economic Flows Yes (Bitcoin zaps via Lightning — direct payments to developers; zero fees)
Governance & Decision Making Decentralized curation (user-selected trust catalogs; no central editorial board; anyone can run a catalog)
Media / Publishing Yes (app release announcements; developer publishing via Zapstore Studio)
Knowledge Management No
Sensemaking Yes (social trust graph surfaces recommended apps from trusted network)
Project Management No
Communication Model Asynchronous (app discovery; developer-user direct messaging)
Network Resilience High (Nostr relay diversity; no central app store server; cryptographic verification independent of Zapstore infrastructure)
Discovery Mechanism Social trust network; catalog-based; Nostr follows
Max Participants Unlimited (catalog-dependent)
Data Sovereignty High (developer-signed releases verifiable independently; user-controlled Nostr identity; no platform custody)