Thanks so much for providing this much detail about what you would like to see in the Unbounce page builder. This type of feedback is absolutely crucial for us, and I wish we had more customers like yourselves who were willing to put the pressure on and tell us exactly what their issues are.
The way we approach new product features is a very lengthy and incredibly detailed path. It all starts with validating the issue, which we achieve by researching the most requested features from our customers. In fact, you mentioned…
ÒI think this issue is pushed to the side often because you do not hear from your customers enough about itÓ
… and you’re absolutely right. We’re huge on tackling the features that our customers actually want. In fact, if you take a look at the most requested features in the Community, you’ll see we’ve built and implemented almost every single one of them into our app. The Community is just one of the channels that we use to collect user feedback, of course, but the data usually lines up fairly evenly across customer touchpoints.
With that being said, if the majority of our users are asking for X feature, and only a small fraction of users are asking for Y feature, we’re likely going to attack X feature first. In regards to your specific pain points, other users in our Community have brought up similar requests which you can find here:
Conditional Forms (aka form logic)
Better Page Management
All of these are clearly being validated by other users such as yourself, so it’s clear that we should move forward with these. However, if you were to compare the traction that these posts have received with a feature such as SSL, you’ll see a pretty big difference in +1’s. User demand (among other things) is essentially why we chose to tackle the big features such as SSL, Responsive, Wordpress and Dynamic Text Replacement first, before moving on to the other features.
Many of these features have been quite taxing in terms of time and resources needed to build them. The amount of effort we put in to this process is necessary because we have such strict standards for testing, deployment and overall polished functionality. As much as we would love to tackle all the awesome features at once, we simply don’t have the bandwidth to pull that off. And thus, prioritization has taken place.
Don’t get discouraged though; I assure you there’s light at the end of this tunnel. Now that we’ve knocked the biggest features off that list (and wordpress is just around the corner), we can start to tackle the smaller things such as reporting, better forms, and page management. In fact, the more vocal our customers are about the types of features they need, the faster they will make it on to our roadmap.
In regards to this specific UI tweak, you’re right, this isn’t a feature, this is really more of a builder enhancement that’s geared to make users lives a little bit easier. We have numerous teams within our company that are responsible for different aspects of the builder, and the UI/UX team is responsible for making sure the overall design and usability of the app is as fluid as it can be. I’m happy to say that we’re putting a lot more emphasis on improving our UX this year, but rest assured that this absolutely does not affect the pace at which we release new features. Think of these more as complementary enhancements.
To wrap this up - your feedback is absolutely crucial to us, and we can’t thank you enough for sharing it. In fact, we appreciate your feedback so much that we’d like to invite you to some limited beta’s that we have coming down the pipeline. This way your feedback can be applied directly where it’s needed most; and help us build a better page builder for everyone.
What do you think?