Looker is a BI application with an analytics-oriented application server that sits on top of relational data stores. It includes an end-user interface for exploring data, a reusable development paradigm for data discovery, and an API for supporting data in other systems.
N/A
React
Score 9.2 out of 10
N/A
React is a JavaScript library for building user interfaces. React enables users to create interactive UIs. Design simple views for each state in an application, and React will update and render just the right components when data changes. React is available free and open source under the MIT license.
As a Sales, it suited me to use such well-developed software with a nice dashboard that could navigate between my prospects, visualize the numbers of clients, and check my achievements for each quarter. That would help me understand my performance and record the data I needed for myself as a salesperson.
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.
Show visited pages - sessions, pageviews - which programs are viewed the most.
Displays session source/medium views to see where users are coming from.
It shows the video titles, URLs, and event counts so we can monitor the performance of our videos.
It gives a graphic face to the numbers, such as using bar charts, pie graphs, and other charts to show user trends or which channels are driving engagement.
Our clients like to see the top pages visited for a month.
I like the drop-and-drag approach, and building charts is a little easier than it was before.
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.
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.
I give it this rating because it deems as effective, I am able to complete majority of my tasks using this app. It is very helpful when analyzing the data provided and shown in the app and it's just overall a great app for Operational use, despite the small hiccups it has (live data).
Looker is relatively easy to use, even as it is set up. The customers for the front-end only have issues with the initial setup for looker ml creations. Other "looks" are relatively easy to set up, depending on the ETL and the data which is coming into Looker on a regular basis.
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.
Somehow resources heavy, both on server and client. I recommned at least 50Mbs data rate and high performance desktop comouter to be abke to run comolex tasks and configure larger amount of data. On the other hand, the client does not need to worry when viewing, the performance is usually ok
Never had to work with support for issues. Any questions we had, they would respond promptly and clearly. The one-time setup was easy, by reading documentation. If the feature is not supported, they will add a feature request. In this case, LDAP support was requested over OKTA. They are looking into it.
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.
Looker gives you options to integrate external APIs with great ease. Our data analytics team is able to easily use multiple data sources as input to the Looker dashboard, and everything is consolidated in one single Dashboard. You also have an option for Shared folders to be accessed by multiple people. The reporting system is perfect and has a wide range of options/reporting options that can be implemented.
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
Looker has a poignant impact on our business's ROI objectives. As an advertising exchange we have specific goals for daily requests and fill, and having premade Looks to monitor this is an integral piece of our operational capability
To facilitate an efficient monthly billing cycle in our organization, Looker is essential to track estimated revenue and impression delivery by publisher. Without the Looks we have set up, we would spend considerably more time and effort segmenting revenue by vertical.
Looker's unique value proposition is making analytical tools more digestible to people without conventional analytical experience. Other competing tools like Tableau require considerably more training and context to successfully use, and the ability to easily plot different visualizations is one of its greatest selling points.
