Qlik Community

Ask a Question

Qlik Design Blog

All about product and Qlik solutions: scripting, data modeling, visual design, extensions, best practices, etc.

Announcements
Support Cases coming to Qlik Community Oct. 4! Start chats, open cases, explore resources. Prep for the big move: READ DETAILS
Henric_Cronström

As most of you have noticed – I hope – we have now released a new product.

Qlik Sense.

new_sense_overview-bottom_left.jpg

Qlik Sense is not just a new release of QlikView. Instead it is something different. But there are still so many similarities between the two products, so I thought it would be appropriate to dedicate a blog post to differences and similarities between the two.

Basically, the two products are two different user interfaces to the same analysis engine. This means that old scripts and old formulae will (almost) always work exactly the same way as before. (There are some smaller differences in that Qlik Sense uses libraries, and cannot always use relative paths for files.)

Hence, the two products both have the same Green-White-Gray logic; both use the same calculation engine; both have roughly the same response times; and you should use the same considerations for both when it comes to data modelling. This also means that many of the previous posts here on the Design Blog are just as relevant for Qlik Sense as for QlikView.

But the two products are still very different. And just as a parent cannot say that one child is better than the other, I cannot say that one product is better than the other. They are good at different things:

  • QlikView is a tool for situations where you want prepared business applications, i.e. applications created by developers who put a lot of thought into the data model, the layout, the charts and the formulae; and deliver the applications to end-users who consume the applications. We call this Guided Analytics. The end-user has total freedom to explore data, select, drill down and navigate in the information, and can this way discover both questions and answers in the data. The end-user is however limited when it comes to creating new visualizations. This type of situation will without doubt be common for many, many years to come.
  • Qlik Sense is a tool for situations where you don’t want to pre-can so much. Instead you want the user to have the freedom to create a layout of his own and in it, new visualizations; charts that the developer couldn’t imagine that the user wants to see. You want Self-service data discovery, which means a much more active, modern, engaged user. In addition, Qlik Sense is much easier to use when you have a touch screen, and is adaptive to different screen sizes and form factors. On the whole, Qlik Sense is a much more modern tool.

Finally, it is important to acknowledge that a piece of software is never ready. It evolves constantly:

Qlik Sense today is only the first version of something that will evolve further and get more features and functions as time goes on. Some of the features and functions of QlikView have not yet been implemented in Qlik Sense – there just hasn’t been time enough – but many of them will be implemented in coming versions.

Also QlikView is not yet a "final product". The product will be developed further, and most likely we will see some of the new functionality from Qlik Sense also in coming versions of QlikView. The goal is to use the same platform for both user interfaces.

With these two tools, we believe that we are well prepared for the future.

HIC

90 Comments
Marcio_Campestrini
Specialist
Specialist

Hi Henric

Great post. He helped me a lot about which way to go with the advent of QlikSense. Now I understand that they are two different tools that complement each other and will continue to exist in parallel.

Thanks a lot!

0 Likes
10,706 Views
Not applicable

As Qlik Sense evolves over time, is the strategy to eventually have a single product that is a combination of both Qlik Sense and QlikView or do you feel that there will be a market for both products?

10,706 Views
Not applicable

Yeah, why did you need to make two different products??? Why would you not do this in one product?

"Self-service data discovery", if you work with a QlikView desktop version, you do or can make your own stuff, anyway, not as simple okay, but Sense is not like a revolutionary new concept to me.    


You must have a better explanation plz?     

10,706 Views
amonjaras
Partner
Partner

Sense's ease of use makes the number of people who can "make their own stuff" many times larger than the number that can do it with QlikView Desktop. The concept is not revolutionary; the fact that the Qlik engine is "under the hood" is the real gem here.

10,706 Views
Henric_Cronström

@Lior Abitbol @-Mikael-

One of the main goals for Qlik Sense was to have one unified client that could run on anything  (=html5). Another goal was to generalize the chart drawing code, so that more graph types could be implemented (=extensions). A third goal was that the client needed to be adaptable to screen sizes and form factors.

These three goals meant total incompatibility with the existing C++ client, and - unfortunately - only a partial backward compatibility. So, we had to start developing from scratch, but to re-implement all functionality from QlikView 11 in a new tool would take a very long time. And, we just haven't done it yet...

I am not allowed to tell you what we have planned for the future, but I can see several possible scenarios: Merge the two products. Or, QlikView disappears because Qlik Sense is so much better. Or, the two products continue in parallel: QlikView survives and flourishes since it is much more flexible and allows for a much greater customization and Application building.

We will see. I can only promise that Qlik will listen to the customers and make decisions based on the feedback.

HIC

10,706 Views
egnaldo_sousa
Creator II
Creator II

Thanks for placement HIC

I believe that this uncertainty in the future of our tool can directly affect our customers, what do you think about this?

Egnaldo

10,706 Views
michael_gardner
Creator III
Creator III

I hope to specifically see the Story Boarding in QlikView in the future.  Based on your descriptions of the two products it makes more sense to have Story Boarding in QliKView than in QlikSense.


My only gripe so far was that I told a colleague to d/l QlikView and he instead d/l QlikSense.  Caused for a bit of confusion on the phone.

0 Likes
8,578 Views
senarath
Creator III
Creator III

Hi Henric,

Would it be possible to maintain BOTH the current version of 11.2 and Qlik Sence in the same server.

My primary requirement is that I would need to develop applications for BOTH iPad users (higher Mgt) and desktop user who are at routine operation. Developments for ipad on Qlik Sense platform and Qlikview for others.

How best I could handle this situation.

Thanks

8,578 Views
Not applicable

Splitting the product and not having a clearly defined and published roadmap is going to hurt the company in the long term.  As I work for a large Corparate and we encounter severe issues in the current Qlikview 11 that prevent us classing the product as enterprise ready, and this will just cause more confusion, and doubt about the product offering.

Why on earth would you not spend the developer time fixing bugs and adding functionality to the existing product !

Is QlikSense the final name for the Qlikview Next product?

I will look at the new product, but I feel you have wedged to door open for competitors to get in now.

8,578 Views
robert99
Specialist III
Specialist III

I am not allowed to tell you what we have planned for the future,

Hopefully this will be published soon?

0 Likes
8,578 Views