Stake article, page-10

While I agree with you, failing to deliver is infinitely better than releasing a buggy product. There's examples everywhere in the tech world of software being released buggy and the audience getting in an uproar over it. Just look at the gaming industry for very clear cut examples. And the reason I mention that demographic is because I believe it overlaps quite nicely with SWF's target audience. Add to the mix the fact that it involves large sums of money and it's the perfect mix for a storm if released buggy.

As a younger person, I've experienced plenty of software releases and can safely say myself and my peers prefer a delayed, solid and complete release over an on-time buggy release.

The fact they've delayed the release tells me they care more about what the developers and system engineers are saying over the targets that corporate or management have set; which leads me to believe it should be a solid, complete release. This gives me (and the peers I've spoken to about it) MORE confidence in the company, not less, because they're actually listening to the people creating this thing instead of tunnel-visioning on deadlines.

The only thing I wish they did better was communicate. Yes setting a date is impossible, but giving an idea of where they're at in their overall development pipeline would go a long way. For example, they might not have any issues at all with the app. Apple may have declined the release due to not following their material design guidelines in which case they just need to tinker with design and not the underlying implementations. Or they might have X amount of critical bugs and Y amount of non-critical bugs after the beta testing.