topic Re: Best practice for developing mashups in QlikSense in Visualization and Usability

Best practice for developing mashups in QlikSense

razvan_brais — Wed, 19 Apr 2017 12:03:09 GMT

Hey guys . I want to know what is your opinion about what to use in developing qlik sense mashups. I saw that I can use React.js , Angular.js or Node.js .

Which is better and why?

Can you please give me some suggestions?

Thank you.

Re: Best practice for developing mashups in QlikSense

simondachstr — Wed, 19 Apr 2017 12:24:18 GMT

I don't think you should develop mashups unless you really have to - stick to native Qlik Sense wherever you can.

Re: Best practice for developing mashups in QlikSense

razvan_brais — Wed, 19 Apr 2017 12:28:17 GMT

The problem is that i really have to develop mashups for my apps. Thats why I`m asking with wich technology to develop mashups.

Re: Best practice for developing mashups in QlikSense

Anonymous — Wed, 19 Apr 2017 13:05:15 GMT

Razvan

Personally I tend to use BootStrap and / or AngularJs in MashUps. I can't see any reason why you should not use ReactJs if you have experience with it and like it, but I am not sure Node.js would be appropriate.

I am now veering towards Martin's viewpoint of avoiding MashUps where possible - and if needed use bespoke extensions within native QlikSense. Except where things will be used on smartphones, as I personally do not like how native QlikSense behaves / renders on smartphones.

Notwithstanding that could you give some background as to why you wish to develop MashUps and what kind of end game you are hoping to achieve.

Re: Best practice for developing mashups in QlikSense

razvan_brais — Wed, 19 Apr 2017 14:02:40 GMT

Thank you Bill ,

We are now in the research phase on what technologies to use , that`s why I was asking what to use. What I want to develop in mashups are buttons , inputtext and some table behaviors or things like this , which I won`t find in regular QlikSense objects.

Re: Best practice for developing mashups in QlikSense

Anonymous — Wed, 19 Apr 2017 14:13:32 GMT

In which case I'd agree with Martin and suggest you go for Out Of the Box QlikSense and if needed bespoke visualization extensions.

In my opinion this approach will give more re-usability of any time, effort and money spent on bespoke visualization extensions. As opposed to MashUps which by definition are tailored to a specific needs and cannot be reused.

Re: Best practice for developing mashups in QlikSense

razvan_brais — Wed, 19 Apr 2017 14:16:16 GMT

Can you please give me some links to read about bespoke visualization extensions?

Re: Best practice for developing mashups in QlikSense

klausskalts — Wed, 19 Apr 2017 14:25:00 GMT

I find that the 'old guys' - like myself - tend to stick to Qlik build in functionality .... but mash-up's can deliver some great functionality too .....

Re: Best practice for developing mashups in QlikSense

simondachstr — Wed, 19 Apr 2017 16:41:11 GMT

Native QS on smart phones is a misery.

Re: Best practice for developing mashups in QlikSense

Anonymous — Wed, 19 Apr 2017 17:20:26 GMT

A good place to start is Qlik Branch if looking for extensions that are mostly open source and free. But bear in mind - if it is free then there are usually no guarantees or formal support.

This section of the online help is worth a read, https://help.qlik.com/en-US/sense-developer/3.2/Subsystems/Extensions/Content/custom-objects.htm

Vizlib | Qlik Sense Extension Library have extensions that are supported by the supplier, but good commercial extensions with support will never remain free - although there will probably always be freebie tasters and samples.

..... other sources, opinions & options are also available.

Best wishes for the journey you are starting on - whatever direction you choose I hope you have fun & succeed.

Re: Best practice for developing mashups in QlikSense

paulcalvet — Thu, 08 Jun 2017 20:56:15 GMT

Hi Razvan,

I developed a mashup with Angular.js for my work.

I downloaded this example on Qlik branch http://branch.qlik.com/#!/project/56728f52d1e497241ae6986a‌ and I transformed it.

In order to simplify the code, I use master item when I want to display a graph, so I maintain it in Qlik Sense.

If I want to display simple text, I use an hypercube with a callback fonction (Callback function for a measure).

Paul

Re: Best practice for developing mashups in QlikSense

razvan_brais — Thu, 22 Jun 2017 09:42:13 GMT

Thanks a lot guys.

Re: Best practice for developing mashups in QlikSense

Anonymous — Thu, 29 Mar 2018 10:58:00 GMT

How come you recommend not building mashups?

As a data scientist and a javascript developer - I've reviewed many reporting softwares and qliks main advantage in my opinion is the mashup capability - without that, Power BI destroys qlik.

Imagine making a SaaS Dashboard for a client with a full login capability - permissions for different departments etc. - going to a client with just qlik sense desktop is insanity in terms of providing real value - even worse for cloud as custom extensions dont translate there.

How do you guys develop full solutions for your clients - (yes I understand deploying a web app is alot of work but wouldnt it make you stand out from other BI developers/analysts?)

Just sharing some ideas... maybe there are limitations I'm not aware of?

Re: Best practice for developing mashups in QlikSense

ABQuintanilla — Thu, 03 Dec 2020 23:30:00 GMT

If you are serious on enhancing the User Experience (and money backs you up) I don't see why not?! MASHUPS do require MORE... but certainly take you to a whole new level.

Re: Best practice for developing mashups in QlikSense

lureilly1 — Tue, 16 Feb 2021 11:22:46 GMT

If you are planning to build mashups in React, check out my project https://www.motor-js.io/.

It's free, open source and will make things super easy if you have some React experience.