Replying to Avatar SondreB

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.

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.

Reply to this note

Please Login to reply.

Discussion

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.