Quote:
Originally Posted by fjtorres
In the tech world, decades of product design successes and failures have shown that letting marketting types write the specs for products leads to failure every time. That is why the techie mantra is K.I.S.S. - "Keep it Simple, Stupid". The proper, time-proven solution isn't kitchen sink specs; it is market segmentation. Different products, each optimized for its intended mission and audience.
|
Sorry, but having techies design products has also led to many product failures due to a failure to focus on the market or non-techie end user. And I haven't seen any evidence that EPUB 3 was driven by marketing or that EPUB 3 Lite is not.
I think the biggest problem with the EPUB 3 standard is that it was drawn up by a committee. Design by committee often leads to bloat because there is no one to say "no". There is no product designer to make the hard decisions about what the design needs, what would be nice to have but might not be technically feasible, and what the design doesn't need.
Quote:
Originally Posted by WillAdams
Because of course, if there isn't time and money to do it right the first time, there's always a way found to do it over after everyone is exhausted by yelling about the errors.
And, those superscripts directly set in ePubLite will be properly handled by a screen reader, right?
|
You can't, as the saying goes, let the perfect be the enemy of the good. If one feature desired by <1% of the user base causes 99%+ of the user base to have no product for two more years, you need to get rid of that feature and let the rest of the product move forward.