Client projectPortal Operations Employee

Inova

HR tools, portals and an app: from hiring to offboarding.

Identified technologies

PHP / Yii2FlutterAPIs

The problem

HR work involves administration, clients and staff, with processes from hiring to offboarding.

The solution

I built an HR system from scratch for Inova, with web administration, client and staff portals and a Flutter app.

What makes up the solution

PHP/Yii2 system for HR workflows, reports, exports and business integrations.
View technical details →
Separate client and staff portals, with different users and responsibilities.
View technical details →
Flutter app with local storage and mobile integrations.
View technical details →

Project scope This is a client project. The case describes the system and its layers while keeping client data and private operations out of the presentation.

My contribution

I built an HR system from scratch for Inova, with web administration, client and staff portals and a Flutter app. It supports steps from hiring to offboarding.

Architecture overview

Operations, client and staff portals, a Flutter app and integrations share one product.

Technical structure

Technology by module.

Three PHP applications serve different audiences. A Flutter app adds mobile operation.

What each part does and which technologies support it. A module in the code does not mean all its features are complete or published.

01 / Existing code

Operations system

PHPYii2JavaScriptBootstrap

Administrative operations.

Staff and management workflows, reports, exports and business integrations, including eSocial components.

02 / Existing code

Client portal

PHPYii2

Client portal.

A client-specific entry point with legacy views, controllers and models.

03 / Existing code

Employee portal

PHPYii2JWT

Staff portal.

Staff surface with authentication and central data integration.

04 / Existing code

Mobile app

FlutterDartSQLiteFirebase

Mobile application.

Organized into pages, providers, services and models, with local storage and notification integrations.

How the parts connect

The PHP modules share a logical database and must keep compatibility. The app uses services and keeps local state in a separate layer.

Data and integrations

MySQL/MariaDB in the legacy system, based on its documented SQL scope. The app has SQLite and local preferences. Physical topology depends on the environment.