Working together on a project

Godot, Tauri and Flutter. PREDEV scoping, architecture, delivery in batches.

What fits best: a project that needs a production framework. Playable prototype, mobile MVP, loop redesign, architecture, or a scope reset before execution.

What gets delivered

Applications, desktop and mobile

Tauri v2 and Rust for desktop, Flutter for mobile. Offline-first, data kept on the user's machine, continuous integration. From scoping to release.

Verso: desktop tarot software published on itch.io, two editions. Tauri v2, Rust, React, SQLite. Offline readings, no account, plain-text journal on disk.

Godot games, GDScript

Game design, loops, economy, prototyping. Desktop and browser.

Games in GDScript, including Sillon, playable on itch.io. Balancing by deterministic headless simulation, pixel art asset pipeline.

Architecture and product scoping

PREDEV/POSTDEV method, batch breakdown, technical documentation, audit.

The same sequence on every project. No batch delivered without tests and an audit.

Types of engagement

What decides an engagement is not only the stack: it is where the project stands, how much structure it needs, and the level expected of the deliverable.

What fits

A prototype or vertical slice to scope quickly
A mobile MVP or a game that needs architecture and prioritisation
An existing project that needs a product or systems audit before moving on

Less suited

A feature factory, with no scoping and no access to product decisions
AAA production with highly specialised roles
Pure execution work, where method and tests do not count

Engagement formats

Audit and reset

To clarify a scope, a game loop, an architecture or a roadmap before restarting production.

Typical output: prioritised action plan, risk points, next batches.

Prototype or vertical slice

To validate a loop, prototype a system or make an idea presentable to testers, partners or investors.

Typical output: playable build, scope decision, next steps.

MVP, from scoping to delivery

To go from a PREDEV scoping to a deliverable product: architecture, batch breakdown, tests, clean delivery.

Typical output: an MVP that is tested, documented, ready to iterate.

Playable demo in 72 h

In 72 hours, a playable prototype with a game loop that runs. Not a design document: a build.

Playable Godot build, Windows and Android
Full source code
Short design document: scope, decisions, next steps

The method

PREDEV scoping before code. Batches with acceptance criteria. Audit after delivery. On Verso, continuous integration rejects any lint warning and runs the Rust and front-end tests on every batch.

Proof

Desktop software

Get in touch