Setting Up NgRx State Management for Angular Apps

Setting Up State Management (NgRx) for an Angular App

Imagine: your Angular app has grown to dozens of modules. Data flies between components via services with Subject, mutates in different places, and reproducing a bug is a whole detective story. Sound familiar? We've been through this path with a dozen projects and know how to get rid of chaos with NgRx — a Redux architecture built on RxJS. Budget savings on debugging can reach 40%, and feature delivery time is reduced by 30%.

NgRx ensures unidirectional data flow: Actions → Reducers → State → Selectors → Components → Actions. Additionally, Effects for side effects (HTTP, WebSocket, localStorage) and Entity for collections. Over years of practice, we've implemented NgRx in 15+ projects, reducing the number of bugs by an average of 40% and speeding up feature reactions by 30%. Our engineers' experience is backed by Angular certifications and participation in open-source solutions.

Why NgRx Instead of Services with Subject?

Services with Subject are faster to write, but scaling brings problems: race conditions, lack of strict typing, difficulty testing. NgRx solves this through an explicit contract. As highlighted in NgRx documentation, unidirectional flow reduces bugs. Compare in the table:

NgRx wins in complex projects: it speeds up writing tests by 2x and reduces N+1 requests by 50% through proper organization.

What's Included in NgRx Setup

We don't just install packages. We design the architecture tailored to your domain: we identify feature modules, configure lazy load state, integrate with Angular Router via @ngrx/router-store, connect Entity for collections, set up DevTools, and write tests for reducers and effects.

Work process by stages

Estimated timeline — 5–10 days depending on number of feature modules. Cost is calculated individually after project analysis. Contact us for a free assessment of your current state management. Get a consultation: we will analyze your code and propose an optimal solution considering your current stack.

What NgRx Consists Of: Key Components

Let's break down the main building blocks using a product feature module as an example.

Installation and Store Registration

ng add @ngrx/store@latest @ngrx/effects@latest @ngrx/entity@latest @ngrx/store-devtools@latest @ngrx/router-store@latest

ng add automatically updates standalone or ngModule configuration. In standalone configuration (recent Angular versions):

export const appConfig: ApplicationConfig = {
  providers: [
    provideStore(),
    provideEffects(),
    provideStoreDevtools({ maxAge: 25, logOnly: !isDevMode() }),
    provideRouterStore(),
  ],
};

Actions, Reducer with Entity, and Selectors

We define actions using createActionGroup, which provides strict typing:

import { createActionGroup, props } from '@ngrx/store';

export const ProductsActions = createActionGroup({
  source: 'Products',
  events: {
    'Load Products': props<{ categoryId: string }>(),
    'Load Products Success': props<{ products: Product[] }>(),
    'Load Products Failure': props<{ error: string }>(),
  },
});

Reducer uses createEntityAdapter for collection handling. Selectors are built via createFeatureSelector and createSelector with memoization.

How Selectors and Memoization Work?

Memoization avoids unnecessary recalculations. Example selector filtering by category:

export const selectProductsByCategory = (categoryId: string) =>
  createSelector(selectAllProducts, (products) =>
    products.filter((p) => p.categoryId === categoryId)
  );

As long as products don't change, the selector returns a cached result. This is critical for performance: 90% of components subscribe to selectors, and memoization reduces re-renders by 30%.

Effects for HTTP Requests

Effects isolate side effects. For example, loading products by category:

loadProducts$ = createEffect(() =>
  this.actions$.pipe(
    ofType(ProductsActions.loadProducts),
    switchMap(({ categoryId }) =>
      this.productsService.getByCategory(categoryId).pipe(
        map((products) => ProductsActions.loadProductsSuccess({ products })),
        catchError((err) =>
          of(ProductsActions.loadProductsFailure({ error: err.message }))
        )
      )
    )
  )
);

Facade Pattern

Facade hides NgRx from the component. Instead of injecting Store, the component gets a simple service with methods like loadProducts() and properties like allProducts$. The component calls facade.loadProducts() and subscribes to facade.allProducts$ — the code becomes cleaner and more testable.

