Today, many organisations are developing data-intensive applications that include interactive dashboards, infographics, personalised data visualisations, and charts that respond to a user’s data entitlements.
In cases where an application needs to display a bar chart or other simple data visualisation, it’s easy enough to use a charting framework to configure the visual and render the chart. But a data visualisation platform’s embedded analytics capabilities may offer richer end-user experiences and tools to support easier and faster enhancements.
Embedding analytics can be a powerful approach to enhancing applications when experimentation around the visualisations is important. For example, an application’s product owner may start with a simple visual but then realise that different user personas require specialised dashboards. A data visualisation platform makes it a lot easier to develop, test, and iterate on these dashboards rather than coding visuals.
Another key benefit of using data visualisation platforms is that data scientists and subject matter experts can participate in the application development process.
Instead of having them write requirements for a software developer to translate into code, the visualisations are iteratively improved by a group of people who best know the business need, the data, and best practices in data visualisations.
Why you should use data visualisation tools
Let’s look at some use cases to embed data visualisations when rapid development and experimentation are required.
- Analytics can be embedded into an enterprise system that includes data from several other data sources. An example is a dashboard for sales managers displayed within the customer relationship management (CRM) application that includes financial data from the ERP (enterprise resource planning) system and prospecting data from marketing automation platforms.
- In customer-facing mobile and web applications, a simple chart or graph can drive user interaction. Think of a stock-trading application that charts stocks on an investor’s watch list and highlights ones near their low prices when it’s potentially the right time to buy.
- Media organisations and others that publish content may want to pursue data journalism, in which a journalist writes an article about a data set and one or more data visualisations, and data and analytics are the foundation of the story.
- Marketing infographics, including graphic designs or data visualisations, are embedded in websites and other marketing tools.
- For businesses trying to be data driven, this may be the opportune time to select a data visualisation platform to develop analytics and embed them in enterprise or customer-facing applications.
- Organisations that are already using data visualisation tools may need to extend a visualisation with custom integrations and functionality to manipulate or process data through a workflow.
- Entire customer-facing applications may be data visualisations for data products and services. The approach is common for data, financial services, insurance, and e-commerce businesses where the data is the product, and analytics can be a differentiator. In these cases, using a data visualisation platform to develop the product and leveraging the platform’s flexibilities to embed it in another system enables teams to innovate and support rapid enhancements.
Embedding analytics drives innovation
What’s different about data visualisation is that the requirements, design, and functionality required are likely to be highly iterative. As more stakeholders and users learn more about the data and what insights are useful, they are likely to modify the requested experience, design, and functionality.
That’s why, even though visualisation libraries may be easy to use for the developer, they may not be an optimal development approach for embedding analytics where frequent iterations are required. Iterative design is especially the case in journalism and marketing where the goal is to let users design, develop, and publish data visualisations without requiring support from developers and technologists.
Steps to embedding analytics in apps
When thinking about embedding analytics in applications, review these development considerations:
- Who are the users, and what questions are you helping them answer with the analytics? The best dashboards and data visuals answer specific questions and perform a business function rather than just reporting on data.
- Will the app be used on the web, on mobile, or both? This requirement qualifies the screen dimensions, number of charts, and data volume considerations that developers must factor into the design.
- How much data needs processing, and what are the performance requirements? For larger data sets and greater performance, using database materialised views, in-memory databases, and visualisation of aggregate data may be necessary.
- What data governance and security define a user’s data entitlements? Developers should dimensionalize these rules as use cases and create test scenarios to validate that implementations adhere to data governance. Furthermore, the visuals may need modifications when there are significant row- and column-level data governance rules.
- Teams should develop standards and a centre of excellence on datavisualisation that guide chart types, color schemes, labels, style guides, and other rules that provide consistent user experiences.
- As the data can change, it is a best practice to create test automations on data visualisation that run in continuous integration and continuous delivery (CI/CD) pipelines but can also run as application monitors alerting on production incidents.
These are some of the steps developers, data scientists, and agile teams should include when embedding analytics in apps.
Want some inspiration? Review the analytics on Tableau Public, Microsoft Power BI Galleries, Sisense example dashboards, and Qlik gallery for examples. While many dashboards are useful as stand-alone tools, they can deliver greater business value when embedded in customer-facing and internal workflow applications.