I always struggle with this type of response on UX issues. They always seem to think the 'how' is important, and that the length of time that takes is also important.

It's not.

You don't need to explain how to do it, you don't need to make an argument on time to implement - unless the time to implement is insanely high.

Use the language of business: You are losing prospects by creating work for them. Resolving this will help your sales funnel. Over time this could be worth substantial revenue, and contribute to the ultimate survival of your product. That is worth a lot more than how long it takes to implement or how to do it.

I've found in most (all?) aspects of my life, trying to tell other people how to deliver feedback is usually the wrong approach. The better thing is to take the feedback regardless of how it's delivered and learn to interpret. Things are implied. Feedback on A, may actually be point at a problem with Z. Sometimes the correct way to interpret is to discard. The source of feedback is not going to connect those dots for you.

That said, I see your point but I will try to defend mine. Your language of business sentence is basically implied by the pure existence of my complaint right? Should I have to type every implication out in order to provide any feedback? And this being a tech place for tech people I wanted to emphasize how simple it would be to correct (I don't really even know if the creator/app owner is reading, so it's more of a general feedback for other people who build products.) Highly subjective either way. Hell, the app owner could argue they don't care about people that don't manually type in the info because they're not really potential customers. I don't know if I'd fully agree, but it could be a form of lead qualification in which your business language feedback would not hold weight. It's at least somewhat true, because I was just curiously kicking the tires. I have no use for this product.

Apologies it was directed, I did mean it more as a generalization and it didn't come across that way sorry. Off for the morning coffee now :)

No worries, feedback is such a highly subjective topic

Sorry, just have to do this..

--- I always struggle with this type of response on feedback. They seem to think that how feedback is given is important, and that the phrasing also is important.

They don't need to explain the business impact, you don't need to use the perfect words, unless it's insanely subtle.

Use the language that takes the least amount of time and effort. We don't want you to forego on giving feedback, since that may push you to not give feedback at all, resolving in substantial lost in quality, and contribute to the ultimate destruction of your product. The fact that you share insightful feedback is a lot more important than the exact words.

-- It's the job of the business people to listen and analyze the business impact of things.

As a counterpoint, having to log in makes it feel more like a real live demo, and not some mockup from the marketing department.

I think auto-fill would strike a good balance here.

After all, I want login screens to look nice and come up fast, too.

while i 100% agree with you that our demo (hi! i'm author 2/2 of this software) should just log you in without asking for credentials... we're 100% focused on the product right now, and being near the top of HN was a huge surprise to us as well.

we are working on ironing out the UX of our site (it's a single column of text, that we whipped together in an hour, so we could focus on building the software). so it's completely a work in progress at this particular moment.