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.

🚨 Please update to Zapstore 1.1.2

It was released last week and contains a fix for a major security bug found in an underlying library, related to nostr event verification.

I don't believe it has been exploited as apps are loaded primarily from relay.zapstore.dev (which properly verifies nostr events) and we haven't heard of any report.

Found by ethicnology, thank you Sir (couldn't find his nostr profile, he deserves some zaps!)

https://github.com/zapstore/zapstore

Thank y'all for the kind words but also for the bug reports.

I hear you and know many things are suboptimal.

We are designing Zapstore v2 (mainly a new indexer with hard lessons learned, revamped zsp and a new mobile app)

I won't spill the beans yet but I'm excited. Everything starting to make much more sense.

Starting to push Zapstore repos to ngit, finally!

https://gitworkshop.dev/npub10r8xl2njyepcw2zwv3a6dyufj4e4ajx86hz6v4ehu4gnpupxxp7stjt2p8/relay.ngit.dev/zapstore

If we can figure this out and link to a specific APK hash, I will implement this

🎯

Seeing more Certificate Mismatch errors?

Deployed an upgrade to the indexer.

As we deprioritize F-Droid signed releases in favor of developer-signed (as it should be) you may find some new Certificate Mismatch errors.

To keep updating those apps you'll need to reinstall them. Unfortunately there is no other way. (If you have multiple profiles on your device, ensure to remove app from all of them!)

Apologies for the inconvenience, but it's the right move to minimize certificate mismatches in the future!

try again

Someone is constantly releasing updates to an app.

It's cool too see how frictionless app publishing can be, on the other hand they live in Latest Releases which takes space away from other projects.

We're going to move away from this dumb REQ approach and work on a smarter feed for discovering new stuff.

Amazing charts of apps on Zapstore!

https://dev.nostrolo.gy/zapstore

GM developers

When publishing, don't skip linking your Android keystore/cert to your Nostr identity!

(We need to know that you actually own the app)

Soon, apps without it will show as unclaimed, as any other indexed app regardless of who published the app metadata.

🚀 zsp release 0.4.14 :

• Fix bad name and icon extraction regression
• Fix Gitlab parser download path
• Add fastlane as metadata source
• Add Tor fallback for failing requests, retries
• Add default image compression

https://github.com/zapstore/zsp

NEW FEATURES

• Background auto updates (opt in)
• Check certificate ownership before installation
• Back up settings, bookmarks, and more to a device key
• Ability to exclude apps from updates
• NIP-56 reporting
• Shareable app dagnostics
• Efficient image loading

Also released new zsp and fixed several issues with apps stuck in the indexer.

Brave, Ironfox, Aurora Store, Flow and others are back!

Implemented on the fly image compression for icons, profile pictures and screenshots.

For some images gains are slight and for others up to 30x

Live on the website and on latest zapstore 1.1.0, it should feel way faster!

🥏 Zapstore 1.1.0 just dropped

New features and lots of fixes!

https://zapstore.dev/apps/dev.zapstore.app

Update from the app or download at zapstore.dev

Over the past week I have also been working on a completely new codebase for the Zapstore app, in pure Kotlin.

(A recurrent issue with the current Flutter app is the boilerplate/overhead to interact with native features.)

Things require less code and feel significantly faster, but to be fair it has 10% of the features so far. Promising option for Zapstore v2.

Great to see an increasing number of nostr-signed apps on the relay!

We also slowly keep adding more indexed apps and will soon re-enable the ability for anyone to add.

In parallel working on lots of code for the new product vision of Zapstore v2, can't wait to share more.

On the app side, ironing out last bugs for a new release. This week we'll have 1.1.0 if all goes well.

I've been silent lately, very busy cookin' the next gen of Zapstore.

Major building blocks to something that makes even more sense in the world of Android apps, and among many other things making it even simpler for developers to publish.

More soon!

Radar indexed on Zapstore!

https://zapstore.dev/apps/com.radarlabs.radar