React Component Lifecycle Infographic | Computer Network Diagram Drawing Tool

Tech architecture infographic titled "React Component Lifecycle" using archetype HOW-IT-WORKS. Show a clear beginner-friendly React lifecycle diagram as a flat/isometric technical infographic with labeled boxes connected by directional arrows. Include these component boxes: 1) "Browser" — icon: retro CRT monitor — role: "Renders DOM and runs JavaScript"; 2) "React Component" — icon: UI window block — role: "Defines state, props, and UI output"; 3) "Props Input" — icon: incoming arrows — role: "Provides external data from parent component"; 4) "State Store" — icon: memory chip — role: "Holds local mutable component data"; 5) "Render Phase" — icon: wireframe layout — role: "Computes virtual UI from props and state"; 6) "Virtual DOM" — icon: stacked layers — role: "Represents the next UI tree in memory"; 7) "Reconciliation" — icon: compare/diff symbol — role: "Finds changes between previous and next trees"; 8) "DOM Update" — icon: document node — role: "Applies minimal changes to the real DOM"; 9) "Effects / Lifecycle Hooks" — icon: gear cycle — role: "Runs side effects after render or on dependency change"; 10) "Cleanup" — icon: broom or disconnect plug — role: "Removes subscriptions, timers, and listeners before rerun or unmount"; 11) "Unmount" — icon: eject/remove symbol — role: "Removes component from the UI tree". Use arrows with short English labels: "initial mount", "receive props", "setState()", "render()", "virtual tree", "diff result", "patch DOM", "useEffect()", "cleanup()", "unmount", "re-render". Show the lifecycle flow accurately: Props Input and State Store feed React Component, React Component enters Render Phase, Render Phase produces Virtual DOM, Reconciliation compares trees, DOM Update patches Browser DOM, then Effects / Lifecycle Hooks run after commit, Cleanup runs before effect rerun and before Unmount, state or props changes loop back into Render Phase for re-render. Add small optional side boxes for "Event Handler" — "Responds to user input" and "Async Data Fetch" — "Loads remote data and updates state", connected with arrows labeled "click event" and "JSON data". Include subtle generic cloud icon only if showing remote data, with no vendor branding. Add a numbered legend (1-7) in English: 1. "Component mounts with initial props and state." 2. "React calls render() to calculate the next UI." 3. "A new Virtual DOM tree is created in memory." 4. "Reconciliation compares old and new trees." 5. "React updates only the changed DOM nodes in the browser." 6. "useEffect() runs after the DOM commit; cleanup runs before rerun or unmount." 7. "Prop changes, state updates, or events trigger another render cycle until unmount." Visual style: retro 1980s computing, blueprint cyan palette, neon cyan lines on deep navy background, faint grid paper, glowing vector outlines, technical drafting annotations, nostalgic terminal-inspired accents, editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Keep layout uncluttered, highly readable for a curious beginner, with large headings, simple arrows, and educational spacing. All text MUST be written in English (array). Every heading, label, caption, legend and metric name in the image must be in English — not English. Spell each English word correctly using English characters and diacritics. Numbers stay as digits, no real cloud-vendor logos (AWS / GCP / Azure) — use generic cloud icons, no watermarks No real cloud-vendor logos (AWS, GCP, Azure) beyond generic cloud icons. Common protocol names (HTTPS, TCP, JWT, OAuth, REST, GraphQL) stay in canonical English form. No security-claim overstatements (do not present diagrams as audited reference architectures).