by squarepeg » Mon Nov 07, 2011 5:25 pm
While your request sounds reasonable from a user's point of view, it is different on the other end.
1) Pretend you are working on a complicated task. Can you say in advance all the difficulties you will encounter? And how long it will take to resolve them? See the problem? Sometimes one feature has to be dropped to allow the working version to progress.
2) If you do make a guess about when you expect to finish something, and miss your target, your users are disappointed. Predicting readiness is nothing but a liability for a developer.
3) Also factor in that Don is in business and must make marketing decisions as well. This is probably why the iPhone version came out before the Android version, even though the later is an easier port.
4) Don has produced the "best of its kind" (maybe the only of its kind) software. I've never been disappointed with the newer versions, and think it is best if we learn to wait patiently. On many occasions Don has given feedback that he wants to include a feature request in the next or future version. But each request has to be evaluated as to its feasibility and cost, which takes time also.
Like other Bliss fans, I eagerly await the next version too.
