How about some screenshots?

qweqwe14 5 hours ago | parent | next [-]

I constantly see those projects that would benefit from a screenshot in a readme, but for some reason the thought about adding one doesn't even come to the authors' mind, even though it's pretty obvious. I'd really like to know what's going on.

▲

sakisv 4 hours ago | parent | next [-]

I think the reason is that you can get quite much of a tunnel vision while developing. Everyone involved already knows what they're building and how it looks, so it's very easy to overlook it.

Case in point, I recently wrote a CLI to show which of your AWS infra is not captured in terraform, and you can either print the result as a json to consume by a machine or generate a dashboard with some charts. It took me an embarrassing while to realise that I should have included a damned screenshot in the README, in fact I think I only realised when I wanted to show it to my brother.

▲

IshKebab 3 hours ago | parent [-]

It's also just quite a lot of work to generate screenshots.

	▲	sakisv 3 hours ago \| parent [-]
		That's true as well, especially if you're still developing and changing things - because you tend to realise problems only after you've pushed the new screenshot :P

▲

gbalduzzi 4 hours ago | parent | prev | next [-]

I think in many cases the authors value functionality much more then esthetics.

Which is a bummer because it is a complete different point of view from the more typical user experience

▲

embedding-shape 4 hours ago | parent | next [-]

> I think in many cases the authors value functionality much more then esthetics.

In many cases the repository isn't meant to be more than for source code too, not everyone use their git repository as also the marketing page, that'd go somewhere else.

With that said, grapheneos.org doesn't seem to have any screenshots either, which I also don't understand and think is a bummer. Even though the point of the differences with GrapheneOS might not be mainly visual, just showing what it looks like seem like a no-brainer.

▲

xboxnolifes 4 hours ago | parent | prev | next [-]

An image is functionality, as it provides significant information to the reader.

▲

gremlinunderway 4 hours ago | parent | prev [-]

Yeah but see, we're talking about a functionality that is inherently visual. Ergonomics has nothing to do with esthetics, and it's such a dumb excuse to hand wave aside interface issues as of they are just about "making things look pretty"

	▲	em-bee 4 hours ago \| parent [-]
		exactly, i am looking at screenshots for apps to get an idea about their functionality.

▲

Dig1t 4 hours ago | parent | prev [-]

"A picture is worth a thousand words"

It's like we've had this ancient knowledge passed down for generations but people constantly just ignore it.

▲

why_at 31 minutes ago | parent | prev | next [-]

I just updated mine to try it out, it definitely looks nicer.

https://imgur.com/a/ZGpbqB7

▲

nicolas_ 3 hours ago | parent | prev | next [-]

I was looking for the same thing. Fine! Maybe it’s in the Readme.md. Nothing! Well, ok then

▲

karimabuseer 3 hours ago | parent | prev [-]

Worth raising a PR/discussion on the repo as reasonable chance the devs haven’t even considered it