Back to Archive
Case StudyPlatformsUI / UXDashboardsFull stack

Zakat – Islamic Financial Platform & Dashboard

A modern Next.js frontend platform for presenting zakat-related content, calculators, FAQs, and dashboard flows with full Arabic support and scalable architecture.

Role
Lead Engineer
Timeline
Production
Industry
Web Platform
Status
Shipped
project_2
Zakat – Islamic Financial Platform & Dashboard
01Overview

What this system is

Zakat is a frontend web platform built with Next.js to deliver an organized and user-friendly experience around zakat content, educational sections, FAQs, media, and dashboard flows. The project was developed from scratch based on a provided UX structure, with a strong focus on clean component architecture, Arabic RTL support, scalability, and readiness for API integration using Redux.

02The Problem

What we needed to solve

Building a content-rich Islamic platform with multiple sections, dashboard flows, Arabic support, and future API integration requires a clean frontend architecture that can handle scalability, maintainability, and a seamless user experience.

03The Solution

How we shipped it

Developed the full frontend of the platform using Next.js, implementing the provided UX from scratch with reusable components, structured routing, RTL support, dark-ready UI patterns, and Redux-based state preparation for future API integration.

04Architecture

How the system is wired

A modular architecture separating presentation, application, and data layers with REST contracts between the frontend and backend. Designed for clean scaling, observability, and predictable deployments.

Data flow
01
Presentation

Server-rendered + responsive client UI with reusable components and animation primitives.

02
Application

Business logic in service classes, validated input, role-aware authorisation, and queueable side-effects.

03
Data

Relational schema with indexed lookups, soft deletes, and migration-backed evolution.

04
Integration

REST APIs, webhooks, and third-party SDKs surfaced through thin adapters.

05Tech Stack

Engineering choices

Frontend
Next.jsReact.jsTypeScriptSCSSMaterial UIi18next
06Gallery

In the wild

Zakat – Islamic Financial Platform & Dashboard
Zakat – Islamic Financial Platform & Dashboard
Zakat – Islamic Financial Platform & Dashboard
11Challenges Solved

Hard problems, handled

Impact
Challenge 01

Building a content-rich Islamic platform with multiple sections, dashboard flows, Arabic support, and future API integration requires a clean frontend architecture that can handle scalability, maintainability, and a seamless user experience.

Resolution

Developed the full frontend of the platform using Next.js, implementing the provided UX from scratch with reusable components, structured routing, RTL support, dark-ready UI patterns, and Redux-based state preparation for future API integration.

Impact
Challenge 02

Maintaining performance under realistic production load.

Resolution

Indexed queries, paginated lists, image optimisation, and lean client bundles kept the platform responsive end-to-end.

12Performance

Built to stay fast

Optimised images and lazy-loaded routes for fast first paint.
Cached read-heavy endpoints and indexed all hot lookup paths.
Pruned unused dependencies and tree-shook client bundles.
Graceful loading states across every async surface.
13UI / UX

Design and interaction

Consistent design tokens — spacing, type scale, radii, motion curves.
Tuned for both desktop precision and mobile thumb reach.
Empty states, error states, and skeletons across every screen.
Reduced-motion fallbacks and accessible colour contrast.
14Production Readiness

Ready to ship and operate

Environment-scoped configuration with no secrets in source.
Migrations + seeders that recreate the full state from zero.
Error boundaries and logging on critical paths.
Reproducible builds, ready for CI deployment.
15System Features

What it does

Built from scratch based on provided UX design
Multi-page frontend architecture with Next.js
Arabic RTL support
Organized reusable component structure
Dashboard-ready frontend flows
Redux state management setup for API integration
16Technical Decisions

Why we chose what we chose

Decision 01

Built on Next.js, React.js, TypeScript.

Mature ecosystem, strong typing where applicable, and predictable performance characteristics for the workload.

Decision 02

REST-first integration boundary.

Keeps clients (web, mobile, partner) decoupled and trivially swappable without coupling to a single transport.

17Outcome

Results

Production
Status
10+ features
Surface area
8 technologies
Stack depth
Continue exploring

Other case studies

Building something similar?

Let's scope your platform — dashboard, mobile apps, APIs, the full stack.