Work

Selected Unity work and technical case studies.

Internal and project-based examples showing how we approach gameplay systems, technical problem-solving, playable prototypes, and Unity/.NET integrations. Internal work is labeled clearly.

Discuss Your Project Explore Services

Featured Work

Each example explains the objective, systems involved, implementation approach, and the type of client work it demonstrates.

Technical Proof

Focused systems and implementation examples.

Smaller examples drawn from the documented TYPESET implementation, showing specific Unity gameplay, rules, runtime-data, and delivery capabilities.

TYPESET board with completed and incomplete words, scoring, available letters, and error states.

Rule enforcement and word validation

Technical problem

A physical word-game flow relies on rules players can resolve themselves. The digital edition needed to validate actions and make their consequences visible.

What was implemented

The Unity build handles ordered letter placement, word validation, vowels, wild letters, errors, scoring feedback, and complete run state.

  • Unity
  • Rule systems
  • Word validation
  • Gameplay UI
View implementation detail
TYPESET gameplay board showing the mandatory-letter row and available letter pools.

Language-aware rule data

Technical problem

English and Hungarian require different dictionaries and letter pools, including accented characters and multi-character Hungarian tiles.

What was implemented

Separate word lists and JSON letter distributions provide language-specific mandatory letters and vowels without hardcoding one language into the interface.

  • Runtime data
  • JSON configuration
  • English / Hungarian
  • Letter systems
View implementation detail
TYPESET start screen with language controls and a numeric seed entered before starting.

Seeded browser and Windows delivery

Technical problem

A solo digital implementation needed repeatable runs and an accessible way to launch and share the playable build.

What was implemented

The released Unity edition supports optional seed entry, language selection, browser play through HTML5, and a downloadable Windows build.

  • Unity
  • Seeded runs
  • HTML5
  • Windows
View implementation detail

Relevant Services

See the type of engagement each example supports.

Direct proof is identified separately from related and available engagements, so service capability is not presented as a fabricated project result.

Related engagement

Unity Project Audit

Rules, state, input, and runtime data are connected systems an audit can trace for technical risk, unclear ownership, and priority fixes.

View service details

Related engagement

Unity Fix Sprint

Contained validation, interaction, and UI-state problems can be isolated as a focused fix inside an existing Unity project.

View service details

Directly demonstrated

Prototype / Vertical Slice Sprint

TYPESET shows a complete playable loop packaged into builds that can be opened, tested, and evaluated.

View service details

Directly demonstrated

Digital Board Game Prototype

TYPESET shows established tabletop rules translated into enforceable digital interactions and a playable Unity build.

View service details

Available service

Unity Backend Integration

Authentication, player data, APIs, and custom .NET services are available as scoped integration work. No public backend case study is claimed here.

View service details

Have a similar project?

Tell us what your Unity project needs next.

Share the current project state, desired outcome, timeline, and main constraint. We will recommend the smallest useful service and explain the expected scope and next step.

Discuss Your Project