How important is the "Feedback" feature of your public site?

I found something that's not right about formatting when trying to compose a gmail today. Been the constructive person I am, I want to report to google team of the problem, but to my surprise I can't find they "submit a bug" link! I first bottom of the page, no links. Then looked under Help Center, found a link to "Common Issues", but it's not listed there. There is a suggestion link, but I am not suggesting a "make-a-billion-dollar-for-me" ideas, I have a bug to report!. So coming back under "Known Issues", nothing listed there, but there is a link "Don't see your issue listed above?" clicked and then "check out our Troubleshooter ", now what? nothing listed under those links! It's not until a co-worker of mine told me that under this very page, if you click "Registration & Invitations", then you will see "I'd like to report a new issue"!!!!

OMG.... all that to get to http://mail.google.com/support/bin/static.py?page=troubleshooter.cs...

This is from the giant google of user friendly centric company! What happen there? I hope someone here will tell me that, No Z, you missed here.

So the question is how important is your public webapp to let user to get feedback to you? and what steps did you tried to make sure you get user's opinion heard?

Thanks,
-Zemian Deng

Views: 56

Reply to This

Happy 10th year, JCertif!

Notes

Welcome to Codetown!

Codetown is a social network. It's got blogs, forums, groups, personal pages and more! You might think of Codetown as a funky camper van with lots of compartments for your stuff and a great multimedia system, too! Best of all, Codetown has room for all of your friends.

When you create a profile for yourself you get a personal page automatically. That's where you can be creative and do your own thing. People who want to get to know you will click on your name or picture and…
Continue

Created by Michael Levin Dec 18, 2008 at 6:56pm. Last updated by Michael Levin May 4, 2018.

Looking for Jobs or Staff?

Check out the Codetown Jobs group.

 

Enjoy the site? Support Codetown with your donation.



InfoQ Reading List

Docker Kanvas Challenges Helm and Kustomize for Kubernetes Dominance

Docker has launched Kanvas, a new platform designed to bridge the gap between local development and cloud production. By automating the conversion of Docker Compose files into Kubernetes artefacts, the tool challenges established solutions like Helm and Kustomize. Developed with Layer5, it marks a shift toward Infrastructure as Code, offering visualisations to simplify cloud-native deployments.

By Mark Silvester

Intel DeepMath Introduces a Smart Architecture to Make LLMs Better at Math

Intel has announced DeepMath, a lightweight agent built on Qwen3-Thinking that specializes in solving mathematical problems. To address common limitations of LLMs in math reasoning, DeepMath generates small Python scripts that support and enhance its problem-solving process.

By Sergio De Simone

JEP 525 Brings Timeout Handling and Joiner Refinements to Java’s Structured Concurrency

JEP 525, a highlight in the upcoming JDK 26, refines structured concurrency for clearer, safer task management. This iteration introduces a timeout callback for custom joiners, enhancing flexibility and error handling. With streamlined APIs and focus on practical usage, it empowers developers to efficiently manage concurrent tasks, paving the way for advanced Project Loom features.

By A N M Bazlur Rahman

Presentation: Thinking Like a Detective: Solving Cloud Infrastructure Mysteries

Brendan McLoughlin shares a detective’s framework for solving cloud infrastructure failures. He explains the "usual suspects" in the network stack - from DNS to API gateways - and discusses how to apply Richard Cook’s "How Complex Systems Fail" to modern observability. He shares strategies for building robust runbooks and using tools like Honeycomb and OpenTelemetry to find hidden timeouts.

By Brendan McLoughlin

Article: Engineering Speed at Scale — Architectural Lessons from Sub-100-ms APIs

Sub‑100-ms APIs emerge from disciplined architecture using latency budgets, minimized hops, async fan‑out, layered caching, circuit breakers, and strong observability. But long‑term speed depends on culture, with teams owning p99, monitoring drift, managing thread pools, and treating performance as a shared, continuous responsibility.

By Saranya Vedagiri

© 2026   Created by Michael Levin.   Powered by

Badges  |  Report an Issue  |  Terms of Service