Zapstore

The open app store powered by your social network

Download 1.0.3 for Android: https://zapstore.dev/

SHA-256 checksum: 60b61717b1858988f84de04d1e8947f97c6029919209dd71cb0c655aa0850105

APK certificate hash (for AppVerifier): 99e33b0c2d07e75fcd9df7e40e886646ff667e3aa6648e1a1160b036cf2b9320

Tech support for developers: https://signal.group/#CjQKIC0VCHf6gGeeHKcIrKcaI-B5Kjvge2NKw2i4P55tMkCwEhBaOk9B80F3_MhMYVbgj7lL

Tech support for users: https://signal.group/#CjQKIK20nMOglqNT8KYw4ZeyChsvA14TTcjtjuC2VF6j6nB5EhDLZ7pQHvOeopr36jq431ow

Nostr DMs will be ignored, tag us instead.

Public Key

npub10r8xl2njyepcw2zwv3a6dyufj4e4ajx86hz6v4ehu4gnpupxxp7stjt2p8

NIP-05 Address

zapstore.dev

Profile Code

nprofile1qqs83nn04fezvsu89p8xg7axjwye2u67errat3dx2um725fs7qnrqlgpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0ds3d9ezw

Publishing to

relay.damus.io

nos.lol

Author Public Key

npub10r8xl2njyepcw2zwv3a6dyufj4e4ajx86hz6v4ehu4gnpupxxp7stjt2p8

Show more details

Last Notes

2026-04-14 01:58:42 UTC

- reply

We can present app stacks but can't install on behalf of the user. It needs to be done one by one.

2026-04-13 21:06:46 UTC

- reply

Lol can't do anything about that.
It's impossible to be on top of thousands of packages and the retarded decisions made by hundreds of developers.
Indexer support will have to be financed in some other way

2026-04-13 17:46:27 UTC

- reply

Would you pay for a fix?

2026-04-13 17:44:29 UTC

- reply

Or spell it correctly? 😅

2026-04-11 20:03:41 UTC

- reply

Dear developers, please migrate these apps via https://zapstore.dev/community/migration (or by using latest zsp!) before they stop showing in newer versions of Zapstore. Deadline April 21st.
@npub1v3t…yvjh: com.koalasat.pokey, com.koalasat.samiz
@npub1v5u…n0v5: fm.fountain.apps
@npub1dsn…2h64: com.aqstr.app
@npub1wyu…87ez: ninja.nostrudel
@npub1w05…tl3x: com.cheshireremnant.teleprompter
@npub1w4u…0jr5: com.greenart7c3.morganite
@npub10fp…332x: com.wavves.app
@npub1s56…3h9f: com.pratik.zaptracker
@npub1scv…68d8: com.espy.app
@npub130m…l29s: com.routstr.localplusplus
@npub13jy…y824: com.github.haorendashu.cache_relay, com.github.haorendashu.nostrmo, com.github.haorendashu.nowser
@npub13uy…d8hw: com.Emin.Karayel.ChristianAppBlock
@npub13lj…cfhw: com.galoyapp
@npub1j9k…uswx: com.walletscrutiny.app
@npub1jeq…nmal: com.tuma.satstracker

2026-04-10 22:56:07 UTC

- reply

Wrong. We're funded by Rothschild's directly.

2026-04-07 22:38:35 UTC

- reply

Ask people to share their stacks 😉

2026-04-07 20:17:40 UTC

zsp got competition 😅
https://asccli.sh/

2026-04-07 17:07:58 UTC

- reply

What is that app store? 👀

2026-04-07 15:59:00 UTC

- reply

Publish a useful app and you will get zapped

2026-04-07 14:01:53 UTC

Anyone else having issues zapping via NWC in Zapstore?
#nevent1q…9t9c

2026-04-07 13:34:46 UTC

- reply

Thank you @nprofile…0a65 🫂

2026-04-07 13:30:30 UTC

- reply

Just introduced a feature to remotely bust entries in local storage

2026-04-07 13:27:21 UTC

- reply

I do not see that. Have you cleared local storage since the incident?
That app does not exist in the relay.

