Domäne
Frontend Development
Skill-Profil
Zustand, Redux Toolkit, Pinia, Jotai: global state, server state
Rollen
7
wo dieser Skill vorkommt
Stufen
5
strukturierter Entwicklungspfad
Pflichtanforderungen
33
die anderen 2 optional
Frontend Development
State Management
17.3.2026
Wählen Sie Ihr aktuelles Level und vergleichen Sie die Erwartungen.
Die Tabelle zeigt, wie die Tiefe von Junior bis Principal wächst.
| Rolle | Pflicht | Beschreibung |
|---|---|---|
| Desktop Developer (Electron/Tauri) | Pflicht | Uses React Context and useState for renderer state management. Understands the need for centralized state for multi-window. Works with localStorage/electron-store for persistence. |
| Frontend Developer (Angular) | Pflicht | Manages state in Angular via services with BehaviorSubject and Angular signals. Understands the difference between local component state and global application state. Uses @Input/@Output for communication. |
| Frontend Developer (React) | Pflicht | Manages local React component state through useState and useReducer. Uses Zustand for global state (theme, user, UI states), understands lifting state up and passing through props and React Context. |
| Frontend Developer (Svelte) | Pflicht | Manages local state in Svelte components through $state and $derived runes, uses writable/readable stores for shared state. Understands Svelte 5 reactivity: automatic dependency tracking, $effect for side effects on data changes. |
| Frontend Developer (Vue) | Pflicht | Uses Pinia for Vue application state management — defining stores through defineStore, reactive state, getters, actions. Understands when to use component local state vs Pinia store. |
| Fullstack Developer | Pflicht | Manages fullstack application state at a basic level: useState/useReducer for local state, context for global data (theme, user). Understands the difference between server and client state in full stack context. |
| React Native Developer | Uses useState and useContext for managing local state in React Native components. Understands lifting state up between screens. Applies basic Zustand store for global state — authentication, theme, app language. |
| Rolle | Pflicht | Beschreibung |
|---|---|---|
| Desktop Developer (Electron/Tauri) | Pflicht | Applies state management tools. Synchronizes state between main and renderer through IPC. Implements persistence middleware. Works with optimistic updates. |
| Frontend Developer (Angular) | Pflicht | Applies NgRx for state management: Store for global state, createFeature for feature state, Effects for side effects. Migrates to NgRx SignalStore for simpler cases. |
| Frontend Developer (React) | Pflicht | Designs state management in React applications: separation of server (TanStack Query) and client (Zustand/Jotai) state, re-render optimization through selectors and atomic state. Implements derived state, middleware in Zustand for logging and persistence. |
| Frontend Developer (Svelte) | Pflicht | Designs SvelteKit application state: global stores for auth and settings, context API for tree-scoped data, $state for forms. Implements optimistic updates through form actions, synchronizes server and client state through load invalidation. |
| Frontend Developer (Vue) | Pflicht | Designs Pinia store structure — modular organization, composable stores, plugins for persistence and devtools. Uses VueUse composables for global state — useStorage, useBreakpoints, createSharedComposable. |
| Fullstack Developer | Pflicht | Independently implements complex UI components with State Management. Optimizes rendering performance. Writes tests. Applies for state management. |
| React Native Developer | Architects state with Zustand — slice separation, subscriptions, middleware. Integrates TanStack Query for server state, Zustand/Jotai for client state. Implements persist with MMKV for offline access. Optimizes re-renders through selectors and shallow comparison. |
| Rolle | Pflicht | Beschreibung |
|---|---|---|
| Desktop Developer (Electron/Tauri) | Pflicht | Designs state architecture for multi-window Electron: shared state through main process, window-local state. Implements undo/redo through immer patches. Optimizes state updates for large datasets. |
| Frontend Developer (Angular) | Pflicht | Designs Angular application state architecture: separating UI/domain/server state, NgRx Entity for normalization, SignalStore with patchState for local state, selectSignal optimization. |
| Frontend Developer (React) | Pflicht | Architects state management for complex React applications: domain-based state separation strategy, cross-tab synchronization through Zustand middleware, optimistic updates with rollback. Designs state machines through XState for complex UI flows. |
| Frontend Developer (Svelte) | Pflicht | Develops state management architecture for complex Svelte applications: state machines through XState, normalized stores, event-driven patterns. Designs offline-first state with IndexedDB synchronization, creates dev tools for debugging $state and stores. |
| Frontend Developer (Vue) | Pflicht | Designs scalable state architecture — Pinia with domain-driven modules, optimistic updates, offline sync. Implements server state management through Nuxt useState, creates caching and invalidation abstractions. |
| Fullstack Developer | Pflicht | Designs state management for fullstack applications: Zustand/Jotai for client state, React Query for server state, separating cache from UI state. Implements optimistic updates with rollback on API errors and cross-tab synchronization. |
| React Native Developer | Pflicht | Architects state management for large-scale React Native applications. Implements patterns — server state vs client state, optimistic updates, derived state via Jotai atoms. Designs state synchronization between devices and offline-first persistence. |
| Rolle | Pflicht | Beschreibung |
|---|---|---|
| Desktop Developer (Electron/Tauri) | Pflicht | Defines state management strategy for the Electron platform. Establishes state design patterns. Coordinates state architecture across modules. |
| Frontend Developer (Angular) | Pflicht | Defines state management standards: when to use services vs NgRx vs SignalStore, server state handling patterns, migration strategy to signal-based state management, NgRx pattern code reviews. |
| Frontend Developer (React) | Pflicht | Standardizes state management approaches in the team's React projects: unified stack (Zustand + TanStack Query), store structure conventions, patterns for typical scenarios. Defines boundaries between server and client state in Next.js App Router architecture. |
| Frontend Developer (Svelte) | Pflicht | Defines state management standards in the Svelte team: when to use $state vs stores vs context, patterns for server state. Trains the team on idiomatic Svelte 5 approach, introduces best practices for predictable data flow in SvelteKit applications. |
| Frontend Developer (Vue) | Pflicht | Defines state management strategy for Vue projects — modular Pinia architecture, cross-tab sync, migration patterns. Introduces store organization standards, trains teams on complex state management patterns. |
| Fullstack Developer | Pflicht | Defines state architecture for the fullstack platform: server vs client state strategy, data normalization, real-time updates through WebSocket. Creates standard patterns and utilities for the team, ensures predictable data flows. |
| React Native Developer | Pflicht | Defines the state management strategy for the team's mobile apps. Establishes tool selection guidelines — Zustand vs Jotai vs Redux Toolkit. Reviews state architecture for memory leaks and unnecessary re-renders. Implements state performance metrics. |
| Rolle | Pflicht | Beschreibung |
|---|---|---|
| Desktop Developer (Electron/Tauri) | Pflicht | Shapes enterprise state management standards for Electron. Evaluates state library evolution. Defines data flow architecture. |
| Frontend Developer (Angular) | Pflicht | Shapes state management strategy for the Angular platform: unifying approaches across teams, state separation in micro-frontends, cross-tab state synchronization, server state via Angular Universal. |
| Frontend Developer (React) | Pflicht | Defines state management strategy for the React application ecosystem: distributed state architecture, synchronization between micro-frontends, legacy solution migration strategy. Shapes platform-level abstractions for unified state management. |
| Frontend Developer (Svelte) | Pflicht | Shapes state management strategy at the organizational level, researches new Svelte 5 rune capabilities for large-scale applications. Defines architectural patterns for state synchronization between SSR, client, and real-time sources in the SvelteKit ecosystem. |
| Frontend Developer (Vue) | Pflicht | Shapes state management strategy for Vue ecosystem — shared state between micro-frontends, event-driven architecture, CQRS. Researches signal-based reactivity, atomic stores and other state management evolutions. |
| Fullstack Developer | Pflicht | Shapes organizational state management strategy: unified approaches for fullstack applications, distributed state, offline-first architecture. Designs platform solutions for data synchronization between client, server and database. |
| React Native Developer | Pflicht | Shapes enterprise state management standards for mobile applications. Defines data synchronization strategy between mobile clients and backend services. Designs reference architecture for offline-capable applications with predictable state management. |