Case study / MVP completed
Itera
A web MVP that compares progression paths and explains a character’s next step using auditable rules.
Problem and user
MMORPG guides offer many options but rarely explain which path matches the character, goal and acceptable risk at a given moment.
My role
Product vision, rule definition, initial architecture and interface implementation.
Delivered scope
- Character profile and goal selection
- Validated forms
- Comparison of three paths
- Accessible recommendations with explanations
Constraints
- Small local catalog without dynamic data
- No backend, database or AI yet
- Explore the hypothesis before expanding the scope
Architecture and data flow
React and TypeScript with Vite form the web application in a pnpm workspace; Sass styles the interface; React Hook Form and Zod validate data; the Path Engine filters eligibility and calculates a deterministic ranking entirely in the browser.
Decisions and trade-offs
Keep rules auditable before adding AI to reduce risk, explain recommendations and validate the journey before building an API and persistence.
Tests and validation
The repository includes Path Engine tests, lint and build commands, and inline form validation.
Current state
Web MVP with a local Path Engine: eligibility, scoring and up to three explained recommendations.
Known limitations
- Limited local catalog; no backend, database, authentication or AI.
Next steps
- Validate path comparisons with players
- Define the API and persistence after validating the journey
Related training
- Components and useState — Open Theme — Outstanding Achievement ↗
React components and state support the form and path comparison.
- Module 1 — Programming Logic ↗
Programming logic applied to eligibility rules and deterministic ranking.
Stack
- React 19
- TypeScript
- Vite
- Sass
- React Hook Form
- Zod
- pnpm workspaces
- Docker