2026-04-07 02:35:53 UTC

🚀 Zapstore 1.0.2 just released!
- Faster loading
- More reliable updates check
- Curated stacks
- A handful of annoying bugs fixed
- Under the hood changes getting ready for communities
Swipe on the stacks to "See More" and make sure you migrate yours to the new format!
Update from Zapstore itself or https://zapstore.dev

2026-04-06 22:17:23 UTC

- reply

What? How are zaps not working?

2026-04-06 16:16:52 UTC

If there is one thing as a user you would pay for in Zapstore...
What would that be?
How much would you pay?

2026-04-02 14:49:25 UTC

- reply

The developer chooses to publish multiple apps, and under different npubs
The link error fixed and out in next release, sorry

2026-04-01 16:25:59 UTC

- reply

Following your logic I assume you meant prior to tapping "Update"
What's the point of doing that?

2026-04-01 15:59:03 UTC

- reply

What exactly is Google Play flagging Cake Wallet for?
Which "another market"?
We are going to introduce malware scanning but I hope you appreciate we don't have the same resources as Google.

2026-04-01 15:53:15 UTC

- reply

Thank you but keep in mind these reactions are out of proportion:
#nevent1q…crrh

2026-04-01 15:25:55 UTC

- reply

If you had no warnings it's the same app
I really don't get it

2026-04-01 15:18:31 UTC

Zapstore working as intended, despite the bug
💯
#nevent1q…rmh9

2026-04-01 15:17:16 UTC

- reply

Guys clear local storage, it's fixed

2026-04-01 15:12:06 UTC

Important clarification:
While the UX is confusing, this is not a catastrophe as it may have sounded.
The word "download" is ambiguous. This posed no risk whatsoever to current Wisp users who wanted to *update*. Android protects you from APKs signed by a different developer certificate.
However, there was a risk for new *installs* but:
- users would have noticed this app did NOT come from @nprofile…tkue but instead from a repository "github.com/captain-stacks/wisp" very clearly displayed in the UI.
Moreover this appared to be an auto-indexed app added by mistake by a nostr user, no malicious code.
That said thank you utxo for sounding the alarm, now this critical bug has been fixed.
Just keep in mind forks will appear and this is EXACTLY my thesis of why catalogs need to be protected.
Striking the balance between permissionless and safe, is fucking hard.
#nevent1q…7dav

2026-04-01 14:59:32 UTC

Issue with duplicate/forked apps is fixed.
Original self-published apps are up again.
If you still see duplicate apps, go to your profile screen and tap on "Clear local storage". If you keep seeing duplicates, reach out to us.
Please share 🙏
https://npub10r8xl2njyepcw2zwv3a6dyufj4e4ajx86hz6v4ehu4gnpupxxp7stjt2p8.blossom.band/9d317a45a9d703f22b03ea2cc7b3e13288d8757730a6deee8d327d3263e760e0.jpg

2026-04-01 00:21:34 UTC

You can now drop Obtainium!
#nevent1q…40k4

2026-04-01 00:20:46 UTC

- reply

It should, yes

2026-03-31 18:36:39 UTC

- reply

Fixed already, available in next release

2026-03-30 11:34:29 UTC

- reply

GM
If you see "app no longer available" it means you are on an old version of Zapstore.
You need to manually find "Zapstore" (because of a bug), access the app detail screen and only then an update will show. Update right away.

2026-03-25 19:04:56 UTC

Fixing tons of bugs y'all reported in the mobile app, thanks for the feedback!
New release coming soon 🫡

2026-03-23 21:24:38 UTC

Attention everyone!
We need to complete the migration to the new NIP (the nostr spec we use). If you don't want to start missing apps:
Update to latest Zapstore 1.0.0+ if you haven't yet.
Developers use zsp 0.4.4+ for publishing ideally. At the very minimum zsp 0.3.4.
(If possible, developers also link your keystore! zsp identity --link-key)
We're a small team and can't afford a smoother transition. We're doing our best but those who don't update by April 21st DEADLINE will be left out.

