Felgo vs jMonkeyEngine

Felgo is a native cross-platform SDK based on Qt for building applications, games and embedded software. Developers mainly use QML and JavaScript, with C++ also supported. Felgo Live updates QML and JavaScript on connected devices after a save, without waiting for build and deployment steps. The Game Engine focuses on 2D casual games and includes Box2D physics, particles, multi-touch and animations. Felgo Apps can use device features such as cameras, sensors and file systems, alongside networking options including WebSockets, Bluetooth LE and NFC. Browser-based Cloud Builds can build and deploy projects from Felgo Cloud IDE. Game Network offers achievements, leaderboards, challenges, cloud storage and offline support. Listed targets include Android, iOS, Windows, macOS, Linux and web. Personal has an annual turnover limit under €50k. Startup costs €79 a month, billed annually per developer, and has a turnover limit under €100k. Business costs €245 a month, billed annually, and has no annual turnover limit. Felgo offers a free plan and a free trial.

jMonkeyEngine is a free, open-source Java game engine for developers. It targets Windows, macOS, Linux, Android, and iOS, with mobile export and multiplayer foundations. Rendering includes a GLES 3.0 backend and direct OpenGL support from versions 3.2 through 4.5. Java 11 through Java 21, Gradle builds, JVM tooling, and direct Java-library use are listed. Networking foundations cover TCP, UDP, RPC, and synchronization patterns. Physics options include rigid-body, soft-body, and vehicle simulation through Bullet, Box2D, or Jolt Physics integration. Graphics features include PBR, custom materials and shaders, bloom, FXAA, SSAO, and tone mapping. A glTF workflow is described for moving Blender materials, lighting choices, and scene setup. The BSD 3-Clause License includes no runtime fees, royalties, splash-screen requirement, or requirement to mention the engine. Setup uses an initializer, NetBeans-based SDK, or direct Java-library configuration. SDK integrations are maintained separately and may lag engine features.