Official community for Mlem, a free and open-source iOS Lemmy client.
Rules
FAQ
Pretty much, yes.
I always see this very basic not helpful feature request and wonder why people think that the devs donβt know about shortcomings in a pre-release testflight software and why some (few) people think that entitled nagging makes this community more likeable and the devs work more passionate π
I think people are just getting excited.
I don't think it's an issue as long as people don't start demanding things as if the software were trash just because is missing this or that. If something being missing affects you so personally that much.. then spend the work yourself to implement it or pay some devs to do it for you. It's free and open source software after all, anyone can make their own fork.
And what's more, devs can make pull requests to kbins git repo. So if you're a dev and you want to see certain features, write them.
But then I have to write PHP or JavaScript...
I mean, if you're a programmer, language shouldn't matter as long as you can think logically. After that it's all just syntax.
Fork it and re-write it in Django+Python haha
You might be able to get chatgpt to do it and then just verify it.
Feature ideas / suggestions β entitled nagging.
Feature requests are a good way for developers to know whatβs most important to their users.
I also know the difference as I am a dev. But even as regular user I understand that an early bird software does have a roadmap and key feature will be missing. Pointing out the obvious over and over again is a little bit pointless.
Most of us miss Apollo and other apps that spez killed off. It's understandable.
So far it seems really good! The only thing Iβd like is to hide voted posts, or hide/ignore. Once Iβve seen or dipped into a thread, Iβm done :)
I just want the core basic features to exist:
-zooming in on images -editing/deleting comments and posts -seeing my inbox/comment/post history -dedicated search tab
Yea, usually in open source projects, project management gets ignored more than it necessarily should.
A roadmap detailing goals and outlining MVPs would be very helpful to developer, albeit it can take away from the excitement of not done correctly. Determining low hanging fruit and work that is good for new contributors early one can make a big difference. Allowing those with seniority to tackle the important and hard core featureset while still getting fixes and small improvements out the door.
No user is ever going to ask for a "quick pay" feature. That's such a corporate thing to implement to incentivize users to purchase as conveniently as possible
I think the comic was originally meant as business people requesting features from their PMs. It's just a light-hearted joke :)