Use Case Frontend
The Use Case Frontend is responsible for the interaction with the user (e.g. citizen or civil servant). The User Interface (UI) is visually and technically designed to ease understanding and usage of the displayed functionalities by users. The business logic is managed by the Use Case Backend.
What do we use to build it?
| Name | Purpose |
|---|---|
Library for web and native user interfaces | |
Developer tool | |
Component library for bootstrapping |
For a deeper explanation of why these tools were chosen, read about the Component Library Evaluation and Front-end framework on GovStack's Confluence.
Where do we demo it?
| GitHub Repository | Used in... |
|---|---|
Which conceptual decisions do we follow?
Both the full-stack USCT demo and the front-end only USCT demo applications live in the same application due to the interconnectedness of the UI and not seeing a point in separating them at this point in time for simplicity's sake. The full-stack demo is an MVP-like application demonstrating how the front-end and the back-end work together when using multiple building blocks to build an application.
The RPC Layer
The RPC Layer is based on the Facade Pattern. In short, we are using it as a configurable API layer for the full-stack USCT demo. It allows us granular control over our API call method endpoints from one location, which is good for demonstrating connectivity between different interchangeable Building Blocks. In addition, the RPC layer can also be configured for different providers, such as MockProvider, APIProvider, LocalStorageProvider, etc.
