If I started talking to people about the credit card “platform” I bet I would get a few strange looks. We take it for granted that we can pay for souvenirs with the same credit card in San Francisco as in Singapore. What makes something a “platform” is its ability to openly interconnect with other systems to accomplish much more than what it could do by itself. For example, the credit card platform ties together merchants, card issuers, banks, payment processors, and consumers into one seamless shopping experience.

credit card.png

In the same vein QlikView is a platform. The best way to imagine it is by describing the opposite: a closed system. Imagine a BI product that limits you to only the data sources for which the vendor distributes connectors. Imagine if the visuals you could create are limited to only the ones that come out of the box. Imagine if the visuals you create are stuck in your BI application and can’t be embedded in another application or web site. That would be a very limiting experience indeed. In today’s heterogeneous business environment, no vendor can possibly anticipate every customer’s data or visualization needs.

QlikView is already a vibrant BI platform with a growing ecosystem of more than 1,400 partners. We recently launched QlikMarket, an online solution exchange where QlikView customers can find QlikTech-vetted connectors, extensions, and apps. Connectors provide pre-built connectivity to business applications such as SAP, Salesforce.com, and PeopleSoft, plus social media sites such as Facebook and Twitter. And that’s not to mention the new visualization extensions and apps that are appearing every day.

With “QlikView.next” (the code name for the next generation of the QlikView Business Discovery platform) we’re taking the platform concept to the next level, under the Premier Platform theme. We are investing in QlikView as the heart of an ecosystem, facilitated by QlikMarket.


The four scenarios we are addressing within the “Premier Platform” theme are:

  • No Data, No Discoveries. The ability to access, transform, and manage data is prerequisite to enabling free data exploration and discovery of insights.  QlikView will provide developers with a modern browser-based development environment where drag-and-drop is the norm. Through a library of scriptlets and expressions, your organization can standardize definitions of KPIs and other important calculations.
  • No More Reporting. QlikView is about action- and activity-based decision making. QlikView will allow users to print exactly what they see and tell the data story via an interactive storyboard paradigm. Those who still need to create static reports for audits and record keeping will be able to export data from QlikView to third-party reporting engines.
  • Simplified Partner Deployments. This scenario is aimed at making it even easier for our OEM (original equipment manufacturer) partners to add QlikView analytic capabilities to their products. QlikView.next will include APIs (application programming interfaces) that permit access to QlikView data and visualizations by a middleware server. QlikTech OEM partners will be able to create sophisticated QlikView extensions, use QlikView to drive an associative experience, and create sophisticated mashups that use some of if not the entire QlikView user interface.
  • Unified Platform Interface. Last but not least, this scenario means that QlikView will be exposing the exact API that the native chart objects use to communicate with the QlikView engine. That means customers and partners will be able to create any visualization they can dream of and integrate them with QlikView to the same degree as native QlikView charts.

QlikView is poised to become a BI developer’s dream platform. Imagine integrating with any data source or destination, creating any visualization, and doing it all within an ultra-modern interface. I’m jazzed to see this dream take shape.

To learn more about “QlikView.next,” the code name for the next generation of the QlikView Business Discovery platform, download the white paper, The “QlikView.next” Product Scenarios.