Open source devs: please, please add screenshots...

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…

SwingingTheLamp,

Hey, all you folks ought to get together and publish a guide to writing good FOSS documentation,

vacuumflower,

A README file is usually comprised of text.

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

Thisisforfun,

README markdown files allow for inline image links to be “expanded”

shaked_coffee,

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)

crate_of_mice,

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,
@Blurghglurgh@lemmy.world avatar

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

That’s pretty ignorant

crate_of_mice,

That’s quite an accusation. Can you elaborate further on that please.

Blurghglurgh,
@Blurghglurgh@lemmy.world avatar

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

mbw,

I find this unnecessarily derisive. There are good reasons for a UI or README not being user-friendly, the top-most one being (imo) that it is really, really hard to get right, takes a lot of time and doesn’t primarily solve the problem the project was started for.

crate_of_mice,

You mean you think I’m being derisive? I think it’s important to remind people that not every open source dev shares their priorities, or indeed any interest whatsoever in whether other people use their code.

This whole post is filled with a really disappointing amount of entitlement and lack of self-awareness.

mbw,

I think you generally can’t know if someone shared their code with the intention that others may use it, but it’s a reasonable assumption.

andruid,

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.

emergencyfood,

README is usually a text file. While some platforms can now use markdown, that is nowhere near universal. So it might be better to ask for screenshots to be put on the website / wiki.

FrostySpectacles,

GitHub and GitLab both support inserting images into your README.md. Here’s the syntax:


<span style="color:#a71d5d;">!</span><span style="color:#4183c4;">Description of the image</span><span style="color:#a71d5d;">
</span>
Nioxic,

Just like obsidian.md

Anafabula,
@Anafabula@discuss.tchncs.de avatar

And anything that supports CommonMark. It’s even in the original Markdown

Pyroglyph,
@Pyroglyph@lemmy.world avatar

And Lemmy!

GlenTheFrog,
@GlenTheFrog@lemmy.ml avatar

Not just a text file, a markdown file. And markdown has supported images since forever

OfficerBribe,

README.txt will be a text file, README.md can be much more

maudefi,

No. ReadMe files should be concise, explicit, and text only. UI/UX screenshots can be part of the repo, wiki, or associated website but they shouldn’t be in the ReadMe.

If you don’t understand the software you’re installing from some rando stranger’s git repo then you shouldn’t install it. Period. Take the opportunity to learn more or use another tool.

Git repos are not app stores. The devs don’t owe you anything.

The vast majority of software in publicly accessible git repos are personal projects, hobbies, and one-off experiments.

Your relationship with the software and the devs that create and maintain it is your responsibility. Try talking to the devs, ask them questions, attempt to understand why they constructed their project in whatever specific way they have. You might make some new friends, or learn something really interesting. And if you encounter rudeness, hostility, or incompetence you’re free to move on, such is the nature of our ever-evolving open-source community.

We bring a lot of preconceived notions into the open-source / foss / software development space as we embark on our own journey of personal development. I try to always remember it’s the journey of discovery and the relationships we curate along the way that is the real prize.

hellishharlot,

For a lot of open source at the moment the root level readme is fundamentally the homepage too. It absolutely should include screenshots, maybe even a gif. If your software has a GUI or TUI it should follow that a concise visual will do more to explain it’s usage than a text document

FrostySpectacles,

As a user, I completely agree. People often make decisions in a few seconds, and you’ve done all this work developing an app. That little extra step will allow you to make a difference to more people!

As a developer of a Lemmy web UI, I’ve been thinking about adding screenshots to my README for weeks but still haven’t done so 🙈

Nioxic,

Get to it, mate! You can do it!

FrostySpectacles,
hellishharlot,

It’s easier said than done for sure

MonkderZweite,

I prefer install instructions. Not everything is in AUR.

gianni,

I think this ties in to the grander idea of: please provide information that is helpful on a nontechnical plane of thinking. It goes a very long way

noodle,
@noodle@feddit.uk avatar

Sometimes I’d settled for a simple description of what the tool even is. Sometimes the readme is just straight into compilation steps and I feel like we’re rushing into something.

Nioxic,

A lot of documentation is like that.

Its terrible when the software is called some random word that has nothing to do with the programs functionality

kite,

I also hate it when it has a name that is a super common word or phrase. Our last 3 records management prograns at work have been like this, and their help fires are terrible to non existent. Good like trying to search the internet for information on the software with those common names. Even adding terms relevant to what the software does, didn’t help much.

(Apologies if this is terribly typed, I’ve got an impending migraine aura that stayed right as I hit reply and have lost a good chunk of my vision. I can’t see most of what I’m saying.)

01189998819991197253,
@01189998819991197253@infosec.pub avatar

Unrelated, but I used to get them often. I found one article about vitamin D deficiency as a potential cause, and figured, “what what hell”. Started taking 5000IU every day of the Swanson’s brand. It took a month or so, but I’ve been aura migraine free for months (still get migraines sometimes, but they’re MUCH less severe than they used to be and no auras). Ask your doctor first, in case you can’t take vitamin D, but it’s worth a try if it’s safe for you.

kite,

I actually know what causes most of mine, there are some nerves in my neck that get pinched/aggravated and trigger them. And for some reason, if I have multiple days in a row where I don’t get much sleep, those nerves get extra cranky. They are extra cranky right now.

01189998819991197253,
@01189998819991197253@infosec.pub avatar

I’m so so sorry! I guess, at lease, you know why. That’s something, right? Not really, but :shrug: seriously, I’m so sorry you’re going through that!

Shadow,
@Shadow@lemmy.ca avatar

Foreplay is important! Gotta get me excited for that app.

QuazarOmega,

🛠️ Building

To build the app install the gamete dependencies and run the following


<span style="color:#323232;">make child
</span>
randint,

100% agree! I always get so frustrated when there are no screenshots in the README.md or on the site.

Dave,
@Dave@lemmy.nz avatar

On github you can even paste your screenshot right from the clipboard. Zero excuses for not having a screenshot.

flop_leash_973,

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

xT1TANx,

Wait what? I thought the read me file was to put as little info as possible to prove how awesome anyone was who can use the program.

shalva97,

Including the documentation link, which only has incomplete getting started section

pivot_root,
Getting Started
  1. Clone the repo
  2. Install dependencies
  3. Compile the project: TODO
  4. Copy the executable to /bin
  5. Add your app.json config to ~/.config/app*
  • IMPORTANT. APP WILL NOT RUN WITHOUT THIS
droans,

Oh hey, they have an example.app.json file. Let’s check that out!


<span style="color:#323232;">{}
</span>
skankhunt42,
@skankhunt42@lemmy.ca avatar

TODO

leraje,
@leraje@lemmy.world avatar

Also, installation instructions that don’t assume you’re already an expert.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • opensource@lemmy.ml
  • DreamBathrooms
  • magazineikmin
  • hgfsjryuu7
  • Youngstown
  • khanakhh
  • slotface
  • vwfavf
  • mdbf
  • rosin
  • kavyap
  • ngwrru68w68
  • PowerRangers
  • thenastyranch
  • everett
  • Leos
  • InstantRegret
  • GTA5RPClips
  • osvaldo12
  • ethstaker
  • modclub
  • cisconetworking
  • tacticalgear
  • Durango
  • cubers
  • normalnudes
  • tester
  • anitta
  • provamag3
  • All magazines