Amid
All work
02HealthcareJan 2024 — Aug 2024

Health Cloud Platform

A healthcare and HR management platform built on a micro-frontend architecture, so features could be developed and deployed independently without giving up performance or code quality.

Organization IPJ Company

Role Frontend Developer

Application performance improvement
20%Application performance improvement
Reduction in production incidents
15%Reduction in production incidents
Feature development and deployment
IndependentFeature development and deployment

01

Overview

IPJ Company builds healthcare and HR management platforms. The Health Cloud is the healthcare product: a platform where several feature areas evolve on their own timelines but present as one application.

I built the Health Cloud frontend on a micro-frontend architecture and worked across the wider product surface with React and Next.js.

02

The Problem

Independent development and deployment is easy to state and hard to get for free. Splitting an application into independently deployable features can trade one problem for two others: duplicated work degrading performance, and inconsistent quality across boundaries no single team owns.

The architecture had to deliver independence and hold performance and code quality at the same time.

03

My Approach

A shell application owns the shared shell — routing, layout and cross-cutting concerns — and each feature is developed and deployed on its own behind that boundary.

Performance was treated as a measured property, not an assumption: profile first with Lighthouse and the React DevTools Profiler, then change what the measurements point at. Quality was handled the same way — through review, pairing and systematic debugging rather than one-off fixes.

04

Architecture & Technical Decisions

Shell application · routing, layout, shared shell
Feature A
Independent deployment
Feature B
Independent deployment
Feature C
Independent deployment

Feature names are illustrative. Each feature owns its own build and release; the shell owns everything shared.

A shell hosts independently developed and deployed features behind one shared application surface.
  • Micro-frontend structure so feature areas can be developed and deployed independently.
  • Zustand for local and shared client state, kept deliberately small and explicit.
  • RTK Query for server data, so caching and invalidation are handled in one place per feature.
  • Systematic performance profiling with Lighthouse and the React DevTools Profiler as a routine step, not a rescue operation.

05

My Contribution

  • Built the Health Cloud using micro-frontend architecture.
  • Developed frontend applications with React and Next.js.
  • Optimized state management using Zustand and RTK Query.
  • Performed systematic performance profiling.
  • Improved code quality and maintainability.
  • Mentored junior developers through code reviews and pair programming.

06

Outcome

  • 20% improvement in application performance, measured using Lighthouse and the React DevTools Profiler.
  • 15% reduction in production incidents through systematic debugging, profiling and code-quality improvements.

07

Technology

  • React
  • Next.js
  • TypeScript
  • Zustand
  • RTK Query
  • Micro-Frontend