Pixelfed, a decentralized alternative to Instagram, has launched its official mobile apps. The service today runs on the same ActivityPub protocol that
There are tons of apps which don’t have a dark mode and you are writing off fediverse app just because it doesn’t have it. Fediverse apps should be supported instead being judged harshly.
And I don’t use them, either. I’m a contributor to multiple Fediverse projects, including Lemmy-based apps and full identity management with ActivityPub. We do not deserve to get held to lower standards if we want the Fediverse to grow, especially when it comes to features that are about things like eye comfort, which can be a mild accessibility issue for some.
Dark mode is a basic necessity in apps today. It’s not a convenience, but a necessity for adoption. There are many people who are going to open the app, then never use it again because of something that’s bog-standard in the libraries and should only take a few hours to work in, which should have been done before an announcement.
So yes, I speak up, because I want this to succeed.
@corsicanguppy@lemmy.ca, @'ing you so I’m not responding in two places 😉 I appreciate the work of the team, but it doesnt change the fact that to many, this is a showstopper and I’m pretty surprised it wasn’t considered as a basic UX requirement pre-launch (see other comments in response to you).
There are tons of apps which don’t have a dark mode and you are writing off fediverse app just because it doesn’t have it. Fediverse apps should be supported instead being judged harshly.
And I don’t use them, either. I’m a contributor to multiple Fediverse projects, including Lemmy-based apps and full identity management with ActivityPub. We do not deserve to get held to lower standards if we want the Fediverse to grow, especially when it comes to features that are about things like eye comfort, which can be a mild accessibility issue for some.
Dark mode is a basic necessity in apps today. It’s not a convenience, but a necessity for adoption. There are many people who are going to open the app, then never use it again because of something that’s bog-standard in the libraries and should only take a few hours to work in, which should have been done before an announcement.
So yes, I speak up, because I want this to succeed.
@corsicanguppy@lemmy.ca, @'ing you so I’m not responding in two places 😉 I appreciate the work of the team, but it doesnt change the fact that to many, this is a showstopper and I’m pretty surprised it wasn’t considered as a basic UX requirement pre-launch (see other comments in response to you).