← Back to projectsPROJECT / CASE STUDY

LionLeaders

A public website and client workspace for a real estate and financial-services business, with Android access, training, backoffice, and business automation.

  • Next.js
  • PostgreSQL
  • Android
  • Automation
Simplified LionLeaders architecture; details in the text below.
Status
Active development · matchme.best test environment
My role
Web and Android development, workflow design, deployment
Scope
Client portal, permissions, training progress, files, and transactional workflows
Outcome & validation
Implemented test workflows and documented regression checks; legacy migration and production acceptance remain separate.
Test website ↗

Opens the public LionLeaders presentation on matchme.best. The client portal requires authorized access, and regional access restrictions may apply. This is a development environment, separate from the original production service.

Public test-site presentation, captured during the November 2026 design review.
Public test-site presentation, captured during the November 2026 design review. Open the image to inspect the full view.

The problem

Modernizing a client portal means preserving who may see and change each record, not simply replacing the interface. LionLeaders brings the public website, MyPort collaboration, Academy training, Backoffice, and profile workflows into a shared application.

My contribution

I develop the Next.js/React web application, PostgreSQL-backed business logic, Android/Capacitor integration, and deployment workflows. matchme.best is the test environment for this project, not a separate real estate product. iOS belongs to the requested broader scope; a delivered iOS implementation is not established by the reviewed source.

The design

Authorized server handlers call shared domain services and PostgreSQL transactions. Protected files have explicit publication and checksum contracts. The Android client uses a constrained mobile API and native storage/lifecycle support. Notification outboxes and serving-authority checks handle operational boundaries.

A difficult problem: retrying the same intention

HouseHour, the fictional transaction sandbox, needed to distinguish a failed response from a failed mutation. The client retains its idempotency key through uncertain responses and refresh failures. The server binds replays to the actor, request content, and sandbox generation. Exact retries return the original result instead of creating a second action. HouseHour is a demonstration, not real-money settlement or property ownership.

Evidence and status

The project records document web and Android tests, authorization checks, interval-based training progress, immutable-file checks, and staged releases. Some combined mobile runs needed focused retests, and physical-device and migration acceptance remain separate. The public-site image shows the test presentation; it does not expose private customer records.

Read the engineering article. About the test environment.