PT

About this portfolio

SEO

100 words

  • Unity
  • Multiplayer
  • LiveOps
  • C#

Leonardo Lycan is a Lead Game Developer specializing in Unity game development, multiplayer architecture, gameplay systems, LiveOps, and technical production. This portfolio brings together published projects, playable prototypes, product studies, and articles on game engineering, applied AI, Web3, onboarding, and digital experiences. The work combines team leadership, C# programming, service integration, performance optimization, and clear communication across design, art, and business. For projects, consulting, or collaboration, Leonardo takes a practical approach: understand the problem, build a robust solution, and turn complex requirements into memorable experiences for players and digital products with measurable, lasting impact for teams, audiences, and product goals.

All courses

Pilot course · Unity + product

From prototype to playable MVP

Turn a gameplay hypothesis into a small, honest, and decisive playable slice.

01 · The transformation

You will leave with a risk map, a vertical-slice structure, and a simple protocol for deciding when a prototype is ready to become an MVP.

02 · Course sample

Open structure · video in production

Open evidence of the kind of reasoning used throughout the complete course.

The sample is in production.

The course structure is open below; the video will be published through YouTube.

Where this lesson comes from

The course reorganizes lessons already documented in the portfolio. Sources remain open so you can compare method and evidence.

Read source insight ↗View related project ↗

03 · Course structure

A path that makes decisions visible.

A risk-led production method: decide what to test first, build a readable vertical slice, and use every build to choose the next step.

01
Start with riskTurn a broad idea into an observable question that can genuinely fail.
  1. 01Hypothesis, behavior, and decision criterion
  2. 02Mapping the risks of the first playableSample
02
Build the smallest honest sliceConnect action, readability, rules, and an ending without anticipating the whole product.
  1. 01Core action and minimum feedback
  2. 02Water Battle Arena across three public builds
03
Use polish as an instrumentAdd presentation only when it makes the player decision easier to read.
  1. 01Feedback that reveals the mechanic
  2. 02What to leave deliberately unfinished
04
From learning to MVPRecord evidence, recognize stability, and turn the slice into a product decision.
  1. 01Hypothesis, observation, and decision log
  2. 02MVP transition checklist

04 · Keep learning

The sample is open. The complete track comes next.

The complete course will be sold and delivered through an external platform. This portfolio does not collect registration or payment.

External platformComplete course coming soon

05 · Supporting courses