Quote:
Originally Posted by petermillard
Perhaps the software's being written by people who only read books?? Not everyone needs/wants to annotate, bookmark, highlight, search or even use a dictionary with their their ebooks - I don't - even if you see these as core requirements of a reader application. Which isn't to say that the developers are right not to accommodate these features, but perhaps they want to concentrate on making a good reading app to start with?
|
I decided to trim my response in order to avoid opening a can of worms. I will just leave it at this: If I only designed products based on what I was personally concerned with, I would limit potential profit and user satisfaction. When one takes on the task of developing a new product, they have two choices: 1) build a new product with new features that pulls users from other existing platforms because this new product is
better, or 2) build a similar (or same) product and employ intense marketing to make sure people use your product rather than theirs (aka. Apple tech).
Part of development is understanding your user base. The features you mentioned are not hard to implement. Leaving them out is just silly.
Quote:
Originally Posted by petermillard
You don't say which reading app you're using, but perhaps you could petition the developers to add the features you need?
|
The features I desire have been brought up over and over with most of the major reader and application designers. God only know why they keep designing Frankenstein'ed devices/application with only
some of features people really want. I understand costs involved, but there is so much potential to "own" the market if a designer just designs a product with
all the major features people expect and want. *Le sigh*