nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qghwaehxw309aex2mrp0yh8qunfd4skctnwv46z7qg6waehxw309aexjcn09ejh2tnwdaehgunfvyhxzurs9uqzp5daxvenwv7ucsglpm5f8vuts530cr0zylllgkwejpzvak0x2kqmehusjv was built with this purpose, to grow the user base on Nostr. It does everything you list in a single app, simply because I'm a firm believer in "super apps". The ideology of one specialized app for one single purpose is not what users want or need. Unreal Engine has more and more features embedded into the editor, reducing the need to learn multiple tools to do your tasks, which is mentally exhausting.

Back in the day when we built Windows apps, we all copied what Microsoft did (especially the file menu). This was to reduce mental load on the users.

These days, everyone is doing their own fancy UI ("thanks" to AI), as a way to get the attention of users.

Nostria is built on Material Design guidelines, making it feel like "home", for anyone on the Android ecosystem, while also introducing some Apple design cues.

It is a solid foundation for future development, it's basically just me developing it and the quality is almost there for wide adoption. Few more tweaks and improvements, and then get the final Play Store approval. Been waiting 4 months for that.

Reply to this note

Please Login to reply.

Discussion

This is awesome work! The UX benefits of consolidating functionality are real.

Though I have concerns about super apps as a concept - they're kind of an authoritarian's wet dream. We see this in China where they become centralized control points. Even with non-custodial architecture, the more functionality you concentrate, the bigger the target for capture.

The complexity creates maintenance burden that makes it harder to keep things truly decentralized and neutral. More features = more attack surface, more dependencies, more reasons for compromise.

Not a critique of Nostria specifically - clearly valuable work. Just thinking about the broader architectural tradeoffs between super apps versus more composable, specialized tools.

It for sure is easy to fall into the trap of just making some centralized services and you have "lock-in" and user migration/export becomes hard or impossible.

I do my best to keep Nostria as compliant to the protocol and stay away from centralized services when possible. It creates extra challenges to ensure good UX and be decentralized, but I've built this for so long that I know a few tricks.

There is a Game API for stream details, Notification API for managing web push notification settings, Account API to check Premium status and last one is Image Service, which compresses profile photos (can be disabled in settings).

https://nostr-ux.com

Your ideas are great but mostly not protocol related. When you enforce these by the protocol, it gets less neutral.

nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcqyqt79zylhgqsy8gy3gfl6zappzknrsuryc54gcxzre5ug0agl0j32r5td2a will be interesting to see it release. I made an account on browser just now to check it out. I am interested to talk to a dev about a client I will create. I like nostr:nprofile1qy2hwumn8ghj7etyv4hzumn0wd68ytnvv9hxgqgdwaehxw309ahx7uewd3hkcqpqyfg0d955c2jrj2080ew7pa4xrtj7x7s7umt28wh0zurwmxgpyj9sldm58v , but there are some things about it, specifically it being off protocol realistically, that I don't like. This client would have that integration as part of it. But the UX/UI on wavlake is solid. I released a track on there to see what its all about.

https://wavlake.com/album/cf2d1559-8c0a-45a1-9320-4e40b752e652

In the about section of Wavlake it mentions RSS? Nostria already supports podcast and music if you have an RSS feed. I want to improve these features and add more options for discovering music, podcasts, etc.

I'm interested in different opportunities; it will likely take a while to get enough premium subscribers to sustain myself.

https://mibo.eu.nostria.app/5876b89c5bf9c9a2c067437bc6665cbc1e47049926511a78f409aa5d458f6ff3.mp4

Ah, just noticed the RSS icon. Why does this not appear everywhere?

https://mibo.eu.nostria.app/a6071dbfbc70d7d5423fd1753cca6b7bb55bc18a8897f814232542a73aa5e16c.webp

This has a different type of RSS format, had to implement support for it. Here it is in action:

https://mibo.eu.nostria.app/3a5f907a9feac90b7843ea5754b3991d16d4a0ccb351b36fd18ba4279f342004.mp4

I can imagine. As a producer having a solid way to release music with some form of... Oh no, he didn't say... royalty structure would be step in... a direction.

Not saying the old models are good, but there are parts that could be salvaged and maybe updated.

I love the idea of v4v. It's an honest, if a bit nieve, way to receive support as an artist. I have a bones structure for what it could look like to take it a bit further and attach licensing options for zaps as a way to encourage that support.

Nostr is primordial ooze, so watching people add and take away from these concepts will be interesting.

So far my single has traction with tons of plays and downloads. So DJs are grabbing the track to add to their sets and people are listening, which is great.

That has yet to produce a zap ⚡. So with that many plays on Spotify I many only get $.000001 cent so far for instance. But that is value of some kind beyond being able to say "cool man, people like this."

Ultimately, this is not a gripe. Just note for people like you looking to attract investment in dev.

My label(s) would be happy to enter into a beta agreement with a dev and offer fresh releases while testing ways to monitize that build our sats, the devs sats and returns that value to the following.

Monitary systems are always complex, even more so when art is involved.

#nostria #wavlake #heuristic #stacksats