Tableau Desktop vs. Progress Telerik Fiddler

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).

Incentivized

I am a senior software engineer and I have actively made fiddler a requirement for all of our engineers to have on their laptops by default. I have recommended it to all web developers that I have worked with and contractors that I have worked with as it has saved my mental stability on numerous occasions when trying to show people details of various web requests when working on integrations between different systems This is an absolutely fantastic product that I have used in a technical capacity many, many times and I will always suggest it as a tool when someone is debugging specifically but also for initial development to see how the requests are formed and for sharing responses and requests details so that others can recreate the request that you have sent through right down to the smallest detail

• The Visualizations graphics are really good and the color options help in designing attractive charts. They help to convey more information and can be made interactive.
• You can add filters with offer you to plug and play with values and understand different outcomes.
• You can drag and drop options while creating charts and dashboards. also it is a very fluid layout.

Incentivized

• Formatting the data to work correctly in graphical presentations can be time consuming
• Daily data extracts can run slowly depending on how much data is required and the source of the data
• The desktop version is required for advanced functionality, editing on [the] Tableau server allows only limited features

Incentivized

• The display could potentially become a bit more user-friendly over time, it's pretty easy to follow but for example, I always view the raw request/response information by default and this is not the default selection, being able to choose the default selection would be nice
• Clearer information and options to reduce 'noise' when viewing the requests, there are often a lot of background requests being sent on a computer, you can filter to roughly see what you want and filter out things that you don't want but there are different types of requests and I can't see how to filter between those - possibly a feature but could be made easier to use potentially
• Nothing else to put, this is a fantastic product so there isn't much else to suggest at this stage of using it and I have been using fiddler for years now in my role as a software engineer

Because right now its the best option out there (disclosure: I haven't used Qlikview or some of the other direct competitors of Tableau). The big investment is in Tableau Server not desktop. For the cost of the license of Tableau desktop, its a pretty good deal. You can hook it up to pretty much any data source easily. You can easily share the visualizations with your team/colleagues easily. Tableau Desktop is generally easy to use for business users. But the more advanced stuff is better suited for a analyst or someone with a IT/CS background.

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

Incentivized

The Tableau Desktop's support team has been very helpful and tend to response very quickly. After all you have paid very premium price for the product and it goes to the services. This makes using the tool much easier for these who doesn't have such experience to get help quickly.

Incentivized

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

Incentivized

Time needs to be spent ahead of implementation to make sure data sources are set up and ready. Consultants need to understand the data sources and the goals before setting foot on-site. Installation is easy, learning to use it takes time. The training resources available are great.

Incentivized

Tableau Desktop is clearly one of the best in the business. It has incredible capabilities, and many features are extremely useful. The intuitiveness of the dashboards and the graphical nature of the visualizations are widely used features and super helpful. One of the other benefits is that both programmers and non-programmers can equally explore and create their own opportunities, and seamless integration is possible.

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.

• Easy to share and manage viewer access on a different level to help identify fraud.
• Faster report generation, increased revenue, better decision-making, and data storytelling.
• One-click access to business health and the ability to build/maintain more effective and efficient reports.
• It's easy to share and even manage access to viewers on a different level, and reports are done in a more visual and storytelling manner.

Incentivized

• Overall this tool has sped up the process of integrating with new systems infinitely
• The cost of fiddler everywhere which is what we use specifically is nothing in comparison to the cost of dev time saved when debugging processes
• Being able to send information around so simply to other support teams to show them what responses we are getting along with the request detail have made communications much quicker and saves a lot of time going back and forth discussing what is being done and what the request is being sent