Safe Blood
A blood bank system in three Flutter apps — a donor mobile app, a hospital dashboard, and an admin panel.
- Role
- Flutter Developer
- Year
- 2025
- Stack
- FlutterDartflutter_blocRetrofitDiofreezedget_iteasy_localization

The problem
When a hospital runs low on a blood type, reaching the right donors means phone calls, and the stock itself sits in a ledger: what is available, what is low, and what expires this week is not visible at a glance.
What I built
Three apps that share one colour system, typeface and component set, in Arabic (right-to-left) and English with a language switch on every screen.
Hospital dashboard (web and desktop)
Open and completed request counts, stock per blood type with its status (available, low, out), creating a donation request by blood type and units, an inventory with quantity and expiry that flags anything expiring within 7 days, and a filterable history of past requests.
Donor app (mobile)
Sign-in with a phone number, the donation requests addressed to the donor with hospital, area, blood type and date, a status filter, accept or decline straight from the list, and a profile with blood type and points.
Admin panel
Hospitals as a searchable card grid, adding a hospital, a details page, and update and delete behind a confirmation.
Under the hood
Feature-first structure with data, logic and UI layers; API services generated with Retrofit and Dio; one result-or-error type (ApiResult) with freezed; Cubit for state and get_it for dependencies.

Inventory: quantity, expiry and status per blood type. 
Creating a donation request. 
Admin panel: the registered hospitals. 
The donor's requests, answered from the list. 
Donor profile. 
The same screen in English.
Outcome
All three apps were redesigned in 2026 around one design system. A golden test in each repository renders every screen in both languages with sample data — the screenshots here come from it.