Quote:
Originally Posted by PinkET
The Kobo Glo is in my opinion a nice piece of hardware, uncomplicated, pretty solid and it potentially could get the job done if it wasn't for the Kobo developers, in particular the one or ones designing the UI. … This eReader has little functionality hardware wise; no sound, no multimedia, no backward compatibility to consider, no 3rd party software, no (real) games, no plug an play hardware (except for a SD card) … It is such a simple piece of hardware to write code for, it is embarrassing to see how the Kobo team is struggling to come up with a solid, intelligent UI for it..
|
I agree, the hardware it self is solid, the firmware isn't.
Most ereaders are build from the same hardware components, like a processor from the TI OMAP series, a Freescale i.MX50x series processor, flash memory etc. Most readers are almost identical or very similar to OEM reference designs with only some minor changes.
Hardware wise, design and build quality are they main differences between devices.
Quote:
Originally Posted by PinkET
Pressing the brightness icon doesn't give you direct control over the brightness anymore. You have to press on a second brightness icon to access the control.I wonder how many extra presses that will mount to per year? Well, it's double the amount that's for sure. (not to forget every press uses up a bit of your battery)
|
Even while the build quality of Kobo devices are solid, the light button is the most freqently used button of the device and this button is probably the weakest hardware part of the device. Is this button durable enough to be pressed so many times? And as you have to press and hold before it becomes responsive most users probably will automatically use a considerable amount of additional force than is really necessary.
Quote:
Originally Posted by PinkET
The brightness control is not conveniently on the bottom of the screen anymore where I could swipe it without moving my hand while continuing reading. It is in the middle of the screen now, eliminating both mentioned advantages in one go. … the search-box that is occupying the whole width of the screen … there is no topbar in Sudoku, so there's no way to access the brightness settings … the Sketchpad opens without any UI, meaning you are stuck in it and only a reset of the Glo can save you. … When you turn on wifi the wifi icon disappears from the bar … Why are programs like Sudoku under settings in the first place? … I can turn down the light in only 6 steps …
|
To generalize, some basic problems are mentioned:
- the screen position of adjustable settings, the display of information etc.;
- the size of these boxes are unnecessary wide;
- menus or settings are not accessable;
- information is not displayed when in use (e.g. wifi icon);
- impractical usability because you have to tap many times to change some settings because these are located in a unlogical place (e.g. "Extras" in the settings menu) or complicated navigation (tap many times) to change a setting.
That's why it isn't always very
practical when you try to use (features of) a device.
This has nothing to with (potential) trade offs or choices that have been or not been made. No, they occur because (additional) features were added, changed, improved or whatever else resulting in enhancement over enhancement or addon on addon on addon. Features are just "parked" somewhere in the exisiting menus to test(?) (some) of its functionality (e.g. "extras" in the settings menu). But afterwards hardly ever reviewed if a feature is placed in the most logical menu location or if it is easy to use (e.g. accessable and whithout many navigational taps)
These are legit, general issues. And not limited to the issues mentioned by PinkET.
Developers develop, testers test, users use the device. Yes, I know, there is alot of overlap here. All I'm saying using a device isn't necessarily testing or developing. Testing and developing involes every part of the device but the main focus is on the technical side: does it work or not and if not, how to fix it. Whether a feature works or not does not mean it is also practical in use.
These general issues mentioned here, comments about firmware releases and bugs elsewhere on this forum are the reason why I canceled my preorder of de Kobo Aura HD. It is just not maximizing its potential.
The Kobo Aura HD is - just as Kobos other ereaders - build of general available parts and therefore I assume that competitors will release similar devices. A real side by side comparison will decide which ereader I'll buy.