React or React.js is a JavaScript library for building user interfaces. React enables users to create interactive UIs.
$0
Tableau Cloud
Score 8.0 out of 10
N/A
Tableau Cloud (formerly Tableau Online) is a self-service analytics platform that is fully hosted in the cloud. Tableau Cloud enables users to publish dashboards and invite colleagues to explore hidden opportunities with interactive visualizations and accurate data, from any browser or mobile device.
$15
per month per user
Tableau Desktop
Score 8.4 out of 10
N/A
Tableau Desktop is a data visualization product from Tableau. It connects to a variety of data sources for combining disparate data sources without coding. It provides tools for discovering patterns and insights, data calculations, forecasts, and statistical summaries and visual storytelling.
I feel like Tableau is easier to use compared with the SAP Business Objects. Both have a bit of a learning curve but I felt that Tableau Online was still more intuitive and user friendly. Tableau Desktop is a powerhouse. It has a very steep learning curve but once you master …
Tableau Online is much simpler than other Business Intelligence tools such as SAS and SAP Lumira. While SAS allows you to create algorithms to display a set, Tableau Online provides a more friendly user interface for ease of access. Although it does not stack up too well with …
From an analyst point of view, Tableau is the most intuitive tool and it's really easy to use. It's simply the most convenient product and gives the biggest possibilities. Of course, it's more expensive and not all features are necessary for some users. I have chosen Tableau …
Tableau Online is much better at presenting and visualizing and manipulating your data. While Host Analytics is second to none in data consolidation, Tableau has much greater flexibility in exploring that data.
Tableau Desktop is great because it has much more extensive capabilities. Tableau Prep is great for ETL. It makes it easy to aggregate multiple data sources, union, clean, etc. It is easy to QA within Prep, and takes a lot of the guesswork out of troubleshooting issues with …
Like previously mentioned, Online and Desktop were eventually rolled together to be one offering the last time I checked. If you'll be sharing reports with other Tableau users then Desktop would be just fine.
Looker ended up as the winning product due to its easy to use and flexibility. It's easy for nontechnical stakeholders to learn how to create their Explores. But Tableau gives us more flexibility in creating highly customized visualizations so analysts still rely on it.
When weighing the pros and cons of Tableau Online vs. SAP ERP, two key considerations emerged as clear winners. SAP ERP is a powerful data purification tool, but it doesn't measure up to the competition in terms of data presentation. When it came to data visualization and …
Sisense offers a powerful backend database, Elasticube that integrates well with Web Service data sources. Tableau enables better visualization flexibility and functionality without having to write javascript.
Both Tableau Online and BI solutions provide visualizations. In Power BI we choose the visualization first, then drag the data into it. In Tableau, we select the data and switch between visualizations on the fly. It’s easier to jump between visualizations in Tableau. Power BI …
Verified User
Analyst
Chose Tableau Cloud
I think Tableau is better for a bigger firm with more data than MicroStrategy is. While MicroStrategy seems to be more user-friendly in terms of customization on the fly, and I find it a bit better organized - which is simply my preference of organizational style - my …
With Tableau Desktop, it's easy to create a report in the
context quickly. It allows for the seamless management of the data sources,
which is convenient for the data users. Because it is simple to use, it is
Verified User
Analyst
Chose Tableau Desktop
The online and public versions are only good for the hobbyist because they are not secure enough for most business applications. Dapresy is a marketing tool that is supposed to give executives a snapshot of marketing results. It's not very customizable and the results are …
We were interested in expedience at reasonable cost and so didn't do any sort of bakeoff, but tried Tableau first as a potential solution for moving beyond Excel for large scale data analytics. We picked it because it more than met our functional needs at a very reasonable …
Verified User
Analyst
Chose Tableau Desktop
I feel like Tableau is easier to use and offers a greater selection of visualizations. I feel that the dashboards are easier to put together and offer a great amount of flexibility for the end-user. Tableau has an excellent user support group. I find the community to be …
My current work environment uses both Tableau Online, MicroStrategy & SSRS in parallel. Tableau is much closer to the SSRS in terms of visualization tool where as MicroStrategy is an enterprise data modeling and reporting tool.
Based on the use case we use different tools. Here …
Cass evaluated Domo, QlikView and Birst prior to selecting Tableau. It came down to cost (and by a significant margin); the others have relatively high implementation, hosting and other costs. Additionally, based on a recent Gartner "Magic Quadrant", Tableau exceeds all others …
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.
If you're using Tableau as the primary BI tool, then Tableau Cloud is well suited to publish and share the results with a wide(r) audience. It is well suited for various degrees of self-service proficiency, from pure consumers of analytical work to more advanced users who can use web editing for smaller or larger adjustments, and even for desktop power users who will publish their work to Tableau Cloud. It has many good ways to organize the content and make it easily accessible via search, favorites, folders, collections ("playlists for your data"), or history ("recents"). It might not be ideally suited if there are many on-prem sources to be used (even though there are options to connect them) or if you have very special requirements regarding custom server setup, which is limited in a shared cloud environment like Tableau Cloud.
The best scenario is definitely to collect data from several sources and create dedicated dashboards for specific recipients. However, I miss the possibility of explaining these reports in more detail. Sometimes, we order a report, and after half a year, we don't remember the meaning of some data (I know it's our fault as an organization, but the tool could force better practices).
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.
Tableau Online is completely cloud based and that's why the reports and dashboards are accessible even on the go. One doesn't always need to access the office laptop to access the reports.
The visualizations are interactive and one can quickly change the level at which they want to view the information. For example, one person might be more interested in looking at the country level performances rather than client level. This is intuitive and one doesn't need to create multiple reports for the same.
The feature to ask questions in plain vanilla English language is great and helpful. For quick adhoc fact checks one can simply type what they are looking for and the Natural Language Programming algorithms under the hood parse the query, interpret it and then fetch the results accordingly in a visual form.
An excellent tool for data visualization, it presents information in an appealing visual format—an exceptional platform for storing and analyzing data in any size organization.
Through interactive parameters, it enables real-time interaction with the user and is easy to learn and get support from the community.
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.
Our use of Tableau Desktop is still fairly low, and will continue over time. The only real concern is around cost of the licenses, and I have mentioned this to Tableau and fully expect the development of more sensible models for our industry. This will remove any impediment to expansion of our use.
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.
Based on comments from our clients, I awarded it this grade. Non-technical customers frequently compliment us on the ease with which they can utilize Tableau Online. Usability is rarely a source of contention amongst our customers. Few complaints have come from me as a user of our internal products.
Tableau Desktop has proven to be a lifesaver in many situations. Once we've completed the initial setup, it's simple to use. It has all of the features we need to quickly and efficiently synthesize our data. Tableau Desktop has advanced capabilities to improve our company's data structure and enable self-service for our employees.
When used as a stand-alone tool, Tableau Desktop has unlimited uptime, which is always nice. When used in conjunction with Tableau Server, this tool has as much uptime as your server admins are willing to give it. All in all, I've never had an issue with Tableau's availability.
Tableau Desktop's performance is solid. You can really dig into a large dataset in the form of a spreadsheet, and it exhibits similarly good performance when accessing a moderately sized Oracle database. I noticed that with Tableau Desktop 9.3, the performance using a spreadsheet started to slow around 75K rows by about 60 columns. This was easily remedied by creating an extract and pushing it to Tableau Server, where performance went to lightning fast
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.
I have not had any issues that require customer support from Tableau at this time, which speaks well to Tableau. I have taken an online course with Tableau and it was very professional and well done, so based on that I would assume a similar level of quality for their customer service.
Tableau support has been extremely responsive and willing to help with all of our requests. They have assisted with creating advanced analysis and many different types of custom icons, data formatting, formulas, and actions embedded into graphs. Tableau offers a weekly presentation of features and assists with internal company projects.
It is admittedly hard to train a group of people with disparate levels of ability coming in, but the software is so easy to use that this is not a huge problem; anyone who can follow simple instructions can catch up pretty quickly.
I think the training was good overall, but it was maybe stating the obvious things that a tech savvy young engineer would be able to pick up themselves too. However, the example work books were good and Tableau web community has helped me with many problems
Again, training is the key and the company provides a lot of example videos that will help users discover use cases that will greatly assist their creation of original visualizations. As with any new software tool, productivity will decline for a period. In the case of Tableau, the decline period is short and the later gains are well worth it.
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
In determining whether to go with Tableau Online versus Alteryx, two important factors stood out in determining our go-to solution. First, while Alteryx is an impressive tool for data cleansing, it did not stack up in terms of data visualization capabilities. Tableau, on the other hand, provided us everything we needed in terms of visualizing our data and analytics. The second factor is cost. Well neither solution would be considered cheap, Tableau was the more cost effective solution for our needs.
I have used Power BI as well, the pricing is better, and also training costs or certifications are not that high. Since there is python integration in Power BI where I can use data cleaning and visualizing libraries and also some machine learning models. I can import my python scripts and create a visualization on processed data.
Tableau Desktop's scaleability is really limited to the scale of your back-end data systems. If you want to pull down an extract and work quickly in-memory, in my application it scaled to a few tens of millions of rows using the in-memory engine. But it's really only limited by your back-end data store if you have or are willing to invest in an optimized SQL store or purpose-built query engine like Veritca or Netezza or something similar.
Tableau was acquired years ago, and has provided good value with the content created.
Ongoing maintenance costs for the platform, both to maintain desktop and server licensing has made the continuing value questionable when compared to other offerings in the marketplace.
Users have largely been satisfied with the content, but not with the overall performance. This is due to a combination of factors including the performance of the Tableau engines as well as development deficiencies.
