Hello World.

“A knotty puzzle may hold a scientist up for a century, when it may be that a colleague has the solution already and is not even aware of the puzzle that it might solve.” — Isaac Asimov

Open source is in no way a new idea. Depending on who you ask, open source is either the result of passionate developers looking to buck the system by creating freely available technology projects, or an efficient way for developers to be mutually selfish.

I honestly don’t care why a developer contributes to open source, because whatever the motivation, open and communal development offers a great opportunity for true innovation. Ideas build on one another, code is forked and branched, bugs are squashed, and things get done.

With the advent of Qlik Sense, Qlik has given developers direct access to the powerful associative QIX engine. A myriad of APIs were introduced which allow developers a range of possibilities, from simply embedding an out-of-box chart to creating a custom client to powering a website.

This was great news to me. There is nothing a developer hates more than restrictions, and now we can create any kind of custom visualization we want. We can leverage JS libraries like d3 and angular. We can communicate with other solutions like R and Node.js. Essentially, we can fit Qlik Sense into our project to build the application we want.


Right, but what is Qlik Branch?

For developers, Qlik Branch is a place to share and collaborate on projects and innovations created with Qlik products in an open source philosophy. All projects posted are required to have the code readily accessible, and the projects must be downloadable directly from the site. In short, everything on the site is free to use and free to modify in the spirit of Open Source.

For everyone else, Qlik Branch is a place to find and download solutions for your Qlik Sense or QlikView projects. If you’re looking for an extension or customization, you might find it on Qlik Branch, and if not, you could most likely find a developer to build or support anything you need.

But, this is just the beginning, and there is much more to come. Qlik Branch is only as useful as the developers that contribute. Beyond sharing or creating new projects, we’re looking to begin featuring content from developers that will benefit the community as a whole. Perhaps you have some insights and/or tips regarding our APIs, feel that a deep dive into a project you’ve built would be insightful, or just have a point of view that would be interesting to developers. If so, please contact branch.admin@qlik.com to get involved early as we enhance the site.

There is much, much more planned for Qlik Branch in the future, and we’re eager to get working. In the spirit of open source, I would not consider Qlik Branch to be a complete concept or project, but rather the root of something larger that could take us in any number of exciting directions.

Thanks for joining us.

Brian Munz
@brianwmunz

For further information on Qlik Branch, please visit our “About Qlik Branch” page here.

Like what you read? Give Alexander Karlsson a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.