Journal

Development diary

What happened, when, and in which version — every post is tied to a real date in the project’s history.

Version 1.0 In the game
describes the game as submitted to the App Store
Version 1.1 Planned
plans for a version in development — nothing here is in the game yet

Dates are the dates of the milestones. The journal opened on 7 October 2026, and every entry so far was posted that day.

Latest

MilestoneVersion 1.0 In the game

VELTRAIL 1.0 submitted to the App Store

The first version is finished and waiting for Apple’s review. It will be released automatically once it is approved.

Read the entry

Earlier entries

  1. Milestone:
    Version 1.1 Planned

    Next: heroes and Endless Flow

    Version 1.1 is in development: eight couriers with one ability each and a solo expedition across the islands. None of it is in the game yet.

  2. Milestone:
    Version 1.0 In the game

    Online matches have a home

    The public game server for VELTRAIL 1.0 went online in Frankfurt and is ready for launch, with name rules, reporting and blocking.

  3. Milestone:
    Version 1.0 In the game

    From tap to menu in about two seconds

    How a cold start on the test phone, an iPhone 17 Pro Max, went from about seven seconds to about two — and what was slowing it down.

  4. Milestone:
    Version 1.0 In the game

    The game meets a real iPhone

    Two days in, a signed build ran on an iPhone for the first time. The next morning the game learned 120 Hz, and on 3 October a stress test held it.

  5. Milestone:
    Version 1.0 In the game

    Why rails at the receiver can’t be cut

    A design decision that came out of bot test runs: a small protected zone around the active receiver.

  6. Milestone:
    Version 1.0 In the game

    The first full 3 vs 3 match

    The morning after the first line of code, a whole match ran from countdown to results — every courier driven by the computer.

  7. Milestone:
    Version 1.0 In the game

    Day one: an idea and a working core

    One document described the game. By the end of the same evening, rails, pulses, sparks and bridges worked in code.

New entries appear when something real happens: a release, an update, a decision.