Quote:
Originally Posted by Josieb1
I get that it bugs you but the functionality works, it's just cosmetically they don't match.
|
I'd like to add a few sentences to my previous comment:
If you sell a car, then what's the first things you do ?
You wash, clean and polish the car - if necessary fix engine, scratches and bumps - to add some monetary value to it.
The basic functionality is to be expected like this:
It's a car... it drives... the customer expects it as functional feature of the car. Otherwise a normal customer wouldn't want to buy it at all. It's the polish that usually drives the "buy" or "no-buy".
But let's wait for the next Kindle firmware update. Maybe some concerns are being addressed till then. My hopes are, that the one or other Kindle developer keeps reading these pages and forward user concerns to the team.
Edit: Besides that, who says it's "low priority" ? The person who works in the quality area (or software texting area) usually works with the "quality handbooks" that usually are part of the contract with the customer who pays for the product.
We usually make an written offer to the customer. The customer either agrees on it or not. That offer usually contains the requirements (software requirements) that the customer wishes that the software should do and the quality it sould have (quality requirements). The quality requirements are not just software tests (press button A should do this and that but not this and that) but also the quality requirments for product documentation and the GUI itself.
You can even get raw sketches from the customer in how the window and GUI should look like. So saying "low priority" is just a matter of general agreement between customer and software company creating the product. Other customers may make it a "hgh priority" to have the GUI look consistent and not fragmented, to not confuse their user base.