UI team more like self oriented (Pay me and I fix any small random bugs and develop some new features from Core) and BTS++ team more focus on community need(Features that highly demanded now and Bugs that blocking users having good user experience). If UI team fail to learn from BTS++ team, then nothing will change.
The approach from BTS++ team and UI team was/is quite different. BTS++ does private discussions and management to define what they do next. Advantage is that they seek proactive feedback (and also get it because they are included in chinese community), disadvantage is that there is no transparency whatsoever to the outsider (not even I would know where to look).
The UI team has done everything managed publicly through the GitHub repository (
https://github.com/bitshares/bitshares-ui). The advantage is full transparency and accountability, and also a public well-defined development cycle. The disadvantage is that it was expected that the community gives feedback by opening an issue in the repository (it was always open for all, anything that I have seen I have created an issue mostly myself).
In that sense, BTS++ collects private feedback proactively, and UI team collects public feedback passive (proactive for anything that I saw). So in that sense I strongly disagree with your statement I quoted above, especially since the current worker proposal addresses your concerns.