youronlyone on Nostr: The beauty of the #Soapbox frontend for #Nostr is that it makes it very easy for ...
The beauty of the #Soapbox frontend for #Nostr is that it makes it very easy for users to enter the Nostr mycelium network (or #Nostrich(?) for short).
The UI is familiar, especially for those who have used or using Soapbox as their frontend for #Mastodon and #Pleroma. Or, are using the #Rebased backend (from the same team as Soapbox).
I like this approach of separating the frontend and the backend. The team can build any backend, first was Rebased for the #Fediverse and now #Ditto for Nostr, and use the same frontend that users are familiar with already.
It reminds me of the same attempt to separate the frontend from the backend back in the #Xaraya days (a fork of #PostNuke which itself is a fork of #phpNuke CMS). In a way, it reflects two types of developers:
1. Backend developers, who are usually either too focus on the backend and they don't have time for the frontend; and/or designing the frontend is not their thing.
Let's be honest, this is a common thing in many projects.
2. Frontend developers. They are the ones who concentrate on building for the user, ensuring the UI and UX are aligned, and the software is easy-to-use for ordinary users.
Think of it this way:
1. Backend devs are the architects and engineers who develop houses and buildings. (And in some circles, developers are called engineers too.)
2. Frontend devs are the ones who design the building from inside out. Because, after all, we can't deny that looks matter. It is the first thing people talk about and what attract customers.
These two goes hand-in-hand, and the way I think of it, if development for these two are separate, it also opens up a lot of possibilities. Which, Soapbox has proven. You don't like the default Pleroma and Mastodon frontend? Then use Soapbox.
Interestingly, Nostr itself is built on that. It's one network with different frontends and backends. While they are not totally separate, a Nostr account can be used for any other Nostr platform.
The UI is familiar, especially for those who have used or using Soapbox as their frontend for #Mastodon and #Pleroma. Or, are using the #Rebased backend (from the same team as Soapbox).
I like this approach of separating the frontend and the backend. The team can build any backend, first was Rebased for the #Fediverse and now #Ditto for Nostr, and use the same frontend that users are familiar with already.
It reminds me of the same attempt to separate the frontend from the backend back in the #Xaraya days (a fork of #PostNuke which itself is a fork of #phpNuke CMS). In a way, it reflects two types of developers:
1. Backend developers, who are usually either too focus on the backend and they don't have time for the frontend; and/or designing the frontend is not their thing.
Let's be honest, this is a common thing in many projects.
2. Frontend developers. They are the ones who concentrate on building for the user, ensuring the UI and UX are aligned, and the software is easy-to-use for ordinary users.
Think of it this way:
1. Backend devs are the architects and engineers who develop houses and buildings. (And in some circles, developers are called engineers too.)
2. Frontend devs are the ones who design the building from inside out. Because, after all, we can't deny that looks matter. It is the first thing people talk about and what attract customers.
These two goes hand-in-hand, and the way I think of it, if development for these two are separate, it also opens up a lot of possibilities. Which, Soapbox has proven. You don't like the default Pleroma and Mastodon frontend? Then use Soapbox.
Interestingly, Nostr itself is built on that. It's one network with different frontends and backends. While they are not totally separate, a Nostr account can be used for any other Nostr platform.