Zapstore

Step by step, v2 taking shape 👷

Imagination, taste and drive are the limiting factors 🎯

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.

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,

and

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

"Version numbers are strings"

Developers:

Trying out new things.

Coming soon to a Zapstore near you.

These comments keep me going 💙

A Bitcoin node syncs blocks and queries locally.

Organic Maps pulls tiles and queries locally.

Why can't Zapstore pull release bundles and query locally?

At first this sounded crazy.

It turns out it's (almost) the holy grail of privacy and UX.

Initial prototype of v2 is insanely promising.

App written in Kotlin from scratch.

Browsing apps is instant. Search is orders of magnitude better.

For update checks, no need to reveal your installed app set to any remote server.

Tor by default.

And that's just the tip of the iceberg.

More soon.