Learn about what's new across all of the products in our growing Qlik product portfolio.
The new 2019 Qlik Statement of Direction is now available. The Qlik Statement of Direction provides a comprehensive overview of our company, products, and vision for the future.
This document is freely available for download at https://www.qlik.com/us/qlik-statement-of-direction for anyone that wants an overview of our company and products or a look into our roadmap.
1 Word -- Exciting
Unable to download the pdf doc
by far the most interesting part ;
.".and new big data capabilities such as Associative Big Data Indexing"
Suggestions for QlikSense - mini forum - Wishlist
A word of criticism from my side. We invested at an early stage in the adoption of Qlikview since we believe in the associative approach. Through the years we enjoyed working with Qlikview. However, since Qliksense entered the market Qlikview seems to stop its development. The releases contained less and less innovations through the years and our developers complained that the Qlikview forums and Qlikview resources were pushed into the background. Okay, we convinced ourselves we should accept it as we also could move slowly over to Qliksense.
Now, switching over slowly to Qlikview requires additional licences and fees. As an early adopter and supporting Qlik we are now confronted with an offer from Qlik that doubles license fees. How unfair, the Qlikview roadmap is showing almost no innovations, Qliksense more and 5 releases. Hey guys from Qlik how about rewarding the early adopters and offer Qliksense for free to make the transition. Place yourselves in our shoes. Since we have to make the transition - since Qlikview is overtaken by other technologies – we can explore the market with an opener mind.
So, I still believe in the Qlik roadmap and the total stack is really great. However, in my eyes, Qlikview slows down its development too much which positions IT departments with Qlikview in a fragile position. Recognize them !! and offer a transition fee that is fair*. A "buying twice" feeling is not a constructive way to help them.
(A true supporter of Qlik Technology)
@Christopher_Ilacqua Can you look at this and either help respond or direct me where I should go. Thanks!
Thank you for your post and appreciate your feedback. We have some exciting news on QlikView and Qlik Sense that we will be sharing at Qonnections this year. There are two planned releases of QlikView this year. Our goal is to unify our Qlik platform and reduce TCO.
Glad to chat directly on your concerns.
Thank you for reaching out. One of our biggest concerns is that our audience (using Qlikview) is confronted with ‘non Qlik technologies’ that in their eyes is more state of the art compared to the possibilities in Qlikview. Qliksense seems to keep the pace compared to others since it embraces D3.js and an open architecture that allows third parties to offer plugins for charting and scripting. Qlikview slowed down in this direction which forces us to make a non-voluntarily investment to follow our audience's expectations in modern charts and graphics.
I like to hear from you and learn if Qlikview is going to keep the pace that our audience expects. How can we manage contact?
You bring up some excellent points on the shifting expectations of modern BI platforms. Our goal at Qlik is to protect your investment in BOTH Qlik Sense and QlikView. To that point you will see the rollout over the next year of services & product enhancements in the following areas:
1. Dual Licensing to reduce the cost of using BOTH products
2. Extend the support of QV11.2 so that customers can plan appropriately their upgrade/mix strategy between QlikView & Qlik Sense
3. Unification of the user experience in accessing BOTH QlikView & Qlik Sense apps from the Hub
4. In the near future allow you to blend the consumption of Qlik View & Qlik Sense apps in a modern cloud based architecture.
More to come... Qlik realizes that the issues are as much business issues as technical and will be providing a holistic offering that will allow customers to mix/blend and/or migrate applications based on YOUR business requirements.
Hope this helps...
Again, thank you for reaching out.
It is the combination of point 1 and 3 that would help customers like us that (still) prefer on-premise Qlik technology. Please realize that it is hard for us to understand why a Qlik positions QlikSense and QlikView as two products. This creates a paradox in making investments, for example, should I continue to develop my Qlikview app since I see that Sense is heading towards … , or, in the other direction should I develop in Sense as we see in Qlikview more ….
So, blending is one step in making this paradox less complex for customers. However, the silver bullet would be a complete merge of both in one excellent product that is more than its sum.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.