Castle Game Engine announced on November 2, 2026 that projects built with Delphi can now target Android and iOS through the engine. For a maker already using Delphi or Object Pascal, the new route means a Castle project can be compiled and run as a FireMonkey mobile app. The engine already supported those platforms with Free Pascal Compiler (FPC); this announcement is specifically about Delphi support, not the first time Castle games could reach phones.
How does Castle Game Engine work with Delphi on mobile?
The engine's manual says to open a Castle example or project in a supported Delphi version, add an Android 64-bit or iOS Device 64-bit target, and build it using Delphi's normal FireMonkey deployment setup. Castle can render as a whole application through TCastleWindow or inside a FireMonkey form through TCastleControl. In either case, the result is a FireMonkey app that uses Castle's rendering and game APIs.
Android development needs the relevant SDK configured in Delphi. For an iOS device build, the manual says a working macOS connection is required. The announcement says Android can be supported as far back as Delphi 10.4.0 with Patch 1, while recommending 10.4.2. A developer should check the detailed version and platform requirements before planning a release around an older toolchain.
Which phone features work, and what is still limited?
Castle says multi-touch, rendering, asynchronous downloads and audio are available. Through FireMonkey components, a game can also use the camera, location, accelerometer and gyroscope; the project provides examples. The documentation cautions that its current Delphi mobile audio backend is suitable for simpler 2D needs but lacks full 3D spatial audio. That limitation matters for games where sound position is part of play.
The engine's own Android and iOS service modules, which include features such as purchases and notifications for FPC projects, are not available through the new Delphi route. Delphi developers need the corresponding FireMonkey functionality instead. This distinction can affect the work needed to ship a game, even if the core scene renders correctly. The team also notes that regenerating project files after changing assets may require adding mobile targets again.
What does this change for a game maker?
The update gives Delphi users a documented path to try Castle Game Engine on phones without changing languages or abandoning the FireMonkey ecosystem. It does not remove platform-specific testing, store requirements or the need to check how controls and layout feel on an actual device. A desktop game may compile for mobile but still need work on touch input, performance and presentation.
This is one more route from an independent game project to an audience carrying phones. VIBPS is a social network for software where makers can show a game they own and connect it to their creator profile; it did not build or test this engine update. The capability and limits here are from the Castle team's announcement and manual.