State machines with composables in Vue - Performance & Optimization

Performance: State machines with composables

MEDIUM IMPACT

This affects how efficiently the UI updates in response to state changes and how much unnecessary work the browser does during rendering.

Managing complex UI states with predictable transitions

Vue

import { createMachine, interpret } from '@xstate/fsm';
const machine = createMachine({
  initial: 'idle',
  states: {
    idle: { on: { START: 'loading' } },
    loading: { on: { FINISH: 'success' } },
    success: {}
  }
});
const service = interpret(machine).start();
const state = ref(service.state.value);
service.onTransition(s => { state.value = s.value; });

State machine enforces clear transitions, reducing unnecessary state changes and renders.

📈 Performance Gainsingle re-render per valid state change, improving input responsiveness

Managing complex UI states with predictable transitions

Vue

const state = ref('idle');
function start() { state.value = 'loading'; }
function finish() { state.value = 'success'; }
// UI watches state and updates directly without clear transition rules

Directly changing state without a structured machine causes unpredictable renders and possible redundant updates.

📉 Performance Costtriggers multiple re-renders and layout recalculations on unclear state changes

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Direct state changes without machine	High (many updates)	Multiple reflows per state change	High paint cost due to redundant updates	[X] Bad
State machines with composables	Minimal (only on valid transitions)	Single reflow per transition	Lower paint cost due to fewer updates	[OK] Good

Rendering Pipeline

State machines with composables control state changes explicitly, reducing unnecessary style recalculations and layout thrashing by limiting when the UI updates.

→Style Calculation

→Layout

→Paint

⚠️ BottleneckLayout due to frequent or redundant state-triggered DOM updates

Core Web Vital Affected

INP

This affects how efficiently the UI updates in response to state changes and how much unnecessary work the browser does during rendering.

Optimization Tips

1Use state machines to control and validate UI state transitions.

2Avoid direct, unstructured state changes that cause redundant renders.

3Monitor layout recalculations in DevTools to catch performance issues.

Performance Quiz - 3 Questions

How do state machines with composables improve UI performance?

A By enforcing clear state transitions and reducing unnecessary renders

B By increasing the number of state updates to keep UI fresh

C By delaying all state changes until user interaction stops

D By removing all state from the UI components

DevTools: Performance

How to check: Record a performance profile while interacting with the UI. Look for frequent layout and paint events triggered by state changes.

What to look for: Fewer layout recalculations and paint events indicate efficient state management with state machines.

Practice

1. What is the main purpose of using a state machine in a Vue composable?

easy

A. To manage and control the different states of an application clearly and predictably

B. To style components dynamically based on user input

C. To fetch data from an API asynchronously

D. To create reusable UI components without state

Solution

1. Step 1: Understand state machine role

   A state machine helps track and control states in a clear way, avoiding unpredictable behavior.

2. Step 2: Relate to Vue composables

   Vue composables organize this logic so it can be reused across components easily.

3. Final Answer:

   To manage and control the different states of an application clearly and predictably -> Option A

4. Quick Check:

   State machine purpose = Manage states clearly [OK]

Hint: State machines organize app states clearly, not styling or fetching [OK]

Common Mistakes:

• Confusing state machines with styling or data fetching
• Thinking composables only create UI components
• Assuming state machines handle API calls

2. Which of the following is the correct way to declare a reactive state variable for a state machine in a Vue composable?

easy

A. const state = reactive('idle')

B. const state = ref('idle')

C. const state = computed('idle')

D. const state = watch('idle')

Solution

1. Step 1: Identify reactive state declaration

   In Vue composables, ref is used to create a reactive primitive value like a string.

2. Step 2: Check other options

   reactive is for objects, computed is for derived values, and watch is for side effects, so they are incorrect here.

3. Final Answer:

   const state = ref('idle') -> Option B

4. Quick Check:

   Use ref for reactive primitives [OK]

Hint: Use ref() for reactive simple values like strings [OK]

Common Mistakes:

• Using reactive() for primitive values
• Confusing computed() with state declaration
• Using watch() to declare state

3. Given this Vue composable code, what will be the value of state.value after calling next() twice?

import { ref } from 'vue'

export function useMachine() {
  const state = ref('idle')
  function next() {
    if (state.value === 'idle') state.value = 'loading'
    else if (state.value === 'loading') state.value = 'success'
  }
  return { state, next }
}

medium

A. 'idle'

B. 'loading'

C. 'success'

D. undefined

Solution

1. Step 1: Trace first next() call

   Initial state is 'idle'. Calling next() changes it to 'loading'.

2. Step 2: Trace second next() call

   Now state is 'loading'. Calling next() again changes it to 'success'.

3. Final Answer:

   'success' -> Option C

4. Quick Check:

   Two next() calls move state from idle -> loading -> success [OK]

Hint: Trace state changes step-by-step for each next() call [OK]

Common Mistakes:

• Assuming state resets to 'idle'
• Forgetting second next() changes state again
• Confusing state.value with state itself

4. Identify the error in this Vue composable state machine code:

import { ref } from 'vue'

export function useMachine() {
  const state = ref('idle')
  function next() {
    if (state === 'idle') state.value = 'loading'
    else if (state.value === 'loading') state.value = 'success'
  }
  return { state, next }
}

medium

A. next() function is not returned

B. Missing import of ref from 'vue'

C. Cannot assign to state.value, should assign to state

D. Incorrect comparison: should use state.value instead of state

Solution

1. Step 1: Check state comparisons

   state is a ref object, so to compare its value, use state.value, not state directly.

2. Step 2: Verify other parts

   Import is correct, assignment to state.value is correct, and next() is returned properly.

3. Final Answer:

   Incorrect comparison: should use state.value instead of state -> Option D

4. Quick Check:

   Compare ref values with state.value [OK]

Hint: Always compare ref values with .value, not the ref object [OK]

Common Mistakes:

• Comparing ref object instead of its value
• Forgetting to return functions from composable
• Misassigning to ref object instead of .value

5. You want to extend a Vue composable state machine to handle a 'failure' state after 'loading'. Which change correctly adds this new state transition when next() is called from 'loading'?

hard

A. Add an else if: else if (state.value === 'loading') state.value = 'failure'

B. Replace the existing loading transition with state.value = 'failure' only

C. Add a new function to set state to 'failure' instead of modifying next()

D. Change initial state to 'failure' to handle errors

Solution

1. Step 1: Understand current transitions

   Currently, next() changes 'idle' -> 'loading' -> 'success'. To handle 'failure' after 'loading' when next() is called, add a new else if condition for 'loading' to transition to 'failure'.

2. Step 2: Identify correct addition

   Adding an else if for state.value === 'loading' to set state.value = 'failure' extends the state machine correctly without removing existing transitions.

3. Final Answer:

   Add an else if: else if (state.value === 'loading') state.value = 'failure' -> Option A

4. Quick Check:

   Add new transition for loading -> failure without removing others [OK]

Hint: Add a new else if condition for the failure state [OK]

Common Mistakes:

• Adding a duplicate else if for 'loading' which conflicts or is unreachable
• Adding separate functions instead of modifying next()
• Changing initial state instead of the transition