Independent creative technology studio · Selected work 2026

Selected work

Three working systems. See what each one does and how it is structured.

W.01 · Tournament & team operations

Drone Soccer Fest

One operation, four roles.

A multi-role platform where admins, coaches, parents and students run one controlled tournament workflow.

Invitations, approvals, eligibility and payments cross four consoles while the system keeps a single consistent state.

Concept visuals with illustrative data. The real screens are kept private.

Drone Soccer Fest concept visual: an operations overview on desktop with approval, team and payment queues, and a coach's team view on a phone. The data is illustrative.
100%
E.01Operations overview · Desktop and mobileConcept visual

The admin overview brings pending coach approvals, students without a team, under-staffed squads, payments and documents into one place. Every count opens its queue.

Drone Soccer Fest coach dashboard concept visual: teams, a step-by-step festival application, the schedule, invitations and announcements. The data is illustrative.
100%
E.02Coach dashboard · DesktopConcept visual

The coach dashboard allows coaches to manage their teams, students, invitations and tournament applications from a single screen.

A single workflow keeps admins, coaches, parents and students coordinated. Invitations, approvals and payments stay out of scattered messages and spreadsheets.

W.02 · Game-performance diagnostics · Windows desktop

ZykeMark

Telemetry becomes a diagnosis.

A Windows desktop tool that records benchmark sessions and reads raw telemetry back as a clear performance diagnosis.

A WPF application with a CLI orchestrates capture; FPS behaviour, frame-time stability and stutter events feed a CPU-bound / GPU-bound call.

ZykeMark benchmark overview showing average FPS, 1% low, P99 frame time, stability and confidence
100%
E.01Benchmark overview

The overview brings average FPS, 1% low, frame time and stability into one summary.

ZykeMark frame-time analysis showing 50 ms and 100 ms thresholds and counted stutter events
100%
E.02Frame-time analysis

The chart separates pacing from headline FPS and counts stutter events against visible thresholds.

ZykeMark bottleneck diagnosis comparing CPU-bound and GPU-bound scenarios
100%
E.03Bottleneck diagnosis

The paired scenarios show how the diagnostic layer distinguishes CPU-bound and GPU-bound behavior.

Measurement to diagnosis

A compact map of how benchmark capture moves from telemetry to diagnosis.

  1. Capture

    A WPF application and its CLI record a benchmark session on a Windows desktop.

  2. Telemetry

    The session keeps average FPS, 1% low, P99 and frame-time telemetry.

  3. Analysis

    Frame-time stability and stutter events past the 50 ms and 100 ms thresholds are surfaced.

  4. Diagnosis

    The session reads back as a CPU-bound or GPU-bound call.

The system turns raw telemetry into a clear CPU-bound or GPU-bound diagnosis. The result shows which side of the machine is holding frame performance.

W.03 · Visa-preparation workspace · Two roles

Vialo

Feedback becomes a next action.

An expert-guided workspace where applicants and experts prepare one visa file through a checklist, versioned documents, review and readiness.

The workspace connects document versions, review states and next actions in one traceable preparation file.

Concept visuals with illustrative data. The real screens are kept private.

Vialo concept visual: a visa file on desktop showing the next step, the document checklist and an expert note, with the same file on a phone. The data is illustrative.
100%
E.01Applicant file · Desktop and mobileConcept visual

The dashboard leads with the next step. Active files, open corrections and published reports follow.

Vialo correction request concept visual: the expert's reason, the affected document version, one clear action and the version history. The data is illustrative.
100%
E.02Correction request · Applicant viewConcept visual

Expert feedback becomes a visible next action with a severity, a reason and the affected document version.

An open correction becomes a clear next action, and the same file moves toward a ready state. This remains a preparation view rather than an official visa decision.

From your problem to a working system.

More case material is available on request.

Discuss a project