Lume v1.2.0 update sneak peak, so far I've made:

- New UI

- Network Space: collective of all accounts that you're following and popular account (max 300) followed by your accounts following

- Support long-form content (Kind 30023)

- WIP: implement NIP-44

- WIP: new onboarding process

# NIP89 is the app store killer

App stores sit at the top of the food chain because they enable us to discover new apps.

Nostr doesn't need an app store to allow us to discover new nostr apps, because NIP89 allows this to happen from within any existing app.

Every nostr client *is* the app store, and you discover new apps by seeing comments etc on events produced by other apps.

### How it works

NIP89 provides two simple building blocks:

- a way for apps to “register” kind applications handlers (e.g. app X supports kind Y using such-and-such URL)

- a way for users to publicly associate kinds with these application handlers throughout their different platforms (e.g. web, vs ios)

A byproduct of this is that anyone can see what applications exist for a given kind and who (from the people they follow) uses which application.

Let's look at Zapstr as an example. It's a music player that lets you publish and listen to music track events (kind 31337).

You can also comment on a track with a note.

When your followers see that comment event in their twitter style nostr clients, the music track itself is not displayed. So it looks like you are commenting on nothing. Their client doesn’t know what kind 31337 means, how to render it, or how to interact with it.

In our new NIP89 world, the song event itself is no longer displayed as a missing event, but as a short description of the song (thanks to NIP31), and when you tap on the event it will open it in Zapster.

It does this by querying the people you follow for the app that *they* use to open kind 31337 events.

### Why this is awesome

Multiple applications can compete under the same use case. Competition is good.

Different applications may be better suited to different communities. For example let's pretend there's a competitor to Zapster, called Japster, designed specifically for Japanese users. Users in Japan who mostly follow other Japanese nostriches will see that most of the people they follow are using Japster not Zapster.

It also means that Nostr doesn't need an app store because your nostr client *is* the app store.

good morning nostr 🫡