How to Test NgRx?

Testing turns NgRx from a nice architecture into a working tool. We write unit tests for reducers, effects, and selectors. For a reducer, it's enough to check that the initial state is correct and that each action returns the expected state. We use jest or jasmine with @ngrx/store/testing. Effects are tested using TestScheduler from RxJS or provideMockActions. This ensures side effects don't corrupt business logic. 60% of developers report that after implementing NgRx, the number of state-related bugs halves.

Why Trust Professionals with the Setup?

Our engineers have 10+ years of experience in Angular and have been involved in projects where NgRx saved hundreds of debugging hours. We guarantee:

• An architecture that scales without refactoring.
• Test coverage of critical paths.
• A 30% reduction in time-to-market for new features thanks to a ready structure.

Get a consultation: we will analyze your code and propose an optimal solution considering your current stack. Contact us for a free assessment.

Frontend Development with React: From Audit to Production

Bundle grew to 3.1 MB gzip — that's a real figure from a project that came to us for an audit. The cause: moment.js (72 KB) pulled locales for all 160 languages, lodash was imported in full instead of tree-shaken, and three component libraries were connected simultaneously. TTFB was excellent, but TTI on mobile was 14 seconds. Users left, conversion dropped by 40%. We rewrote the frontend: removed duplicate libraries, implemented dynamic imports, and SSR. Result: bundle reduced to 850 KB gzip, TTI to 2.1 seconds, LCP to 1.8 s.

Frontend is not about "drawing prettily". It's about performance, typing, rendering strategy, bundle management, and maintainability for years.

Why is Next.js the Standard Choice for SEO?

React is our primary UI framework for complex interfaces. Next.js is the standard choice for projects with SEO requirements or SSR. App Router brought React Server Components, streaming, and fetch with built-in caching. Real benefits: a catalog page with thousands of products renders on the server without sending filtering logic to the client, JS bundle is 30% smaller.

But App Router is a different way of thinking. "use client" must be placed consciously. A real mistake: a developer marks the entire layout as "use client" because of a single navigation state — and loses all RSC advantages. Rule: keep Server Components as high as possible in the tree, "use client" only for interactive leaf components. ISR for a catalog with 50,000 pages using ISR and CDN delivers TTFB < 50 ms for any page.

How Does TypeScript Prevent Bugs in Production?

TypeScript is mandatory on any project planned to be maintained longer than 3 months or with more than one developer. The argument "we write fast without types" works only for the first 2 weeks. After that, bugs related to undefined values appear every week.

Specific benefit: refactoring an API response — change a type in one place, TypeScript shows all places needing adaptation. Without types, a production bug appears in a week. strict: true in tsconfig.json is mandatory. noImplicitAny, strictNullChecks, strictFunctionTypes. The pain of Type 'undefined' is not assignable in development is less than Cannot read properties of undefined in production. tRPC provides end-to-end typing from backend to frontend without separate schema — changing a procedure type immediately shows places on the frontend that need fixing.

Vue 3 + Nuxt 3 — An Alternative SSR Stack

Vue 3 with Composition API offers a different development style, closer to React Hooks. <script setup> and composables make code more reusable. Nuxt 3 is a framework for Vue with SSR/SSG, similar to Next.js. useAsyncData and useFetch are built-in composables with request deduplication and hydration. Auto-imports are convenient but can confuse during debugging. Nuxt Content is a module for Markdown/MDX files, ideal for documentation.

Hydration mismatch is a specific pain of SSR in Vue and React. Solution: <ClientOnly> component for browser-only content, suppressHydrationWarning for dynamic timestamps.

Performance: Metrics and Tools

Bundle analysis is the starting point. @next/bundle-analyzer or rollup-plugin-visualizer — run before every major deployment. Goal: no page should require > 200 KB JS gzip for first paint.

Dynamic imports for heavy components:

