Skip to main content

Buggy UI/UX software will get no bug reports?

Experience-1

"One client has praised the UI of Burrow for more than half an hour", my boss told me once. It's no surprise for us as even Airbnb was adopting many of the features introduced in our software. Sometimes we used to get petty, trivial feedbacks as bug reports--then we used to wonder how and why clients are pointing out even these tiny dots.

Experience-2

Some long time ago, someone brought me shopping cart software and its UI was big mess. When I pointed out messy UI, the person told me that it must be rugged at core level... but software was so buggy--even basic functionality of the cart system didn't work.  We then wondered how such buggy software is surviving.

Possible reasons

I think there are couples of reasons why poor UI software will get less bug reports:

  • Poor UI means rugged core? I think, people wrongly associate poor UI with solid core.
  • "Shouldn’t expect more" attitude. Some people may underestimate the knowledge of the coders on seeing poor UI and they may learn not to expect more from such guys.
  • Good UI means more happy usage. When the software has good UI, they may find it happier to use it lot and so finding tiny issues.
  • Expecting more from good UI. Some people may expect more from the developers of good UI (e.g. Flickr, etc). So, they can't stop reporting even tiny dots.
Labels:

Comments

Post a Comment

Popular posts from this blog

BehaviorS.js - An alternative to Behaviour.js, event:Selectors and Low Pro libs for unobtrusive JavaScript programming

BehaviorS.js yet another unobtrusive JavaScript library similar to Behaviour.js and event:Selectors but in implementation uses hash based lookup without extending elements; so presumably it should be faster than the rest. The original script and idea was by JLof ; I extended it for DOMContentLoaded support, optimized a bit to avoid scanning of more depths, and added new rules support. I wanted to document the plug a long time and just got time to do it. For the time being BehaviorS.js is available here Update (2006-09-11) : Coralized the link to BehaviorS.js so as to save the load on free brinkster.com webpage Update (2006-09-27) : If the coralized link to BehaviorS.js doesn't work, use http://www21.brinkster.com/guideme/BehaviorS/ Update (2025-06-07) : Now available in https://github.com/rrjanbiah/behaviorsjs
17 comments
Read more

RTaKeyman Bookmarklet v2.0

RTaKeyman The above bookmarklet is for English to Tamil transcription. This should work like a Input Method Editor on web page forms. The first version I tried didn't work well and so this bookmarklet version. Version 2.0 2004-12-27 1.0 2004-12-12 Usage Make a bookmarklet with the above link. Point to a web page where you want to enter Tamil characters and click the bookmarklet. This will initialize the keyman for that page. Then start typing on the forms; RTaKeyman will transcribe the characters whenever it sees a space, carriage return and tab. To-do Turning on/off keyman (i.e., to enter both Tamil and English). Help and other user interfaces. Credits Sundar for informing the necessity and for being a beta tester
5 comments
Read more

Solved: "Ports" Tab Not Visible in VS Code (WSL2)

None of the solutions I found on Reddit or GitHub worked, and most of the related GitHub issues were locked. So I'm documenting this here for future reference. Problem When using WSL2 in Visual Studio Code, the Ports tab—needed to access your application in Windows browsers like Chrome or Edge—doesn't appear. Even the Ports-related options are missing from the Command Palette. Solution After a lot of trial and error, here's what worked: Run npx serve in the VS Code terminal. It will output a URL such as http://localhost:3000/ . Click the link (or use the Follow Link option). This will open the app in your default browser. You may notice that it opens on a different port (for example, http://localhost:64198 ). At this point, the Ports tab becomes available in VS Code. After this initial trigger, the Ports tab seems to remain available in future VS Code...
Post a Comment
Read more