Skip to content

POSDash Client

website

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.

Client: nDevers · View client experience

Role
React frontend and inventory workflow development
Scope
Client routing, Firebase authentication integration, inventory request flows, and item-management screens
Status
Legacy learning/reference project; current runtime and production readiness unverified

Problem

An inventory interface needs to connect sign-in, item browsing, stock updates, and personal item lists while coordinating browser state with a separate API.

Constraints

  1. C1

    The client embeds a legacy Heroku API address; current end-to-end operation was not verified.

  2. C2

    Only some account-oriented routes use the client authentication guard; backend authorization remains a separate responsibility.

  3. C3

    This client references warehouse-management-server, not inventory-management-system-server.

Architecture

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.

01

Client routes

React Router maps inventory, item details, account, and static information screens.

02

Identity and requests

Firebase handles client sign-in; a token hook sends an email to the API and stores the returned token locally for requests.

03

Inventory interaction

Item-detail request code loads records and submits stock and delivery updates to the separate API.

Decisions

D1

Separate client and API responsibilities

React screens manage interaction while inventory persistence depends on a separately hosted service.

D2

Reuse identity and request helpers

Firebase initialization, authentication guards, and a token hook centralize parts of the client integration.

D3

Distinguish route behavior from authorization

Client guards describe navigation behavior and do not establish server-side permission enforcement.

Contribution

  • 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.

Outcomes

  • 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.

Verified stack

  • JavaScript
  • React
  • React Router
  • Firebase Authentication
  • Axios
  • Tailwind CSS

Working through something similar?

Share your challenge, scope, and timeline to start a focused conversation.

Discuss a project