How are these apps going to be written? Are you trying to make a browser? I hope it's not just wrapping Chrome and asking people to write JavaScript.
Just launched a campaign at Geyser: https://geyser.fund/project/44billion/prelaunch
Apparently it will auto-close if it doesn't reach $210 goal 😱😱😱😱
If you like the project, please contribute or share to your follows!
Discussion
The project is a platform (a regular website with some tricks) that abstracts away the boring parts of making a nostr app like multi-account login/signing and notifications. Then devs are free to build simple Nostr apps that are just static websites that handle just one already logged-in user. It is supposed to help with app discovery too like app stores do.
What else will you abstract? Just abstracting login is not enough to justify this. Login is easy with bunkers and something like window.nostr.js.
Or even if you don't think it is, that's the same thing the Spring browser tried to do, and you could do it on a platform by rehosting web clients and force-including a window.nostr global that implements NIP-07 even for people that do not have an extension, and done.
But why?
I think it could be more interesting if you done something different like abstracting the UI and providing all apps with a homogeneous theme, or doing what I said on the note above, or perhaps also abstracting relay pooling, connection and selection and smart relay picking on behalf of apps, I don't know.
I'm aware of bunkers and of that lib. I've already seen that mysterious lib's button floating around on some webapps ^^.
Spring Browser is good and very similar but I think I can bring new ideas to the table that could work better, I hope.
There are some problems when trying to rehost web clients like api calls that won't work from different domains or blocked iframe loading.
For now I think if devs depend on my lib or on custom api calls to handle relay connection it may centralize things or be one more thing for them to learn. Though I definitely want to help handle things like user relay migration (copying events) that would be too much for every app to code and something the user shouldn't suffer with.
Thx for the ideas. I've added some extra explanations to the bottom of the campaign page.
You can also addon the built-in nostr specific customazations on my browser having the built-in key management.
Most of CORS issues would be mitigated if your features worked in the background of web extensions.
I don't have much time to develop anything beyond the key management, but I'm open to someone else developing the built-in add-on!
Note that it's firefox only, though.
I think it's an idea worth pursuing if you think you can bring new better stuff to the table, but on the other hand it goes against all my (not super strongly held anyway) principles, so I don't know what to say about it.
One more thing I don't know if was clear: App storage is on relays (new spec). I thought of ways to ease the life of not just users but also devs.