Skip to content
Projects

prod-forge/frontend has 329 GitHub stars and 32 forks. GitHot measured +2 stars in 24 hours. Last checked 2026-11-19 02:44 UTC. Last push 2026-11-15.

How these counts are measured

Measured star growth

in 24h
+2
in 7 days
Collecting history
in 15 days
Collecting history
in 1 month
Collecting history

Net star changes over overlapping periods, not daily totals. Missing measurements are left blank. Stars measure attention, not software quality.

About

Prod Forge frontend: React web client, Expo mobile client and design system with production-grade quality gates

Web & Apps

README.md

Original

Prod Forge

AI made writing the code easy. Running it in production is still hard.

This repository holds the web and mobile clients in one NX monorepo, with a shared design system. It answers: how do I build, ship, and keep web and mobile clients healthy?

Part of Prod Forge — start with the organization overview: https://github.com/prod-forge

Stack

Layer Tools
Web Client React · Vite · Redux Toolkit · Tailwind CSS · NX
Mobile Client Expo · React Native · Redux Toolkit
Quality ESLint · Prettier · Husky · Commitlint · CI/CD

The full stack table is on the organization page: https://github.com/prod-forge

Getting started

Requires Node 24 and the backend API running (see the backend guide).

npm ci
cp .env.example .env   # VITE_API_BASE_URL is required for a build (absolute URL ending with "/"); dev falls back to the /api/v1/ proxy
npm run dev            # web client
cp apps/mobile-client/.env.example apps/mobile-client/.env   # EXPO_PUBLIC_API_BASE_URL, mobile client only
npm run dev:mobile     # mobile client (Expo)

Table of contents

Conclusion

A frontend is easy to start and hard to keep healthy.

The first screen takes an afternoon. What takes years is everything around it: two clients that must agree on the same rules, a bundle that grows a little with every feature, an error a user saw that nobody can reproduce, a release that has to be rolled back on a Friday evening, and a design that drifts a pixel at a time until nobody trusts it.

This repository is an attempt to show that work, not just the screens.

The stack - React, Expo, Redux Toolkit, Tailwind, NX - is not the point. These are just tools. The principles behind them apply to almost any client, whatever framework comes next.

What matters is the thinking:

  • Why does sharing a store and an API layer between web and mobile pay off only with a strict dependency direction?
  • Why should a design system live in the repository, with tokens, stories and visual tests, and not in a design file?
  • Why does a client need its own observability when the backend already logs every request?
  • Why is the browser an untrusted environment, and what does that change about tokens and configuration?

These are not advanced topics. They are basic requirements for any client that real users depend on. The goal of Prod Forge is to make these practices visible, understandable, and reusable.

What comes next

Open work is tracked in the roadmap and summarized on the organization page.

A final thought

The best time to set up these practices is at the beginning of a project.

The second best time is now.

A client without error tracking leaves you guessing about what users actually saw. A design system without visual tests drifts until nobody trusts it. A bundle without a budget only grows. A release without a rollback path turns a small mistake into an outage.

None of these things are difficult to set up. They are just easy to skip. This project exists as a reminder not to skip them.

Intentionally out of scope

  • Passwords, refresh tokens, sign-up and an identity provider: the clients sign in with the backend's login stub, see Security
  • Store release of the mobile app: no EAS Build, EAS Submit or over-the-air updates, see Mobile Client
  • Running CI: the workflows exist but are disabled on purpose, see the roadmap

Contributing

We welcome any kind of contribution, please read the guidelines:

CONTRIBUTING

The MIT License

LICENSE