Many developers creating new npubs just for releasing apps.
In v2 we will be pushing features so that they use their most reputable npub.
Otherwise web of trust is even less helpful.
Zapstore
_@zapstore.dev
npub10r8x...t2p8
Download 1.1.2 for Android: https://zapstore.dev/
SHA-256 checksum: 29b7aae256ef567e466c30fac13b8a7794d84a79862162d69f029f61c2ce5dd2
APK certificate hash (for AppVerifier): 99e33b0c2d07e75fcd9df7e40e886646ff667e3aa6648e1a1160b036cf2b9320
Nostr DMs will be ignored, tag us instead.
ICYMI: Update now
View quoted note โ
The app is dead. Long live the app!
View quoted note โ
Zapstore 1.1.3 released, update now!
Rolling out Zapstore v2 over the next weeks, this patch release includes compatibility with new relay v2 constraints and the new catalog signing key.
If you stay on 1.1.2 you will notice the experience degraded, though it should still work.
Step by step, v2 taking shape ๐ท


Imagination, taste and drive are the limiting factors ๐ฏ
View quoted note โ
Shower thought turned into an app!
Zaplite is a lightweight client for Zapstore
The app itself is only 1.5 MB. It uses very little storage and bandwidth. Designed to run on low powered devices and old Android versions.
No search by name
No browsing
No stacks
No screenshots
No comments, profiles, or zaps
No privacy reports or permission lists
No settings or Tor
No update all
No uninstall
Just keeping up to date.
https://zapstore.dev/apps/dev.zapstore.lite
Services back online.
Relay should be healthy but please report if you find any issues.
Investigating what happened.
View quoted note โ
We are having issues with our server.
On it. Will post updates here.
Despite having the lowest bar for publishing apps ever...
We still have developers lagging behind.
WE GONNA LOWER IT EVEN MORE


Replacing our indexing software, so there won't be external updates until tomorrow due to this maintenance operation.
Self-publishing not affected.
We now placed all emphasis on certificates, so if you get another "certificate mismatch" just know it will be the last time.
We picked one stable key per app, and honor rotations. Prioritizing self-signed apps and deprioritizing external builds such as F-Droid.
This is the first step towards v2.
Zapstore v2 is becoming almost a full rewrite. The clankers, @Pip the WoT guy and @franzap have been going hard on development (but mostly systems design) for many weeks now.
It is the first time I can say everything *actually* makes sense. We have a cohesive product story that is reflected in every project that constitutes it.
Including how we communicate it. It's a freedom tech product, not just a nostr one anymore.
This is why I'm quite silent, and why there are no incremental updates. The whole product will be launched at once.
We can finally push features we've been asked for, for ages. I'm particularly excited about the new privacy and security features. Publishing and discovery as well.
The new website is looking hot. Not only way faster but more clear. No more ambiguities around rules for publishing.
I have also taken time to sharpen tools and operations, many are now agent-first (public and internal). And app releases should happen more often.
Fortunately, it seems we won't have many migration or backward-compatibility issues.
Hard work, probably a million decisions taken already to reshape this in the right direction. Excited for what the future holds.
Done!
Appears to be a great Google Maps alternative:
https://zapstore.dev/apps/naddr1qqyxzurs9emx2mrpqyv8wumn8ghj7un9d3shjtn6v9c8xar0wfjjuer9wcpzq7xwd748yfjrsu5yuerm56fcn9tntmyv04w95etn0e23xrczvvraqvzqqqr7pv8aaj9n
View quoted note โ