QlikView or Qlik Sense?
Two products from the same company evoke questions on the usability and the future roadmap of Qlik products. The question not only arises in the mind of existing Qlik View users but also the prospective data visualization users.
As Qlik Sense (hereafter called QS) is the younger sibling, some of the questions are:
- Would QS replace QlikView (hereafter called QV), sooner or later?
- Is QS a polished version of QV and will make it redundant?
- Should we start using QS, and move away from QV?
- How do they stand against each other?
- Or, should we use both together, catering to different user needs?
Qlik View (actually “Quik View”; Q-Quality, Understanding, Interaction, Knowledge) was introduced in 1993. And, Qlik Sense was launched in 2014. So, we can assume that the customer feedback from the QV experience, has shaped up the QS.
Thus, one of the points which most of the QV users (including me) would agree is the not-so-cool self-service data discovery option. Or, in other words, the ad-hoc analytical requests. QS makes it easier and better for the power users (the term used for technically aligned end-users).
Another major difference is the approach, i.e.:
QS – If a user is looking to reach a desired analytical output and that too without entering into the muddy waters themselves i.e. without dirtying their hands.
QV – Or, if a user wants to explore the possibilities and then discover useful analytics along the direction of the desired output.
As, we see the difference of approach and usage of the two applications we realize that both can co-exist. However, they need to be installed on different servers. Also, they use the same analysis engine.
Thus, as we can now appreciate the features of both the tools, to conclude I can say that:
– “QV and QS” together will work in case of a diverse set of users
– Choosing either “QV or QS” will work based on the user priorities