I agree, although I'll point out that I never claimed to be an expert on software development. If you read my observation as condescending (despite the smiley face), I'm sorry. Perhaps it was a little brusque. Or maybe something was lost in translation. Either way, no harm was intended.
But the OP didn't ask a question, it was an accusation! In my mind, that accusation (of broken promises) was unfair.
It seems to me that Omni has been very careful not to promise anything. All they communicated was their plan, which, of course, is subject to change.
I'm no expert, and I'm not talking down to anyone, but I have enough experience to know that software development suffers from second-order ignorance. It's extremely difficult to make accurate plans and stick to them when you don't even know what to plan for. The solution: keep your plans flexible and adapt as unforeseen obstacles present themselves. It seems to me, as an outside observer, that that's exactly what Omni has done.
Again, I'm not claiming to have any special insight into these matters nor to be any more knowledgable than otter or JohnJ80. In fact, as a development manager himself, I'm sure JohnJ80 has dealt with similar issues in his own work.
All I'm saying is that we should assume that Omni is managing these issues to the best of their ability, that they're making decisions based on a variety of factors (some of which might not be apparent to end users), and that Omni has got the best interest of their customers in mind.
Exactly, which is why I suggest we back-off on the accusations of broken promises and give Omni some credit for managing this thing.
I think these are some constructive observations. My only point of contention is that I'm not convinced the metadata column has actually been promised. I haven't seen that language used by any of the Omni folks.
Maybe it just comes down to semantics, but I think we need to have some empathy for Omni's position. On one hand, they really want to let customers know where the app is headed and keep them informed about upcoming features. But on the other hand, Omni has got be careful in managing expectations. As we've seen, it's easy to mistake plans for promises.
So what is Omni to do?
(A) Don't reveal their plans in the first place?
(B) Reveal their plans and manage the backlash when things go awry?
Seems either way is troublesome.
Omni chose the open kimono route on dates and development plans. It's difficult to do this half way which causes confusion. There have been some specific mentions by Omni on versions. I think committing to getting this done with some specifics is the right answer. I appreciate the vacillation on this, especially with the wrench the iPad launch created. Either way, that is a known now, Omni has promised this feature, and it it time to probably talk about what the feature set really is and which rev it will be in - i.e. commit definitively.
So - how about a date and revision. How about we get this feature fleshed out?