SPIKE: Explore how to break off the UI folder into its own island.

[desi]

What is this about?

Analyze the dependencies within the UI folder to identify circular dependencies and determine how to isolate it into its own"island". This involves evaluating the current dependency tree and proposing refactorings to try to break those dependencies.

Primary Outcome/Benefits:

If we determine that we can remove the circular dependencies within the UI folder, that might allow us to tackle this work by itself and hopefully gain faster load times for users on login. i.e. it could let us get some perceived performance gains for users sooner rather than later. Users would still incur/experience performance issues when the rest of the app loads but maybe we can at least improve the initial login experience.

Supporting visualization

If we can determine a path toward removing the dependencies from the rest of the codebase and the circular dependencies within this island we might get the gains mentioned above.

Scenario

No response

Design

No response

Technical Details

No response

Threat Modeling Framework

No response

Acceptance Criteria

• We have an idea other whether we can actually pull it apart from the rest of the continent of dependencies so that it can be addressed on its own.

Stakeholder review needed before the work gets merged

• Engineering (needed in most cases)
• Design
• Product
• QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
• Security
• Legal
• Marketing
• Management (please specify)
• Other (please specify)

References

No response