Ac Client State And Interaction

Client-side state as its own engineering problem: server cache versus UI state and the data layer that separates them, optimistic updates and rollback on failure, finite state machines for interaction logic, undo and redo as a command history, list virtualization for long lists, offline reads and writes on the web with background sync, and the written client-state record. It explains the client data layer and interaction mechanics; it never recommends a framework and never promises an offline app. Use when asking "server state versus client state", "optimistic update", "state machine UI", "undo redo implementation", "virtualized list", "offline first web", "background sync", "stale while revalidate", "undo history", "when to refetch". Not for component structure and state placement basics (ac-frontend-ui), not for mobile offline sync (ac-mobile-client-engineering), not for WCAG conformance (ac-frontend-ui).

jiayaoqijia Updated 81 repo stars

File contents

jiayaoqijia/cryptoskill commit 2ca5f450b3

Frequently asked questions

npx get-skill add jiayaoqijia/ac-client-state-and-interaction