Arshad, thank you for compiling this list! I did a similar thing for Salesforce 6 years ago when we were still using that platform before we switched to QuickBase in 2015. It ended up being 12 pages long! They were impressed enough that I got a 30 minute conversation with their VP in charge of development. He was effusive in his thanks for so much good feedback. And then ... after 3-1/2 years of waiting, not a single item was knocked off my list. So I respectfully told them I was leaving. And they had the gall to contact me after I gave my notice and ask me which item(s) on my list could they try to implement to keep me. Too little, too late....
QuickBase, on the other hand, iterates much more frequently than Salesforce, and so far over the last 2-1/2 years, I have been very pleased with the updates. Many have been relevant to my app and have saved me time or enabled me to implement planned updates, without the need for extensive coding.
I agree that the UserVoice communication mechanism feels less useful and less relevant to me than it should. And I do not like having my votes limited to some arbitrary number! A good suggestion is a good suggestion, and I want to promote as many good ideas as I can that are relevant to my needs. QuickBase seems somewhat accountable to what we are saying there, but there isn't enough transparency about which suggestions they are taking seriously and planning on doing vs. those that they will not attempt to implement. We never get to know anything until they are done and the feature has been implemented, and for some of the good ideas, it can take 5 to 10 years. This needs to get better!
I would love it if Development showed us on a relative time frame what they are working on and have planned. Obviously things change and time frames might have to adapt. That's programming. But not telling us anything until something is fully implemented is not really good communication. And good communication is more important than ever today in fostering enduring client relationships.
