ContributionsMost RecentMost LikesSolutionsRe: Preview New QuickBase UI code nameThis was never...a new UI." Gideon Ansell, Quick Base Director of User Experience, called it "a new UI" at least 5times at the Empower 2016 Product Keynote. It was absolutely clear that QB intended to change out the UI with the goal of "your same apps running in the new interface" (Gideon's words). He repeatedly says the current "classic" UI is problematic due to inconsistency across devices, it's slow, it's too complex, it doesn't show enough data on screen, and it's not adept at localization(And he's right on all counts). You can watch the video if you don't believe me, skip to 37 minutes in: https://www.youtube.com/watch?v=CMxu_Hs-f0I So rewriting history that Quickbase users are perfectly happy with a UI from 2012 staying on for the foreseeable future, and this pivot will all work out great for everybody with two different architectures, is just pure spin.Re: Preview New QuickBase UI code nameThank you for the update. This does not reflect well on QB's ability to manage and deliver on their own roadmap. A year ago, they believed they could migrate existing QB apps to Mercury gradually, starting with the simplest ones. Clearly, they since figured out they would never be able to migrate more complex apps, and abandoned that strategy altogether and will now have two (seemingly) incompatible products instead). The concern is that this is their own platform-- how can they be this unsure how a new feature will work?Re: Preview New QuickBase UI code nameCan anyone provide an update on the status of the new UI beta testing process? It seems to me that the Mercury UI has been pushed off multiple times. I'm beginning to wonder if we'll ever see it in production.