Work

Projects

Enterprise software, delivery, mobile products and games. Each significant project has a case study: context, role, decisions and outcome.

Mobile Product

CresciBimbo

Offline-first Android app for tracking a newborn's growth, sleep, feeding and medical visits.

Result: Published on Google Play, designed and released end to end by me.

Tech: Flutter · Dart · Riverpod

Role: I own the product end to end: definition, UX, architecture, development, QA, Play Store policy compliance and release configuration.
Problem: New parents log dozens of small events a day across notes, chats and memory. The information exists, but it is scattered, hard to read over time and hard to share at a check-up.
Key decisions: Flutter UI with Riverpod for predictable, testable state.
Isar as the local NoSQL store — no network needed to log an event.
Firebase Authentication for account access.

Enterprise Software · Delivery

Public-sector delivery where I was both senior Java developer and team leader.

Result: Nine-month engagement (03–11/2023): requirements, progress and risks shared with the client.

Tech: Java · Spring · REST API

Role: Senior Developer / Team Leader. Responsible for governance, milestones, stakeholder alignment and requirements gathering, while developing Java / Spring backend services.
Problem: A public-sector programme with firm deadlines, several client stakeholders and a mixed dev and QA team. The risk was not only technical: requirements, priorities and progress had to stay visible and agreed.
Key decisions: Java / Spring backend services and REST APIs.
Requirements → backlog → sprint planning → review loop.
Progress monitoring and deadline tracking shared with the client.

Enterprise Software

Enterprise IT portal for Fastweb on Java / Spring Boot microservices and Apache Kafka.

Result: Features planned and delivered inside Fastweb's enterprise release process (2021–2023).

Tech: Java · Spring Boot · Apache Kafka

Role: Java developer on assignment: planning and development of microservices within the client's teams and processes.
Problem: An enterprise telecom environment: many integrated systems, event-driven flows and structured release processes. New features had to ship without destabilising services already in use.
Key decisions: Java / Spring Boot microservices.
Apache Kafka for asynchronous, event-driven communication.
Enterprise release process with planned deployment windows.

Browser Game · Technical case study

Real-time strategy on a living 3D planet, playable in the browser.

Result: Playable now: free, no ads, no installation.

Tech: Three.js · WebGL · JavaScript

Role: Concept, game design and direction: the rules, the balance and the look. The code was written with AI assistance and verified with automated play-throughs.
Problem: Make a planet feel alive and stay readable as a strategy map: smooth orbit and zoom, thousands of objects on a sphere, and destruction that has consequences — using nothing but Three.js.
Key decisions: Deformable cube-sphere terrain with an exact height lookup, so units, roads and projectiles follow craters.
Instanced rendering: 15,000 trees, about a thousand buildings with procedural night windows, hundreds of cars, airliners and ships.
Hand-written HDR pipeline: MSAA scene buffer, bloom, tone mapping, depth of field, sun shadows, cloud shadows baked from a cube map, four quality presets with automatic downgrade.

Mobile Game · Technical case study

3D checkers for Android in Unity 6, with adaptive AI and fully offline play.

Result: Published on Google Play: free, no ads, no pay-to-win.

Tech: Unity 6 · C# · URP

Role: Producer and developer: roadmap, backlog, development, QA, publication and maintenance on Play Console.
Problem: A 3D board game has to feel smooth on mid-range Android phones, play fully offline and offer an opponent that is challenging without being unfair.
Key decisions: Component-based gameplay architecture in C#.
Dynamic board generation and piece management.
Adaptive AI opponent and local multiplayer.

Android App