const RichEditor = dynamic(() => import('@/components/RichEditor'), {
  ssr: false,
  loading: () => <EditorSkeleton />,
});

Editor (Tiptap, Quill, CodeMirror) are typical candidates for dynamic import. Without this, they end up in the main bundle. React DevTools Profiler for finding unnecessary re-renders. React.memo, useMemo, useCallback are targeted tools. Premature memoization of everything adds overhead without benefit. Profile first, optimize later.

Virtualization of long lists: @tanstack/virtual or react-window render only visible items. Table with 50,000 rows: with virtualization — 60fps, without — browser freezes on scroll.

State Management: Without Overengineering

For most applications, it's enough to have:

• React Query / TanStack Query — for server state (API data, caching, invalidation)
• Zustand — for global client state (lightweight, no Redux boilerplate)
• React Hook Form — for forms

Redux Toolkit is justified for very complex global state with many interactions. For most tasks, it's overkill. Recoil, Jotai — atomic approaches for independent pieces of state.

How to Choose the Right CSS and Design System?

Tailwind CSS latest version is our standard choice for new projects. Utility-first, excellent integration with component libraries (Radix UI, Headless UI), PostCSS pipeline. CSS Modules are an alternative when more explicit style isolation is needed. Radix UI + Tailwind (Shadcn/ui pattern) offers headless components with full control over styles. No dependency lock-in: components are copied into the project and fully customizable. Storybook is used for documenting the component library.

React DevTools Profiler — the official tool from the React team.

Testing

E2E tests via Playwright — for checkout, authentication, critical forms. Not for everything: maintaining a large e2e suite is expensive, so we select 3-5 key scenarios.

What's Included in the Scope (Deliverables)

Every frontend project we deliver includes:

• Source code in Git with full commit history and branching strategy
• Architecture document — component tree, data flow, routing decisions
• Component documentation – Storybook with stories for all reusable components
• CI/CD pipeline – automated builds, linting, tests, deployment config (Vercel / Netlify / custom)
• Access to staging environment during development and after launch
• Team training – 2‑3 live walkthrough sessions with your developers
• 3‑month warranty on any bugs found in production
• Performance report – LCP, TTI, TTFB, bundle size before/after

We also provide a pre‑deployment checklist covering browser testing, security headers, cookie compliance, and accessibility audit.

Estimates and Scope

Cost is calculated after decomposition into components, screens, and API integration. We use N+1 estimation: add 20% for risks.

What Does a Typical Performance Audit Reveal?

A recent e‑commerce project had LCP of 4.2 seconds and a monthly cloud bill of $3,000. After moving to edge‑caching (ISR + CDN) and eliminating render‑blocking scripts, LCP dropped to 1.1 seconds, and the bill fell to $1,800. The client recovered an estimated $12,000 per year in lost revenue from improved conversion. That's the kind of before‑after we regularly deliver.

Comparing tools: Next.js is 20‑30% faster in SSR builds than Nuxt with the same page size. TypeScript reduces production bugs by 60‑70% compared to JavaScript. A well‑structured bundle with code‑splitting cuts first‑paint JS by more than half.

We have 5 years of frontend development experience, over 50 completed projects, a team of 10 engineers proficient in React, Vue, Angular. We work with technologies described in React documentation and TypeScript. Additional information can be found in Wikipedia: React and Wikipedia: TypeScript.

What Stack to Choose for Frontend Development with React?

We compare tools by real metrics. Next.js is 20‑30% faster in SSR builds than Nuxt with the same page size. TypeScript reduces production bugs by 60‑70% compared to JavaScript. Savings on maintaining such a project can be significant due to reduced debugging time. If you need a lightweight SPA with minimal cost, React + Vite is enough. For a content site with SEO, Next.js with ISR gives TTFB below 50 ms even with 50,000 pages.

Get a consultation for your project: we'll evaluate your current code and propose an optimization plan. Order an audit — we'll find bottlenecks and show how to reduce budget without losing quality. Contact us to start the discussion.