2026-03-21 17:17:48 UTC

- reply

That's great.
So, the bug is related to your app using different identifiers in metadata (`com.traveltelly.app`) than in the APK manifest (`com.traveltelly.twa`)
We should be catching this in Zapstore but if you want to resolve it faster, fix that.
What are you using to publish it? zsp definitely extracts the correct metadata for me.

2026-03-21 15:22:20 UTC

- reply

It's a bug in zapstore because I can install the APK manually just fine.
It is strange though. This is the only app that triggers the bug.

2026-03-21 01:58:10 UTC

- reply

I thought it was self evident but no 😂
That's right. Californians are encouraged to move to another state or country so they can keep using Zapstore.

2026-03-21 00:51:56 UTC

- reply

What version of zsp are you using?

2026-03-21 00:37:40 UTC

- reply

If you give details I may be able to help

2026-03-21 00:36:55 UTC

- reply

When things change, we will find a way.
What's important is not becoming a cucked doomer.

2026-03-21 00:32:34 UTC

Zapstore will remain usable by anyone around the world without requiring personal information, identification or an account. Zapstore and our services will remain available internationally. If Zapstore can't be used in a region due to their regulations, so be it.
https://image.nostr.build/a05f4f7291dcbfa738263e6f22f8cd3089114d2f5c40b436b0e549e1b5d26f2e.png

2026-03-20 13:38:59 UTC

- reply

I am pretty sure you have multiple profiles and "dev.zapstore.app" has NOT been uninstalled from all of them. That explains why you can install rc1: it has a different app ID "dev.zapstore.alpha"
I don't know how you got into that situation but as I said before you fix it by running adb uninstall. This is an Android problem not a Zapstore one!

2026-03-19 22:29:08 UTC

systemd added birth date storage in order to comply with California, Colorado and Brazil age verification laws.
Slippery slope.
https://image.nostr.build/3086923f6e9e5e55c755ae8825478670b3d3abd14d95d4937d7e361fe3eb527f.jpg

2026-03-19 22:08:43 UTC

- reply

@npub1c9d…sqfm could you confirm #GrapheneOS will remove the sideloading restrictions set in AOSP?

2026-03-19 22:06:35 UTC

- reply

We had issues with the relay, is it working better now? You could kill the app and/or clear local storage if issues persist. Let me know!

2026-03-19 22:05:22 UTC

- reply

Would it be possible for you to share a screenshot? It can be here or on our Signal support group. Thanks

2026-03-19 19:19:29 UTC

- reply

I am finding it quite hard to follow. You can be certain that your device and OS are fully supported because that is what I personally run.
"3 instances on Graphene" what would that mean? My advice would be connect your device to a computer and use adb to remove the app completely: `adb uninstall dev.zapstore.app`

2026-03-19 19:11:02 UTC

- reply

Thank you, this helps. Now you need to tell me what the error is, because I cannot guess it.

2026-03-19 17:54:31 UTC

- reply

Hi, what are you trying to install, which version? I need more details to help you

2026-03-19 17:37:34 UTC

Our relay was getting overloaded since last night, and that resulted in a degraded experience in the mobile app and webapp, that a lot of you noticed. Fixes were applied and it should work better now. We are monitoring the situation.
It's likely we were getting spammed. Already planning longer-term solutions for this.

2026-03-19 17:32:07 UTC

- reply

When you say "App Not Found", where does that message appear? Which version?

2026-03-19 16:36:18 UTC

- reply

which version of Zapstore are you running?

2026-03-19 16:34:31 UTC

- reply

Yes. We are having issues. Sorry.

2026-03-18 17:30:58 UTC

https://image.nostr.build/e8c114ffae5f857839c12af60df9dd48c4a059872b5e27c66a51927ce290659a.png
You should notice because the interface is pretty broken already.
If in doubt 👉 Download at https://zapstore.dev/
#nevent1q…xgy4

2026-03-18 13:14:53 UTC

- reply

Sorry whats the problem?

2026-03-18 01:54:35 UTC

- reply

