Fluent Commerce Logo
Docs

Analyzing What's Built in an App

Use CaseExamples that showcase what's possible with the platform. These use cases focus on feature and capability discovery and may not include implementation details.

Author:

Fluent Commerce

Changed on:

6 Apr 2026

Problem

A Fluent Commerce Mystique manifest that has been developed over multiple sprints by multiple developers accumulates components, routes, and queries that become increasingly difficult to reason about without a structured inventory. Without a consolidated view of what the manifest contains, developers working on new features or modifications operate with an incomplete picture of the existing application, making assumptions about component usage and route coverage that are not always accurate. Complexity builds up in specific pages or sections without anyone noticing until a change in that area produces unexpected failures, and the absence of a scored analysis means there is no objective way to identify which parts of the manifest carry the most risk before making modifications. Components that were added during earlier development cycles but are no longer referenced by any active route remain in the manifest silently, adding noise that makes the application harder to understand and maintain. Internationalisation coverage gaps are rarely surfaced during development and typically only become visible when the application is used in a non-default language by a real user, at which point the gap is already affecting the live experience.

A development team inherits a Fluent Commerce OMS application from a previous team and is asked to add several new pages and optimise the performance of the existing order list view. Without a structured analysis of the existing manifest, the team begins work based on a manual review of the manifest files, which runs to several hundred lines across multiple files. Two weeks into the engagement, a developer modifies a shared component configuration that turns out to be referenced by six other pages, causing rendering issues across the application that take a day to trace and resolve. A separate performance investigation eventually surfaces a data query on the order list page that is fetching significantly more fields than the page actually uses, a pattern that is repeated on three other pages and that no one on the previous team had flagged. An unused component registered in the manifest is discovered only when a new team member asks what it does and no one can answer. None of these issues would have required investigation if a manifest analysis had been run at the start of the engagement.

Solution Overview

Analysing an existing application manifest starts with a single request that triggers a seven-dimension assessment across the full manifest. The tool examines component usage and frequency, route structure and coverage, a weighted complexity score for every section of the manifest, data query patterns, internationalisation coverage, and the overall structural patterns applied across the application. Visual diagrams are produced to make the relationships and structure easier to interpret, regardless of how familiar a developer is with the codebase.The output gives developers at both experience levels something useful. Experienced developers can identify optimisation opportunities, complexity hotspots, and areas of technical debt. Newer developers can use the analysis to build an accurate mental model of how the application is structured before making changes, reducing the risk of unintended consequences.Running this analysis before significant manifest work begins is the most effective use: it ensures that decisions are grounded in an objective view of the current implementation rather than assumptions or partial knowledge.

Solution