Skip to main content

Refraction Getting Started

Outcome​

Use this page to confirm whether Refraction is the right place to start and which package boundary matches your UI question.

What You Will Achieve​

By the end of this page, you should know whether your task is about state-down, events-up Blazor components, Reservoir-style client state, or another Mississippi layer.

Before You Begin​

First Verified Success​

  1. Read the Refraction overview and confirm the problem is about the UI interaction contract rather than the state-management model.
  2. Open Refraction Reference and identify which Refraction package boundary matches the question you are trying to answer.
  3. If the core issue is really store behavior, switch to Reservoir before going further.

Choose Your Starting Point​

  • Start with Mississippi.Refraction.Abstractions when you need the contracts behind the UI layer.
  • Start with Mississippi.Refraction.Client when you need the Blazor component layer itself.
  • Start with Mississippi.Refraction.Client.StateManagement only when the question is about Refraction's composition helpers around client state.

Verify You Are In The Right Section​

  • Stay in Refraction when the concern is component interaction contracts and UI composition.
  • Move to Reservoir when the concern is the store, reducers, effects, or selectors.

Verify The Result​

  • You should be able to state whether the issue is UI contract first or state-management first.

Current Scope​

This page covers package selection and subsystem orientation. For a runnable Blazor UI example using Refraction, see the Spring sample.

Summary​

Refraction is the right entry point when the problem is the Blazor UX contract itself: state down, events up.

Next Steps​