Configuration-driven UI – Fast Track the UI Development


Measured has seen tremendous growth in terms of providing accurate marketing spend reports with its core in incrementality. However, they were running these services with Tableau dashboards as an MVP. To extend its range of services, Measured took to transitioning from Tableau to native dashboards. This meant there was a need to develop complex custom dashboards consisting of multiple charts, data-heavy tables, quick access buttons, and multiple other UI elements, as well as integrations with backend and data platforms.

With Measured’s wide range of products and services, there was a need to implement a solution that would ease out the same problems for multiple products at the same time and enable Customer Success teams to build custom dashboards out of the box.


Keeping in mind the product’s complexity and delivering the features and dashboards more systematically and faster, a configuration-driven UI built for reusability was the most suitable solution to cover overall use cases and development.

This implementation came with its own set of challenges. One is Reusability. If a component is reusable, it will have multiple use cases across the product, and the built component should fit the bill for all of it. Not just that, there is also a need to have flexibility to the extent that the components can be interdependent and still perform and manage heavy data. Ex – A “Filter component” (Read about reducing uptime by 20x using a Framework level feature) and a “Table Component” are interdependent on each other’s functionality.


Configuration Driven Development enables both tech and non-tech teams to respond much faster to customer queries and requests. Listed here are some of those benefits:

Customer success teams were able to quickly create and demonstrate complex visualizations and build more ambitious dashboards to increase product stickiness using pre-existing components.

Developers reported they were now at an almost 3 times faster pace increment in delivering new features by reusing and benefitting from the component library.

Especially in the case of handling large sets of data, configuration-driven UI established a rather smoother interaction between the UI elements and the backend.

With a central library of UI components, anything built using these components resulted in improved code quality and consistency across the products.

ETA on bug fixes was significantly reduced

Minor changes, like nomenclature changes were made more systematically across the products whenever necessary.

Configuration-driven development made room to address changes and bug fixes based on sections ensuring product uptime.

“I am proud of Measured’s strong culture, thus one of my chief concerns during our expansion is a dilution of that sense of community. Akrity has assuaged my concerns through their own commitment to community and has worked lockstep with Measured to keep ours strong. Akrity’s technical ability and skill has not only supported our endeavors but has helped us push out key features that have measuredly grown our position in the market.”

Jared Scott

Director, Engineering, Measured