I've been building a tool aimed at better web annotations for teams and AI collaboration at https://viewall.io/
Having worked with web facing teams there are always vastly different methods any individual uses to capture their feedback. If you or anyone you know on Mac that has 100s of screenshots on their desktop, this is aimed at bridging the gap.
Clipboards are optimized with context for LLM markdown ingestion and for use in work suites like Jira/Confluence.
Still fairly early, but I've been using the tool to help build the app itself which has been an enlightening experience.
You'd be hesitant to trust a brand if it can't keep consistent styling. Branding helps users identify a brand and believe it or not the aesthetics of a brand make a great deal of impact on consumers.
As others have said, your point comes across as "let's remove design who cares" because design and human computer interaction roles stopped where your understanding ends. Everything looks the same to you after all (it doesn't, you just haven't noticed it affecting your decision making).
The common recommendation I've seen is to use your network. If it's something you're building then ideally you know what problem you're solving and who has that problem. Then getting those early users you know with that problem involved to test and give feedback, you can then optimize further for that audience and need. From there those users will likely share with those that they know within their own network having the same issue. There's a few books on it like Tribes by Godin (though not everyone agrees of course).
Other than that there are a few places that highlight product launches like product hunt, etc. to gain initial usage. Probably check for niche groups having the issue and reach out organically - no one likes spam.
This is just what I've gathered from others, I'm in the beginning phase of this myself :-)
I can't tell if you're serious or not, but tables are an absolute mess to handle layout.
Email clients handle the CSS code to varying degree of support when wrapping responsively so even if you think your layout looks good with wrapping it's because CSS influenced the layout in whatever particular client you are using. If client doesn't support CSS or the CSS properties you've used: jank email. Email unfortunately requires you to code like 1999 in this regard.
Browsers having CSS as standard and relatively up to date is a very good thing. Tables that aren't representation of tabular data are a mess.
It's actually really simple to use tables to handle layout once you're used to it, like I said, it's what we had to do with email for a long time.
It does take some css, of course, but only width and max-width. That's basically it to turn a table responsive. Add the dir attribute and you can also control the stacking order of elements.
My point being, working in a constrained way (like with email) allows you to make the most of the properties available to you, and it turns out tables for layout (semantic issues aside) are easy to grok and work predictably and reliably.
Having worked with web facing teams there are always vastly different methods any individual uses to capture their feedback. If you or anyone you know on Mac that has 100s of screenshots on their desktop, this is aimed at bridging the gap.
Clipboards are optimized with context for LLM markdown ingestion and for use in work suites like Jira/Confluence.
Still fairly early, but I've been using the tool to help build the app itself which has been an enlightening experience.