←back to thread

314 points CharlesW | 3 comments | | HN request time: 0.517s | source
Show context
Carrok ◴[] No.42201300[source]
Why do so many projects fail to include any screenshots at all?

Maybe the authors don't think it's necessary, but step 3 under `Getting Started` is called `Creating UI`. Why would they not show what the result of the tutorial looks like?

replies(4): >>42201503 #>>42202073 #>>42205183 #>>42209182 #
xixixao ◴[] No.42202073[source]
Screenshots are harder to produce, maintain and publish.

I also suspect many technical authors are less “visual” so to speak, putting less emphasis on visual presentation.

replies(3): >>42202385 #>>42203350 #>>42206078 #
jamager ◴[] No.42203350[source]
> Screenshots are harder to produce, maintain and publish

What, really? What am I missing? If you tell me video, yes, but a screenshot...

replies(1): >>42203530 #
1. madeofpalk ◴[] No.42203530[source]
I don't think it's that hard, but it's easier for screenshots to drift and become out of date compared to just written text documentation.
replies(2): >>42203709 #>>42207731 #
2. high_na_euv ◴[] No.42203709[source]
It is literally a few minutes of effort

If you cant do such basic thing, which would significantly improve an ability to understand your product, then wtf

3. conductr ◴[] No.42207731[source]
You’re just trying to give us the gist of things with images. It’s basically selling your thing to me as something I would want to try out. Usually if I connect with something I see in first few moments then my likelihood of trying the thing out is higher.

We don’t need it to be updated on every commit. Or illustrated docs but some idea of what I’m getting myself into is nice to have.