View Single Post
Old 07-05-2009, 11:40 PM   #52
emellaich
Wizard
emellaich ought to be getting tired of karma fortunes by now.emellaich ought to be getting tired of karma fortunes by now.emellaich ought to be getting tired of karma fortunes by now.emellaich ought to be getting tired of karma fortunes by now.emellaich ought to be getting tired of karma fortunes by now.emellaich ought to be getting tired of karma fortunes by now.emellaich ought to be getting tired of karma fortunes by now.emellaich ought to be getting tired of karma fortunes by now.emellaich ought to be getting tired of karma fortunes by now.emellaich ought to be getting tired of karma fortunes by now.emellaich ought to be getting tired of karma fortunes by now.
 
Posts: 1,101
Karma: 4388403
Join Date: Oct 2007
Device: Palm>Ebookman>IPaq>Axim>Cybook>Kndl2>IPAD>Kndl3SO>Voyager>Oasis
What a mess ...

... that Bookeen finds itself in. The firmware update is useless if it doesn't have folder support and enable the delete button. No, it must support epub and mobi in the same version. Better menu structures? Font size changes?

All of these make sense, although even for them the definition of good design is open to interpretation. Better menu structure according to who?

The problem is that Bookeen pushed out an unfinished firmware (e.g., unassigned buttons) and thus left the expectations of follow up releases. Then they dangled the promise of updates over a long time. Our over-active imaginations supplied the rest. Each of us imbued the hoped for release with the factors we each desired. The new release was something different in my eyes versus yours. When each of us expressed a desire for the upcoming release we each envisioned something different, but we thought we were talking about the same thing. Whatever Bookeen delivered was bound to disappoint everyone.

They would probably have been better off with no updates, and to ask us to be satisfied with the features we originally purchased. Or, there were two alternatives. They could have embarked on a rapid release cycle - releasing new features every months. Any given release may not have contained specific features needed for every individual, but the promise of new features would always been a month away. The other alternative would have been to set the expectation purposefully low (realistic?). A long term release plan with firm dates once a year, and specific features announced for each release. In this case, the release plan may not be to the taste of everyone, but there would not be the disappointment when the releases arrived.
emellaich is offline   Reply With Quote