Preview New QuickBase UI code name

  • 1
  • 2
  • Question
  • Updated 2 years ago
  • Answered

QB Email received titled Exclusive Look: Preview the New QuickBase Experience

Product Announcement

Preview New QuickBase UI

Watch as we announce the next iteration of the QuickBase user interface, codenamed Mercury, at our recent user conference.

Features:

  • Productivity
  • Cross-device consistency
  • Simplicity

Having been with QB during the last major UI change is there any way (or will you be) setting up a preview of site in current and new as was done last time. There where a few of the changes that required modification to roles, pages and even forms. Need ample time to review !!!

Photo of GLF

GLF

  • 10 Points

Posted 3 years ago

  • 1
  • 2
Photo of QuickBaseCoach App Dev./Training

QuickBaseCoach App Dev./Training, Champion

  • 62,944 Points 50k badge 2x thumb
I understand that QuickBase has a plan to gently transition which will be announced in the Fall.  We are all eager to try it out on our own apps, but their cake is not yet baked.
Photo of QuickBaseCoach App Dev./Training

QuickBaseCoach App Dev./Training, Champion

  • 62,944 Points 50k badge 2x thumb
The direction of Mercury has pivoted to be a new platform initially targeted at New Builders.  Quick Base (with a space) will continue to be strongly resourced for enhancements and the Road Map for QuickBase was outlined at EMPOWER.
http://www.quickbase.com/quickbase-blog/empower2017-whats-new-in-quick-base
Photo of Eric Fulmer

Eric Fulmer

  • 80 Points 75 badge 2x thumb
Thank 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?
Photo of QuickBaseCoach App Dev./Training

QuickBaseCoach App Dev./Training, Champion

  • 62,944 Points 50k badge 2x thumb
This was never a new feature or a new UI. It was a new Architecture platform.

I believe that Rick Willet, the new CEO, got in there with fresh eyes, benefit of the engineering team now better understanding what would be involved in a migration, and realized that forcing a generally happy customer base through a difficult forced migration was not a viable business plan to grow the business.

So yes they certainly did a pivot in their strategy and I for one as a developer and I'm delighted. The Quick Base we know and love will continue to get regular enhancements for the forseeable future and Quick Base can experiment with the new product to see if they can get growth in their user licenses with it.

Some of the enhancements for Mercury will be useful as infrastructure for QuickBase classic as well. An example of this would be the whole area of governance and management of users, which is very important to getting more acceptance from IT Managers at large companies. . These enhancements are common to both platforms but only need to be developed once.
Photo of Eric Fulmer

Eric Fulmer

  • 80 Points 75 badge 2x thumb
"This was never...a new UI."

Gideon Ansell, Quick Base Director of User Experience, called it "a new UI" at least 5 times 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.
Photo of QuickBaseCoach App Dev./Training

QuickBaseCoach App Dev./Training, Champion

  • 62,944 Points 50k badge 2x thumb
The reality is that there was no feasible way to migrate apps from the current Architecture to the new Architecture. That was not known or at least not comprehended by senior management at the time, hence the Pivot.

So in that sense, you are quite right. Their Plan A did not work, so they moved on to Plan B. Plan B will be much more incremental.

Continue to improve Quick Base Classic.

Roll out Mercury by prioritizing features one by one, until at some point it becomes practical for developer to have a real choice as to which platform to use for developing a brand new application which needs most of the features that QuickBase now has.

Maybe sometime in the future those three platforms will converge, who knows.
(Edited)
Photo of QuickBaseCoach App Dev./Training

QuickBaseCoach App Dev./Training, Champion

  • 62,944 Points 50k badge 2x thumb
typo correction
Maybe sometime in the future those two platforms will converge, who knows.