Qubit from a content point-of-view
November 11, 2016

Qubit from a content point-of-view

Austin Limmer | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User

Overall Satisfaction with Qubit

We use qubit broadly across the business, but in the team that I am part of (Content) we use it use it for updates that would otherwise require an app release - such as hiding promotions that are only available for a short time. We also use it for content that we would like to be shown across all pages like service messages and banner promotions.
  • Instant, preview-able changes that can be performed from anywhere with just a web browser.
  • Makes targeting customers based on specific locations very simple.
  • Timed promotions that would finish in the middle of the night or on a weekend no longer need developer supervision.
  • Service can sometimes go down or become unresponsive and there is little we as a customer can do about it.
  • At peak work hours the updates can sometimes take a long time to show and require a few refreshes.
  • The autosave functionality will sometimes pick up a change mid way through and delay showing the change leading to some confusing errors when previewing the page.
The decision to use qubit had been decided before I joined the team - but it has proven itself to be a very versatile package that has saved us from having to use in-house methods to test and update content. The analytics it provides has also helped us and the wider business a lot.
Qubit is handy if you want to make a quick minor short-term change to the site. We often fix bugs with qubit that we then fix properly later with an app release. Timed and targeted promotions are ideal to do with qubit - especially if they need to end at inconvenient times. It isn't wise to do too many noticeable [promotions] as there is a jump in content between the html loading and the qubit js loading.