this post was submitted on 14 Aug 2023
1122 points (97.7% liked)

Open Source

31114 readers
1 users here now

All about open source! Feel free to ask questions, and share news, and interesting stuff!

Useful Links

Rules

Related Communities

Community icon from opensource.org, but we are not affiliated with them.

founded 5 years ago
MODERATORS
 

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....

(page 2) 50 comments
sorted by: hot top controversial new old
[–] crate_of_mice@lemm.ee 11 points 2 years ago* (last edited 2 years ago) (4 children)

There's an awful lot of comments in this post from people complaining that developers aren't making their projects attractive and user friendly enough, or the READMEs descriptive enough.

Can I just say, as a developer with some open source projects on github, I don't care; you're not my intended audience.

[–] Blurghglurgh@lemmy.world 3 points 2 years ago* (last edited 2 years ago) (2 children)

I don’t care; you’re not my intended audience.

That's pretty ignorant

load more comments (2 replies)
load more comments (3 replies)
[–] Gallardo994@lemmy.world 7 points 2 years ago (1 children)

To be fair, most of time you can just Google %appname% screenshot. I understand that this is not as convenient as having screenshots in the readme, but eh, it's not as big of a problem when you realize this.

P.S. I do actually add at least one screenshot for my software. Maybe because sometimes UI is one of the main focus, idk. I just feel like it.

[–] CoderKat@lemm.ee 5 points 2 years ago

I think that doesn't work for most smaller projects. That'll work for something like Firefox, but there's little reason for random, unheard of tools to have an image on the web. Plus the naming of some projects is super generic, which can make it hard to find correct images.

Some software changes appearance often, too, and google is bad at knowing what up to date is. It can be really easy to find wildly out of date images as the top results.

[–] Winn_Addison@lemmy.ml 7 points 2 years ago

TURE...👍

[–] flop_leash_973@lemmy.world 6 points 2 years ago

Don't forget to assume what works on macOS also will work fine on a Linux server deployment.

[–] 13@calckey.world 5 points 2 years ago (3 children)

Where should I store the screenshots? In a screenshots folder in the repo? Should I update them at some time? Should I screenshot both light and dark theme?

[–] moritz@lemmy.deltaa.xyz 9 points 2 years ago (1 children)

Where: In the repository, most projects seem to use media or screenshots as the name of the directory.

How often: Whenever a big change happened or many small changes have accumulated.

What: Light theme suffices. I only care about the general look and feel, not about specific colors.

That’s how I would do it for my own projects.

[–] moritz@lemmy.deltaa.xyz 4 points 2 years ago* (last edited 2 years ago)

As an example, an old Android project of mine: https://github.com/moritzruth/JamRSS

I showed one screen in both the light and the dark variant to demonstrate that the app generally has support for dark mode.

[–] xamboni@lemm.ee 9 points 2 years ago* (last edited 2 years ago) (1 children)

That’s one option, or use imgur.

Update them if your UI has significantly changed or does not adequately represent the final product.

If having a light/dark theme is an important feature or highly requested feature for your project, it would be nice to show it off.

Screenshots can, most of the time, get away with showing just the default configuration. Share what a user would see when opening your project for the first time, and assume they used the default configuration. Optionally, if you offer a lot of customization, show what it could look like if someone spent a good amount of time personalizing things!

[–] jelloeater85@lemmy.world 10 points 2 years ago

Please don't use a external image host, have it live with your code in /docs

[–] CoderKat@lemm.ee 5 points 2 years ago

Yes. Git can store binary files fine. It's not the most efficient for storing them, but it works, especially for a small number of screenshots. For updating and theme, that's entirely up to you. It's all a judgement call. If you want to show off your functionality (like a dark mode), I encourage you to include screenshots of it. If you substantially change your UI, update the images.

You don't have to update for every new button you add. It's more about giving a general impression of the UI. Is it minimalist? Is it a chaotic mess? Does it look like it fits in naturally with whatever OS appears to have been used? Does it look like any thought was put into UI and UX? Those are the kinds of things you're trying to answer.

[–] vacuumflower@lemmy.sdf.org 5 points 2 years ago (1 children)

A README file is usually comprised of text.

Other than that - usually if it has a webpage, it has some screenshots.

[–] Thisisforfun@lemmy.world 3 points 2 years ago

README markdown files allow for inline image links to be "expanded"

[–] MonkderZweite@feddit.ch 4 points 2 years ago

I prefer install instructions. Not everything is in AUR.

[–] andruid@lemmy.ml 3 points 2 years ago

Anyone know of good Gitlab CI or GitHub actions for auto generating GUI screenshots and links them in the README? I only barely know testing tool and frameworks like OpenQA and Robot for GUI. Even better if we can get AVIF/GIF linked in there to see an app in motion.

Honestly though, documenting is a pain enough, I really don't want to be doing screenshot walk throughs on anything I'm not paid to do.

[–] shaked_coffee@feddit.it 2 points 2 years ago

I totally agree that screenshots and a proper description of the app in the README are a must-have for all foss apps, but as a developer I know that most of the times you prefer use your time to add new features to your app rather then documenting existing ones...

Personally I'll try to add them to all my future projects but what I would suggest to everyone who use and love a foss app is to check out its README and, if needed, submit a pull request with an updated version of it with screenshot etc (You don't need to be a developer to do that and it can be really appreciated)

load more comments
view more: ‹ prev next ›