1201

Open source devs: please, please add screenshots... (lemmy.world)

submitted 1 year ago* (last edited 1 year ago) by mypasswordis1234@lemmy.world to c/opensource@lemmy.ml

140 comments fedilink hide all child comments

I beg you, if you are a developer of an open source app or program - add screenshots of your app to the README file. When looking for the perfect app, I had to install dozens of them just to see what the user interface looked like and whether it suits me. This will allow users to decide if the app they choose will suit them... Please, don't think about it, just do it....

you are viewing a single comment's thread
view the rest of the comments

[-] OsrsNeedsF2P@lemmy.ml 131 points 1 year ago

While we're at it, I love that you let me customize the settings via a config, but for the love of god make the default config the best it can possibly be

[-] TheHobbyist@lemmy.zip 56 points 1 year ago

This. It should be the most sane configuration and fit most use cases and lead to an experience working out of the box.

[-] charliespider@lemmy.ca 29 points 1 year ago

I contribute to OS projects and work on one full time. EVERYBODY thinks that their obscure use case is the most common (not saying this is what you are doing).

We get users that are completely flabbergasted that our software doesn't offer some feature that is totally specific to their industry and has never been requested even once by anyone else previously. We'll show them our feature request form on our site where you can also view and upvote other requests, and point out that the feature they want has never been requested. They will literally come up with some bs excuse why that is and then insist that we get on it and build out this custom functionality that they need or else they're going to slander us on social media.

Your app doesn't integrate with "didLr"? OMG any decent app integrates with "didLr"!

[-] TheHobbyist@lemmy.zip 7 points 1 year ago

I understand the developer POV too. It's clear that getting the right config for most use cases is a UX problem, which may involve user studies, telemetry to be setup. Perhaps out of scope for most small scale individual projects.

Additionally, I also fully understand that many, if not most of these projects are hobby projects and expectations from users should align with the scope of the project and the resources committed. It's so easy to feel entitled and deserving of high quality projects but they are so time consuming.

My comments were not for those projects but rather mature ones. And contributing to the projects is often the most appreciated way when proposing changes.

In all cases, for any free project, it is always acceptable to answer that something is out of scope, that resources don't allow for the feature to be implemented or that additional help on implementing it are welcome.

People demanding something in exchange for nothing are obviously not the most welcome users :)

[-] GenderNeutralBro@lemmy.sdf.org 14 points 1 year ago

There's a real problem here with backwards compatibility. If you add an option for something, it makes sense to make the default match the functionality of old versions, even if it's not the best for general use cases. That way any tools built on top of it can safely update.

[-] charliespider@lemmy.ca 15 points 1 year ago

Ding ding ding!

That said, the solution is to set new defaults for new installations only and not change existing configs. Users lose their minds (rightfully so) if you modify their existing configs.

[-] RickyRigatoni@lemmy.ml 9 points 1 year ago

I prefer the simple, sane defaults that work for everyone with a heavily commented config file giving detailed information on what each value for each option does, personally. Like MPV's config file.

[-] ccdfa@lemm.ee 5 points 1 year ago

I haven't even touched MPVs config file because I just assumed it would be empty like so much other software I use. Looks like I know what I'm doing tonight.