When you inspect the generated events, the 'author' there does coincide with the npub in zapstore.yaml?
Try again I whitelisted you

2026-03-18 01:52:30 UTC

- reply

This is very strange, I had multiple people publishing this way already. I'll manually whitelist you

2026-03-18 01:19:14 UTC

- reply

I fed it to the agent, it compared against the code and concluded you may be signing with a different pubkey than the one declared in the config. Can you confirm?

2026-03-17 19:10:07 UTC

- reply

Link?

2026-03-16 23:42:09 UTC

Try making your agent autonomously publish an app to Google Play or F-Droid

2026-03-16 23:37:39 UTC

Bro blindly pushing to Zapstore 😂
So cool. It works!
#nevent1q…jeek

2026-03-16 18:11:03 UTC

- reply

Love it

2026-03-16 14:29:51 UTC

- reply

of course...

2026-03-16 14:29:23 UTC

- reply

It was a joke. Just in case.

2026-03-16 13:32:58 UTC

- reply

There will be a perfect way out: add to your license you do not allow using your software anywhere in the world 😂

2026-03-16 13:01:46 UTC

Designing a NIP for age verification so you can use Zapstore in California.
😂😂
https://image.nostr.build/c58ca545ab6f7cb8da6da581bf40ca75cb2d379b65fd482b809e6b8d1d760424.png

2026-03-16 12:19:48 UTC

- reply

Give this to your AI and it will figure it out: https://zapstore.dev/docs/publish

2026-03-16 12:18:56 UTC

- reply

Exactly. Give this to your AI and it will figure it out: https://zapstore.dev/docs/publish

2026-03-16 12:15:33 UTC

- reply

Are they even on Nostr?

2026-03-14 15:39:17 UTC

- reply

Think whatever you want. But if you are going to call my work's mission ignorant then get the fuck out of my comments.

2026-03-14 01:39:51 UTC

- reply

This is funny, ngl

2026-03-14 01:39:35 UTC

I didn't know Stockholm syndrome existed for mobile devices 😂
#nevent1q…l3mw

2026-03-14 01:30:46 UTC

PSA if you see duplicated apps in Zapstore, or apps signed by Zapstore that shouldn't, please go to profile screen > Clear local storage
#nevent1q…6mrv

2026-03-14 01:29:20 UTC

- reply

@npub1kzg…ylue and @npub1w4u…0jr5 I'd appreciate if you could re-publish your latest versions. This mistake won't happen again, I'm sorry!
Recovered events for @npub142g…xrj0 @npub1lu2…xlm6 @npub1v3t…yvjh @npub120m…5vf8 @npub1z2g…6ser but if you could please double-check apps are effectively in their latest versions.
Thank y'all for understanding.

2026-03-14 01:24:34 UTC

Zapstore relay is back up again!
Post-mortem:
A bug in the indexer background process replaced 8 self-published apps with indexed ones (signed by Zapstore indexer). Main symptom for users was seeing duplicates of these apps.
Backups were there but faulty so the recovery was difficult and partial. 5 were successfully recovered and 3 were not (Primal by @npub1kzg…ylue and Amber and Citrine by @npub1w4u…0jr5 ).
Users please go to your profile screen > "Clear local storage" if you see double entries of some apps! We are working on a feature in the next release to repair these issues without you having to delete the cache.
Backups, as well as the original indexer bug, were fixed.
#nevent1q…trck

2026-03-13 19:35:46 UTC

I'll explain:
- I'm switching off the relay to prevent bad data from spreading to clients which will cache it
- We are working on ways to bust these cache entries in the mobile app but that's not ready yet (next release though)
- If I leave the relay on, I will get an avalanche of support requests I can't handle by myself
- I'm also the only guy doing devops, which really is a full-time job in itself, and I have an appointment now so I'll take care of it when that's done. At least 2-3 more hours
tl;dr: making sure all apps are always up to date is hard.
#nevent1q…n50a

2026-03-13 19:29:41 UTC

We just had a data issue in our indexer, it's possible I have to turn the relay off for a few hours. Investigating. Apologize in advance.

