Domo is a full self-service business intelligence software that combines several data analysis and reporting tools into one platform. It helps users connect to multiple data sources, create robust visual reports, manage their data, send messages in real-time, manage projects, and develop new apps.
N/A
QlikView
Score 8.2 out of 10
N/A
QlikView® is Qlik®’s original BI offering designed primarily for shared business intelligence reports and data visualizations. It offers guided exploration and discovery, collaborative analytics for sharing insight, and agile development and deployment.
N/A
React (React.js)
Score 8.8 out of 10
N/A
React or React.js is a JavaScript library for building user interfaces. React enables users to create interactive UIs.
$0
Pricing
Domo
QlikView
React (React.js)
Editions & Modules
No answers on this topic
QlikView
Custom
per user
No answers on this topic
Offerings
Pricing Offerings
Domo
QlikView
React (React.js)
Free Trial
Yes
Yes
No
Free/Freemium Version
No
No
Yes
Premium Consulting/Integration Services
No
Yes
No
Entry-level Setup Fee
No setup fee
Optional
No setup fee
Additional Details
—
On an perpetual license basis, based on server plus number of users.
Contact vendor for pricing.
I believe that companies that record large amounts of data about their product, service employers KPIs, etc, can make the best out of Domo for reporting and data analysis, but if a company handles little data and is not recording this consistently, it will not be of much use.
Sales data validations have helped manage our justifications in the past, especially with regard to new product development and new business introduction. It has also been helpful in identifying trends with business impact and direction specific to quarter and monthly sales from ERP data as well as decisions to purchase equipment of staffing based on run rates and product demand.
One thing that can get out of hand is data output - if you aren't careful in your query, you may be overloaded with data dumps and drown in the amount of info you have to filter through. This is a user caution, not a comment on the software itself.
React is a JavaScript user interface construction library that works well for:
Developing web apps with dynamic and complicated user interfaces.
creating reusable UI elements that may be used in other applications.
creating single-page applications with dynamic content updates that don't require a page reload.
The Virtual DOM's effective updating mechanism allows it to handle large volumes of data updates.
React, on the other hand, might be less suitable for:
Websites that are simple, stagnant, and have no interaction. Other libraries or simple HTML, CSS, and JavaScript may be a better fit in such circumstances.
Web sockets may be a better choice for applications that need real-time updates, such as chat or gaming apps.
When creating mobile apps, React Native is a better option.
Server side rendering only, as React is designed to run on the client side.
Exceptional Transform area of the platform - any/all raw data can be manipulated and combined to create datasources that are very useful for our departments.
Visualization layer is clean and is very business presentable. Its simple but includes depth. Visuals can be created/used by all roles throughout our firm, its not limited to analysts.
Ability to communicate and talk about insights in the data - the communication tool is exceptional. I can @ mention specific users to bring attention to a discovery. I can start a private chat. I can annotate and communicate what I am seeing. I love it.
Mobile experience is excellent. When I am on the road i can actively monitor and engage with my team due to my Domo dashboard on my mobile device. Its amazing to run the business and not worry while away from the office.
React is fantastic for building performant user interfaces. Our web app is snappy and great for our customers.
React has the philosophy of doing one thing and doing it well which is the view layer of the application. This makes it incredibly intuitive and flexible for developers to use.
React has lead the way in being able to write modular and structured code. It is a drastic improvement since the days of spaghetti jQuery code.
React has an unmatched community. The amount of tools and libraries available is fantastic, and there plenty of solutions available online for common problems.
Copying Reports - In Excel or Google Sheets, I like to make copies of similar reports and modify them as necessary for users. In Domo, makes copies of reports (called cards) but all copies are connected. So if you adjust the copy, it changes the original. This means a user has to recreate the report from scratch and then adjust it.
Unforgiving SQL - Domo does allow users to write their own SQL codes, which is great. However, Domo's SQL code is pickier than the other SQL database I've used (Metabase).
Text Alerts - Domo's alerts aren't always the smartest. Some of my dashboards are about the sales teams monthly performance and I get notified when there is a change of more than 20%. I always get notified at the start of the month that reports have changed from 'x' number to zero. This is expected because it's a monthly report and I hate getting texts about it. The only reason I don't term them off so I can be aware if something breaks in the middle of the month.
We found that QlikView can be a bit slow in supporting some forms of encryption. It is web-based and we needed to upgrade all of our server to not support the older SSL and TLS 1 protocols, only support TLS 1.2 and TLS 1.3. However, QlikView could not run with TLS 1.2 and TLS 1.3. We had to wait over six months to get a version that would handle the newer TLS versions.
There are so many options with QlikView that you can get lost when developing a visualization. There are still items I have not yet figured out, such as labeling a graph with the name of a selected detail item.
QlikView works by pulling the data it is going to use for visualization into its database. I am a security reviewer and I need to make certain that PII and PHI is not pulled by QlikView for a visualization, otherwise this could become a reportable indecent.
Debugging React is challenging. Bugs in react code generate stack traces internal to React and it is often totally unclear how it relates to the code you actually wrote.
Relating your React elements to corresponding DOM elements is difficult. The intentional separation of virtual and actual DOM also makes it difficult to map the elements to the structures in the DOM. This is partially ameliorated by the use of the React dev tool, which provides a DOM-like view of the React elements, but the tool still does not provide a direct correspondence with the DOM that is often necessary to figure out why something isn't right.
Because JSX is React-specific and not a language feature, a special compilation process is necessary to convert JSX code to normal JS. Coming from a C++ background, compiling things doesn't bother me, but many JS developers are used to a less structured development.
Domo is a great up-and-coming product. There are many fantastic features that are extremely compelling to our end users, which makes Domo a great fit for our organization. As with many BI tools, there are items on the wish list that could make implementation, administration and usage easier, but I believe these will be addressed over time as the product matures and evolves. The overall concept and approach of this solution has definitely raised the bar in this area of expertise and I would like to see things advance in giving the enterprise tools that will make decision making easier and more robust in the future.
Ease of use, ability to load from pretty much any data source. today I created an application that loaded time sheets from excel that are not in a table format. With Qlik's "enable transformation steps" I was able to automate loads of multiple spreadsheets and multiple tabs easily. Could not do that with any other tool.
The built-in user support and intuitive design of Domo makes it simple to learn and use. I find I can spend hours drilling deep, or else quickly gain an overview in just a few minutes. This is a great advantage since the flexibility fits well with the demands of my role. I enjoy using Domo since I know it will give me comparative data across almost every variable I might want to explore - I look forward to it!
QlikView is very easy to implement. The installation is very straight forward. QlikView has several different data connectors that can connect to different data sources very smoothly. The user interface to build the reports is very easy to understand. This helps to have a smaller learning curve. Something very helpful is that QlikView is a browser application for the end users. So, you don't need to install any applications on the user's computer.
React is just a bit of a different animal. I was avoiding it for the longest time. I thought for sure I would land on Vue or something else with a more approachable and familiar appearance. But after taking an online course in React, I started realize what people were raving about (and complaining about) and decided to implement it at our office for one of our products.
Pretty responsive. It took a while to get a response in selecting data points for our particular cards. Might have taken about a month? I am not sure if this was something on our end or Domo's end. But haven't had any other issues yet that required additional support from Domo.
My experience with the Qlik support team has been somewhat limited, but every interaction I have had with them has been very professional and I received a response quickly. Typically if there is a technical issue, our IT team will follow up. My inquiries are specific to product functionality, and Qlik has been very helpful in clarifying any questions I might have.
Since it's open-source and very popular, the community support for React and related tools and libraries is excellent. There are a lot of people using the same tools, and so issues tend to get fixed quickly and "recipes" are easy to come by. And since it's backed by Facebook, they have a dedicated engineering team working on the progression of React.
My team attended, but I cannot myself rate, but I think it was good as they've successfully launched a training program at our company themselves for users. It was 3-4 day training.
Training was as expected. The demo environments tend to be more fully featured that our own environment, but the training was clear and well delivered.
It is a true web-based application so implementation is much easier and smoother compared to other non-web based BI solutions. Also, they offered consulting services during the implementation process, which was helpful. Also, they provided lots of on-demand training courses and videos, which I liked.
"Implementation" can mean a few things... so I'm not sure that this is the answer you want.... but here it goes: To me, implementation means: "Is the user interface intuitive and can I produce meaningful reports with ease?" On that score, I'd say YES. The amount of training required was minimal and the results were powerful. The desktop implementation is a simple, "blank" interface just waiting for your creativity. The pre-populated templates give you a reasonable start to any project -- and a good set of objects to "play around with" if you're just getting started. Finally, note that the "implementation" I used was baked into QuickBooks 2016 Enterprise -- called "Advanced Reporting"..... That integration makes it ultra useful and simple.
At the end of the day, end-user adoption and taking the burden of IT to build reports was my goal. Demoing and testing many BI tools, DOMO is the one that allowed both to happen.
The only other vendor product that I have worked with that provides a similar experience to Qlikview is Tableau. I would recommend Tableau if your use case is to build a fixed dashboard. You can share reports for free without needing to buy additional licenses. I would recommend Qlikview if your users are looking for a more interactive experience. They can create new objects to represent the data which can't be accomplished as easily in Tableau
While this is a widely contested debate with various blog posts and benchmarks all over the place, its really a personal choice to determine what works for the team. Coming from a Angular 1.x background, I decided to try a new framework when Angular 2.x was announced and at that time React is gaining popularity and Vue hasn't taken off yet. Compared to Angular 1.x and Vue (hybrid of React and Angular) that split the logic from the html templates, I loved the way React breaks code into components using the jsx syntax. In my mind, this allows for cleaner components and easier maintenance
I mentioned a "previously un-analyzable" dataset that we were able to visualize in Domo - the result was business re-alignment for increased productivity, cost savings and ROI.
It's tough to quantify the ability to provide insights that have been desired for years but not possible - we continue to amaze our executives and product managers with the analysis we can provide.
You can use the free desktop version to do a lot of reporting and analysis work more quickly so the ROI is huge
QlikView is great at finding outliers such as data entry errors
QlikView is great at helping you quickly discover new insights about your business that can prompt you to take action that can immediately affect your cash flow.
