The visible feature was only the surface
An inventory interface needs to connect sign-in, item browsing, stock updates, and personal item lists while coordinating browser state with a separate API.
The system also had to respect concrete constraints. The client embeds a legacy Heroku API address; current end-to-end operation was not verified. Only some account-oriented routes use the client authentication guard; backend authorization remains a separate responsibility. This client references warehouse-management-server, not inventory-management-system-server.
My role covered react frontend and inventory workflow development, with responsibility for client routing, firebase authentication integration, inventory request flows, and item-management screens.
I turned the constraints into boundaries
A legacy React inventory client with Firebase sign-in, item browsing, stock update and delivery controls, and user-specific item pages. Data workflows depend on a separate POSDash API.
React screens manage interaction while inventory persistence depends on a separately hosted service.
Firebase initialization, authentication guards, and a token hook centralize parts of the client integration.
Client guards describe navigation behavior and do not establish server-side permission enforcement.
The key decision: Separate client and API responsibilities.
The implementation had to prove the model
I delivered the work across the full path: Built inventory browsing and item-management routes. Integrated Firebase sign-in and API token request helpers. Added request flows for stock updates and delivery controls.
The result is concrete: The source demonstrates a browser-to-API inventory workflow. Account and inventory screens share routing and identity helpers. The project records early React integration work; hosted workflow success and business impact are unverified.
The senior engineering lesson was that solving the visible workflow is only half the job. The architecture must also make constraints, failure modes, evidence, and ownership explicit enough for the next change to remain safe.