In that particular thread that is linked, we have a problem with certain types of transactions that is affecting at least 2 of the 3 users there reporting issues (which are in this thread). I suspect this pattern is present across a lot of support requests. I whole-heartedly agree that we need to get the app working for those users, but they still represent a small portion of our userbase -- those that are participating in pooled mining.
It's not the userbase the participates in certain types of pooled mining that is the issue. The issue is that Armory won't work for some typical transactions (one input, lots of output addresses). There are many applications of this and it will only be more common.
Sorry for being so adversarial today. I like what you guys are doing.