It’s been a while since I’ve posted about how a developer can get started with Qlik, so I figured it would be a good idea to review current tools and resources for developers new to Qlik.
A good place to start would be the Getting Started on the Qlik developer help page. There’s some links here to get you started building mashups, extensions, and widgets. There’s also information about creating connectors, building Windows applications, and automating administrative jobs. You can use the navigation on the left to explore. One thing that can be easily missed but may be really useful for someone new to Qlik Sense is the Concepts section, which will explain things like generic objects, hypercubes, list objects, and other concepts that are really essential to Qlik. Also, don’t miss out on the Videos you can find here.
When you feel like you’re ready to build something, Getting started building mashups with Dev Hub is a good place to jump in. I wouldn’t recommend trying to build production-level mashups in dev hub unless it’s simple, but it’s a good place to just get a feel for the Capability APIs. You can see how the Capability APIs are loaded and accessed, what a connection to a Qlik Sense app actually looks like and can embed a few objects or create a few cubes or lists and see what that code looks like. From there, you can check out the Capability API Reference and try building a mashup without using the dev hub. Here’s a great quick reference for Connecting to the Capability APIs.
One thing you need to understand is that the Capability APIs simply provide the ability to embed visualizations and communicate with the Qlik Engine. But if you just want to communicate with the Qlik Engine and you don’t need to embed visualizations then using the Capability APIs is probably not the best choice. You should check out enigma.js, which is an open source library for communicating with the Qlik Engine. You may also want to check out other Qlik Open Source projects, such as picasso.js, a library for building visualizations that is optimized for use with Qlik.
Whether you’re using the Capability APIs or enigma.js (or even some other way) to communicate with the Qlik Engine, you’ll definitely want to keep the Qlik Engine Reference handy.