Skip to the case study
ELALFY.
All work

صاينتراRepair management SaaSIn development

SAYNTRA

Repair-center operations, from intake to diagnosis, for teams working in Arabic and English.

A bilingual repair-center application connecting customer intake, device records and technician workflows in one focused workspace.

My part
Full-stack development — Next.js interface and Laravel API integration
Status
In development
Built with
  • Next.js
  • React
  • TypeScript
  • Laravel
  • PHP
  • MySQL
  • Sanctum
  • Three.js
No public demo — this page is the full write-up.

Actual marketing-story screenshots; the illustrated repair device contains explicitly labelled sample data.

Scroll-linked storytelling; future operations are labelled in development.
Arabic mobile composition captured from the actual application.
SAYNTRA — 1 of 3
SAYNTRA repair story with rendered smartphone and intake explanation

Actual marketing interface. The device contains labelled sample data.

Why it exists

Give repair-center teams a structured way to record devices, keep their history and coordinate diagnosis, while making a complex operational product approachable in English and Arabic.

My part: full-stack development — next.js interface and laravel api integration.

How it is built

Next.js and strict TypeScript form the interface layer. A Laravel API uses Sanctum cookie authentication and MySQL persistence. Organization scopes, policies and relational constraints protect tenant boundaries. React Three Fiber, Drei and Three.js power the marketing device presentation.

What is implemented

  • English/Arabic interfaces with RTL and theme preferences
  • Organization-scoped customer and device records
  • Repair intake, technician assignment and diagnosis
  • Role-aware dashboards and guarded status transitions
  • Team invitations and repair history
  • Scroll-driven 3D repair story with low-power fallbacks

Hard parts and decisions

Making operations legible

Separate intake from assignment and diagnosis, with clear status history instead of one overloaded workflow form.

Tenant boundaries

Scope every customer, device and repair to its organization through Laravel policies and relational constraints, so one repair center can never read another’s records.

Arabic and English parity

Use mirrored layouts, localized navigation and typography, plus themes and reduced-motion-aware 3D presentation.

Where it stands today

In development

Working local checkpoint. Intake, assignment and diagnosis are implemented. Estimates, inventory, invoicing, payments and the complete delivery lifecycle remain in development. Not deployed.