2026-03-13 18:34:26 UTC

- reply

What is the most secure Android in your opinion, then?

2026-03-13 18:32:32 UTC

- reply

I am interested, so I searched HN threads and could not find anything like you describe. Can you share some links?

2026-03-13 16:06:22 UTC

- reply

Let me know if we can help you in any way.
FYI there is now the option of cryptographically linking your Nostr identity to your Android keystore/certificate (zsp identity --link-key). That is one single event you sign once, it can even be done offline and then publish. From that moment on we take care of pulling your new releases into the Zapstore relay.
Pro: you don't have to mess with crafting Zapstore-compatible events. Con: you don't have full control over the metadata, though in practice it works just fine as we can pull metadata from Google Play, F-Droid and others.

2026-03-13 15:54:19 UTC

- reply

Any plans of publishing the Android app on @npub10r8…t2p8 ?

2026-03-13 15:40:46 UTC

- reply

You're right, fixed it in the wizard

2026-03-13 15:07:47 UTC

- reply

Ideally the icon should be correctly extracted from the APK. Just FYI, this appears to be an edge case as we parse over 3000 apps and very few have issues with icons.
Overriding in metadata should work, what do you mean it does not let you pick an icon? If you send more info I can help

2026-03-13 15:02:12 UTC

- reply

It will improve soon. You can find yours by visiting your profile in the app

2026-03-13 15:00:28 UTC

- reply

Explain

2026-03-13 14:58:48 UTC

- reply

What are you talking about?

2026-03-12 16:48:30 UTC

- reply

It has to be companies with *some* weight I imagine, not just random apps

2026-03-12 16:29:21 UTC

- reply

Stack accordingly

2026-03-12 14:47:47 UTC

- reply

You can keep using Verizon I suppose

2026-03-12 14:41:36 UTC

- reply

Per month? 🤔

2026-03-12 14:40:44 UTC

- reply

This is amazing. How can we make it more amazing by including a Zapstore link to https://zapstore.dev/apps/app.zeusln.zeus in step 1? @npub1xnf…lpr5

2026-03-12 14:29:49 UTC

- reply

Go for it!

2026-03-12 14:24:32 UTC

We have reached out to Keep Android Open to co-sign the letter: https://keepandroidopen.org/open-letter/
After a week, received no response. I read somewhere that they require a Wikipedia page (?) to get listed.
But we will add some form of banner to our app and website.
(1) Anyone here with a Wikipedia account to create a Zapstore entry?
(2) Anyone here with a contact at Keep Android Open?
I was happy to see a good soul added Zapstore on here: https://en.wikipedia.org/wiki/List_of_Android_app_stores

2026-03-12 14:19:32 UTC

- reply

Great question!

2026-03-12 14:19:19 UTC

If Google does not change its stance before September, assume some apps won't work on Google-controlled devices.
For those using Zapstore on the Guulag, we will attempt to identify apps such that users can know/filter beforehand. At the same time, we will take the opportunity for a marketing campaign emphasizing:
"Google owns your device and is limiting your options. If you want to fully unlock all apps, use @npub1235…0ht5 or other alternative ROM."
Hoping to leverage this insanity against their control.
#nevent1q…scfq

2026-03-12 12:29:16 UTC

- reply

Music to my ears... thank you 💜

2026-03-12 12:22:38 UTC

- reply

Fixed now?

2026-03-12 12:20:11 UTC

- reply

Thank you

2026-03-12 00:34:34 UTC

- reply

It was all for your own good 😅

2026-03-11 19:00:42 UTC

- reply

@nprofile…6vq0

2026-03-11 19:00:17 UTC

- reply

Yes, of course, it will come. We're doing what we can

2026-03-10 22:10:04 UTC

After these important infrastructure improvements, our next big challenge is communities (next 4-6 weeks).
Anyone is able to run one, and discoverability will be first-class in the app and webapp. Instead of managing relays, Blossom servers, and tweaking a bunch of technical knobs, no: those are prepackaged in a community spec.
We are going to push the permissionlessness hard.
Stay tuned, it's going to be awesome.