Suppliers, clients and administrators need distinct procurement experiences. Supporting pricing requests, contracts and supply orders in multiple languages adds complexity that a duplicated frontend cannot sustainably manage.
What I built
I built a modular Next.js application with role-specific dashboards, shared feature modules, API-driven server state and internationalized routing. The interface supports Arabic, English, Hindi and Chinese with automatic RTL/LTR behavior.
02 / ARCHITECTURE & TECHNICAL DECISIONS
Engineering with intent.
01
Shared features, role-specific experiences
Reusable feature modules and UI patterns support separate application areas without duplicating the underlying frontend architecture.
02
Server state has its own lifecycle
TanStack Query manages API-driven state. React Hook Form and Zod give complex procurement forms typed validation and consistent interaction patterns.
03
Internationalization at the routing layer
next-intl and direction-aware layouts support four languages. RTL/LTR behavior is part of the application structure rather than an isolated styling patch.
