Some thoughts on your questions?.....
1. Your right the main difference is the UI which allows dashboards to be displayed in responsive environments over the old way. Thereare also data stories and master items which are new features worth exploring.
2.qlik view is the more mature feature rich tool so if you want tried and tested fully costomisaboe dashboards than view is your tool. If the look in mobile environments is important then look at sense. It's still building it's feature set up but it looks great and is certainly the future.
3. View is developer focused and sense is business user focused Although developers can use sense and visa versa.
HOpe these help
Thes links should help you understands the difference in depth.
I will endeavour to answer your questions...
Still I have some queries & doubts about Qlik product, below they are --
1. What is difference between QV & QS?
QV will provide the developer with a substantial amount of power when building data visualisations , mostly due to the large amount of attributes available to tailor the user experience , because of this vast feature set it is not the best for User Self Service experiences, but the ability for mobile integration is in my opinion somewhat limiting, although QV 12 may be better than QV11 now, I have yet to experiment more.
QS on the other hand provides a more easily accessible data visualization development for self service and the mobile experience as it's all HTML5 based, plus there is a large library of easily integrated extensions. My last client site uses QS Server and we integrated many D3 and other extensions to provide the user with what they required, this was much easier than QS.
2. When should I use QV / QS?
That's not a question I could answer quickly as it depends on the delivery expectation of your client/business. From my recent experience QS still has a way to go at the Enterprise level, we did have many annoying traits that stonewalled us during development, however I believe QS will mature and provide rapid/agile development capability in the near term. The ability to share on QlikCloud as well is a real boon, especially when this offering becomes more commercialized.
3. What will be the role of developer, while developing application using Qlik?
Despite the advertising and marketing that QS is simple and easy to use, it still can be confounding for the self
service user , as to do any advanced calculations within the product, the user must have a grasp of advanced expressions , set analysis, data modelling (associative) etc. So there will always be a role for the developer in my
opinion when the deliverable becomes a more advanced requirement.
4. Can you please list down some verticals or companies using Qlik now.
There are many listed on the Qlik web site, but in Australia I am aware of banks, health departments, Telcos etc using Qlik tech products..
5. Do you have any test case, which minimize decision making time from months to days?
Sorry not available, mostly these are confidential Biz Cases internally. From my experience sites have performed
due diligence by taking a small project and developing in e.g. QV, QS , Tableau etc and form their decision tree from the metrics of the project. We did this some years ago and arrived at QlikView, my latest is QlikSense as it
provided a faster (weeks) deliverable for the intended user.
6. Do you have any case studies for QS? So any beginner can complete them as a part study.
I do have a training course (please email me directly) that uses a Business Case story to develop a
full QS solution, this would give you a good foundation in QS development and understanding of the
product for use, in fact at my last client site 3 of the team purchased the course.