Krow/Krow-workspace
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: Implement FAQs feature for staff application with updated routing and UI components

Browse Source
This commit is contained in:
Achintha Isuru
2026-02-18 23:21:26 -05:00
parent 316a010779
commit 8578723fb3
12 changed files with 54 additions and 241 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
internal/launchpad/assets/documents/prototype/client-mobile-application/architecture.md
View File

@@ -59,7 +59,7 @@ The application is broken down into several key functional modules:
| Component | Primary Responsibility | Example Task |
| :--- | :--- | :--- |
| **Router (GoRouter)** | Navigation traffic cop | Directs the user from the "Login" screen to the "Home" dashboard upon success. |
| **Router (Flutter Modular)** | Navigation traffic cop | Directs the user from the "Login" screen to the "Home" dashboard upon success. |
| **Screens (UI)** | Displaying information | Renders the "Create Order" form and captures the user's input for date and time. |
| **Providers (Riverpod)** | Data management & State | Holds the list of today's active shifts so multiple screens can access it without reloading. |
| **Widgets** | Reusable UI building blocks | A "Shift Card" widget that displays shift details effectively, used in multiple lists throughout the app. |
@@ -91,7 +91,7 @@ While currently operating as a high-fidelity prototype with mock data, the archi
## 8. Key Design Decisions
* **Flutter Framework:** chosen for its ability to produce high-performance, native-feeling apps for both iOS and Android from a single codebase, reducing development time and cost.
* **GoRouter for Navigation:** A modern routing package that handles complex navigation scenarios (like deep linking and sub-routes) which are essential for a multi-layered app like this.
* **Flutter Modular for Navigation:** A modern routing package that handles complex navigation scenarios (like deep linking and sub-routes) which are essential for a multi-layered app like this.
* **Riverpod for State Management:** A robust solution that catches programming errors at compile-time (while writing code) rather than run-time (while using the app), increasing app stability.
* **Mock Data Services:** The decision to use extensive mock data allows for rapid UI/UX iteration and testing of business flows without waiting for the full backend infrastructure to be built.
@@ -102,7 +102,7 @@ flowchart TD
direction TB
subgraph PresentationLayer["Presentation Layer (UI)"]
direction TB
Router["GoRouter Navigation"]
Router["Flutter Modular Navigation"]
subgraph FeatureModules["Feature Modules"]
AuthUI["Auth Screens"]
DashUI["Dashboard & Home"]

2
internal/launchpad/assets/documents/prototype/staff-mobile-application/architecture.md
View File

@@ -98,7 +98,7 @@ flowchart TD
direction TB
subgraph PresentationLayer["Presentation Layer (UI)"]
direction TB
Router["GoRouter Navigation"]
Router["Flutter Modular Navigation"]
subgraph FeatureModules["Feature Modules"]
AuthUI["Auth & Onboarding"]
MarketUI["Marketplace & Jobs"]