replace the "Krow" with "KROW"

This commit is contained in:
Achintha Isuru
2026-02-26 15:13:26 -05:00
parent f9c2d822e6
commit b8d07380c0
60 changed files with 225 additions and 227 deletions

View File

@@ -1,7 +1,7 @@
# Application Overview: Krow Client Mobile App
# Application Overview: KROW Client Mobile App
## 1. Executive Summary
The **Krow Client App** is a mobile workforce management tool designed for business owners and managers. Think of it as a "control center" that allows businesses to easily hire, manage, and pay temporary staff for events or shifts.
The **KROW Client App** is a mobile workforce management tool designed for business owners and managers. Think of it as a "control center" that allows businesses to easily hire, manage, and pay temporary staff for events or shifts.
Instead of calling agencies or managing spreadsheets, a business user opens this app to:
* Define a job (Event/Shift).
@@ -11,10 +11,10 @@ Instead of calling agencies or managing spreadsheets, a business user opens this
* Handle payments and invoices.
## 2. High-Level Architecture
The application follows a **Modern Mobile Architecture** designed for reliability and speed. It acts as a "smart interface" that connects the user to the central Krow platform.
The application follows a **Modern Mobile Architecture** designed for reliability and speed. It acts as a "smart interface" that connects the user to the central KROW platform.
* **The Frontend (This App):** Handles everything the user sees and touches. It validates inputs (like ensuring a shift end time is after the start time) and displays data beautifully.
* **The Bridge (API Layer):** The app talks to the Krow Cloud Server using **GraphQL**. This allows the app to ask for exactly the data it needs—no more, no less—making it fast even on slower connections.
* **The Bridge (API Layer):** The app talks to the KROW Cloud Server using **GraphQL**. This allows the app to ask for exactly the data it needs—no more, no less—making it fast even on slower connections.
* **The Backend (The Brain):** All heavy processing (matching staff to jobs, processing payments) happens on the secure server, not on the phone.
## 3. Major Components & Modules
@@ -45,9 +45,9 @@ These modules contain the specific business logic and UI for each distinct part
## 5. External System Communication
The app does not live in isolation; it talks to several outside services:
* **The Krow Backend (GraphQL):** The primary source of truth for all data (Events, Staff profiles, Shifts).
* **Firebase Auth:** Handles secure login (passwords, email verification) so the Krow team doesn't have to build security from scratch.
* **Firebase Remote Config:** Allows the Krow team to change app settings (like feature flags or text) without forcing users to update the app.
* **The KROW Backend (GraphQL):** The primary source of truth for all data (Events, Staff profiles, Shifts).
* **Firebase Auth:** Handles secure login (passwords, email verification) so the KROW team doesn't have to build security from scratch.
* **Firebase Remote Config:** Allows the KROW team to change app settings (like feature flags or text) without forcing users to update the app.
* **NFC Services:** Interacts with physical NFC tags, likely for scanning staff badges or verifying presence at a location.
* **Geolocation Services:** Uses the phone's GPS to verify that actions (like creating a hub) are happening at the correct physical address.
@@ -109,7 +109,7 @@ flowchart TD
subgraph External_Services [External Cloud Ecosystem]
direction TB
Krow_Backend[Krow Backend Server]:::external
Krow_Backend[KROW Backend Server]:::external
Firebase[Firebase Auth & Config]:::external
Maps_NFC[Geolocation & NFC Services]:::external
end

View File

@@ -1,4 +1,4 @@
# Use Case Documentation: Krow Client Mobile App
# Use Case Documentation: KROW Client Mobile App
## 1. App Initialization