Alternatives to libGDX logo

Alternatives to libGDX

MonoGame, Android Studio, Cocos2D-X, Godot, and JavaFX are the most popular alternatives and competitors to libGDX.
45
60
+ 1
3

What is libGDX and what are its top alternatives?

The framework provides an environment for rapid prototyping and fast iterations. Instead of deploying to Android/iOS/Javascript after each code change, you can run and debug your game on the desktop, natively. Desktop JVM features like code hotswapping reduce your iteration times considerably.
libGDX is a tool in the Game Development category of a tech stack.
libGDX is an open source tool with 22.8K GitHub stars and 6.4K GitHub forks. Here’s a link to libGDX's open source repository on GitHub

Top Alternatives to libGDX

  • MonoGame
    MonoGame

    It is a free C# framework used by game developers to make games for multiple platforms and other systems. It is also used to make Windows and Windows Phone games run on other systems. ...

  • Android Studio
    Android Studio

    Android Studio is a new Android development environment based on IntelliJ IDEA. It provides new features and improvements over Eclipse ADT and will be the official Android IDE once it's ready. ...

  • Cocos2D-X
    Cocos2D-X

    Cocos2d-x is an open-source and cross-platform open source free 2D game engine for mobile game development known for its speed, stability, and ease of use ...

  • Godot
    Godot

    It is an advanced, feature-packed, multi-platform 2D and 3D open source game engine. It is developed by hundreds of contributors from all around the world. ...

  • JavaFX
    JavaFX

    It is a set of graphics and media packages that enables developers to design, create, test, debug, and deploy rich client applications that operate consistently across diverse platforms. ...

  • pygame
    pygame

    It is a cross-platform set of Python modules designed for writing video games. It includes computer graphics and sound libraries designed to be used with the Python programming language. ...

  • JavaScript
    JavaScript

    JavaScript is most known as the scripting language for Web pages, but used in many non-browser environments as well such as node.js or Apache CouchDB. It is a prototype-based, multi-paradigm scripting language that is dynamic,and supports object-oriented, imperative, and functional programming styles. ...

  • Git
    Git

    Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. ...

libGDX alternatives & related posts

MonoGame logo

MonoGame

32
51
1
A free C# framework used by game developers
32
51
+ 1
1
PROS OF MONOGAME
  • 1
    Cross-platform
CONS OF MONOGAME
  • 1
    Can't working in vs mac 2019
  • 1
    No GUI

related MonoGame posts

Android Studio logo

Android Studio

24.9K
19.8K
361
Android development environment based on IntelliJ IDEA
24.9K
19.8K
+ 1
361
PROS OF ANDROID STUDIO
  • 176
    Android studio is a great tool, getting better and bet
  • 103
    Google's official android ide
  • 37
    Intelligent code editor with lots of auto-completion
  • 25
    Its powerful and robust
  • 5
    Easy creating android app
  • 3
    Amazing Layout Designer
  • 3
    Great Code Tips
  • 3
    Great tool & very helpful
  • 2
    Easy to use
  • 2
    Built in Emulator
  • 2
    Keyboard Shortcuts are Amazing Out of the box
CONS OF ANDROID STUDIO
  • 4
    Slow emulator
  • 4
    Huge memory usage
  • 2
    Using Intellij IDEA, while Intellij IDEA have too
  • 2
    Complex for begginers
  • 2
    No checking incompatibilities
  • 1
    Lags behind IntelliJ IDEA
  • 1
    Slow release process

related Android Studio posts

Gustavo Muñoz
Senior Software Engineer at JOOR · | 8 upvotes · 443.7K views

In my modest opinion, Flutter is the future of mobile development. The framework is as important to mobile as React is to the web. And seeing that React Native does not finish taking off, I am focusing all my efforts on learning Flutter and Dart. The ecosystem is amazing. The community is crazy about Flutter. There are enough resources to learn and enjoy the framework, and the tools developed to work with it are amazing. Android Studio or Visual Studio Code has incredible plugins and Dart is a pretty straight forward and easy-to-learn language, even more, if you came from JavaScript. I admit it. I'm in love with Flutter. When you are not a designer, having a framework focused on design an pretty things is a must. And counting with tools like #flare for animations makes everything easier. It is so amazing that I wish I had a big mobile project right now at work just to use Flutter.

See more
Julien DeFrance
Principal Software Engineer at Tophatter · | 8 upvotes · 442.4K views

As a Engineering Manager & Director at SmartZip, I had a mix of front-end, back-end, #mobile engineers reporting to me.

Sprints after sprints, I noticed some inefficiencies on the MobileDev side. People working multiple sprints in a row on their Xcode / Objective-C codebase while some others were working on Android Studio. After which, QA & Product ensured both applications were in sync, on a UI/UX standpoint, creating addional work, which also happened to be extremely costly.

Our resources being so limited, my role was to stop this bleeding and keep my team productive and their time, valuable.

After some analysis, discussions, proof of concepts... etc. We decided to move to a single codebase using React Native so our velocity would increase.

After some initial investment, our initial assumptions were confirmed and we indeed started to ship features a lot faster than ever before. Also, our engineers found a way to perform this upgrade incrementally, so the initial platform-specific codebase wouldn't have to entirely be rewritten at once but only gradually and at will.

Feedback around React Native was very positive. And I doubt - for the kind of application we had - no one would want to go back to two or more code bases. Our application was still as Native as it gets. And no feature or device capability was compromised.

See more
Cocos2D-X logo

Cocos2D-X

63
84
0
Open source game engine
63
84
+ 1
0
PROS OF COCOS2D-X
    Be the first to leave a pro
    CONS OF COCOS2D-X
    • 2
      Popular only in Asia
    • 2
      Based on Chinese
    • 1
      No Multiple Languages
    • 1
      Not Popular in itch.io and in Steam
    • 1
      Very poor system
    • 1
      No GUI
    • 1
      Bad Windows Performance

    related Cocos2D-X posts

    Godot logo

    Godot

    206
    257
    39
    Free and open source 2D and 3D game engine
    206
    257
    + 1
    39
    PROS OF GODOT
    • 11
      Open source
    • 6
      Easy to port
    • 5
      Supports both C++, C# and GDScript
    • 5
      Cross-Platform
    • 5
      Simple
    • 4
      Avaible on Steam For Free
    • 3
      GDScript is Based On Python
    CONS OF GODOT
    • 1
      Harder to learn
    • 1
      Performance in 3D
    • 1
      Need opengl 2.1 / 3.3
    • 1
      Somewhat poor 3D performance and lacks automatic LODs

    related Godot posts

    JavaFX logo

    JavaFX

    281
    415
    10
    A Java library for building Rich Internet Applications
    281
    415
    + 1
    10
    PROS OF JAVAFX
    • 10
      Light
    CONS OF JAVAFX
    • 1
      Community support less than qt
    • 1
      Complicated

    related JavaFX posts

    Farrukh Waheed
    Configuration Management Engineer · | 4 upvotes · 11.8K views
    Shared insights
    on
    JavaFXJavaFXSwingvySwingvy

    Hi experts, I need to write a GUI app that would configure a .json file. I am considering it to be cross-platform with as much as less dependency as possible i.e. once build/compiled, it should be running on the maximum number of OS platforms without re-building or re-compiling. So up till now, I've shortlisted 3 selected frameworks. The Swingvy was to be Java Swing but was not in the list. And after reading some stuff, I think that Java Swing or JavaFX should do the job. But I need suggestions/opinions from you experts, which would be a great help in order to achieve a precise decision. Any help/suggestion would be really appreciated. Thanks a bunch

    See more
    Shared insights
    on
    JavaFXJavaFXElectronElectron

    I create desktop applications that use a database for storing data. My applications are used as management tools in supermarkets, stores, warehouses, and other places. I don't know which one to use; Electron or JavaFX. Can anyone advise me on this matter?

    See more
    pygame logo

    pygame

    110
    170
    5
    Open Source python programming language library for making multimedia applications
    110
    170
    + 1
    5
    PROS OF PYGAME
    • 3
      Easy to install
    • 1
      Simple
    • 1
      Lightweigt by only being 12 mb
    CONS OF PYGAME
    • 2
      Has only 2d
    • 1
      Slow

    related pygame posts

    JavaScript logo

    JavaScript

    350.9K
    267.2K
    8.1K
    Lightweight, interpreted, object-oriented language with first-class functions
    350.9K
    267.2K
    + 1
    8.1K
    PROS OF JAVASCRIPT
    • 1.7K
      Can be used on frontend/backend
    • 1.5K
      It's everywhere
    • 1.2K
      Lots of great frameworks
    • 896
      Fast
    • 745
      Light weight
    • 425
      Flexible
    • 392
      You can't get a device today that doesn't run js
    • 286
      Non-blocking i/o
    • 236
      Ubiquitousness
    • 191
      Expressive
    • 55
      Extended functionality to web pages
    • 49
      Relatively easy language
    • 46
      Executed on the client side
    • 30
      Relatively fast to the end user
    • 25
      Pure Javascript
    • 21
      Functional programming
    • 15
      Async
    • 13
      Full-stack
    • 12
      Setup is easy
    • 12
      Its everywhere
    • 12
      Future Language of The Web
    • 11
      JavaScript is the New PHP
    • 11
      Because I love functions
    • 10
      Like it or not, JS is part of the web standard
    • 9
      Expansive community
    • 9
      Everyone use it
    • 9
      Can be used in backend, frontend and DB
    • 9
      Easy
    • 8
      Easy to hire developers
    • 8
      No need to use PHP
    • 8
      For the good parts
    • 8
      Can be used both as frontend and backend as well
    • 8
      Powerful
    • 8
      Most Popular Language in the World
    • 7
      Popularized Class-Less Architecture & Lambdas
    • 7
      It's fun
    • 7
      Nice
    • 7
      Versitile
    • 7
      Hard not to use
    • 7
      Its fun and fast
    • 7
      Agile, packages simple to use
    • 7
      Supports lambdas and closures
    • 7
      Love-hate relationship
    • 7
      Photoshop has 3 JS runtimes built in
    • 7
      Evolution of C
    • 6
      1.6K Can be used on frontend/backend
    • 6
      Client side JS uses the visitors CPU to save Server Res
    • 6
      It let's me use Babel & Typescript
    • 6
      Easy to make something
    • 6
      Can be used on frontend/backend/Mobile/create PRO Ui
    • 5
      Promise relationship
    • 5
      Stockholm Syndrome
    • 5
      Function expressions are useful for callbacks
    • 5
      Scope manipulation
    • 5
      Everywhere
    • 5
      Client processing
    • 5
      Clojurescript
    • 5
      What to add
    • 4
      Because it is so simple and lightweight
    • 4
      Only Programming language on browser
    • 1
      Test2
    • 1
      Easy to learn
    • 1
      Easy to understand
    • 1
      Not the best
    • 1
      Hard to learn
    • 1
      Subskill #4
    • 1
      Test
    • 0
      Hard 彤
    CONS OF JAVASCRIPT
    • 22
      A constant moving target, too much churn
    • 20
      Horribly inconsistent
    • 15
      Javascript is the New PHP
    • 9
      No ability to monitor memory utilitization
    • 8
      Shows Zero output in case of ANY error
    • 7
      Thinks strange results are better than errors
    • 6
      Can be ugly
    • 3
      No GitHub
    • 2
      Slow

    related JavaScript posts

    Zach Holman

    Oof. I have truly hated JavaScript for a long time. Like, for over twenty years now. Like, since the Clinton administration. It's always been a nightmare to deal with all of the aspects of that silly language.

    But wowza, things have changed. Tooling is just way, way better. I'm primarily web-oriented, and using React and Apollo together the past few years really opened my eyes to building rich apps. And I deeply apologize for using the phrase rich apps; I don't think I've ever said such Enterprisey words before.

    But yeah, things are different now. I still love Rails, and still use it for a lot of apps I build. But it's that silly rich apps phrase that's the problem. Users have way more comprehensive expectations than they did even five years ago, and the JS community does a good job at building tools and tech that tackle the problems of making heavy, complicated UI and frontend work.

    Obviously there's a lot of things happening here, so just saying "JavaScript isn't terrible" might encompass a huge amount of libraries and frameworks. But if you're like me, yeah, give things another shot- I'm somehow not hating on JavaScript anymore and... gulp... I kinda love it.

    See more
    Conor Myhrvold
    Tech Brand Mgr, Office of CTO at Uber · | 44 upvotes · 10.1M views

    How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:

    Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.

    Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:

    https://eng.uber.com/distributed-tracing/

    (GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)

    Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark

    See more
    Git logo

    Git

    289.8K
    174.2K
    6.6K
    Fast, scalable, distributed revision control system
    289.8K
    174.2K
    + 1
    6.6K
    PROS OF GIT
    • 1.4K
      Distributed version control system
    • 1.1K
      Efficient branching and merging
    • 959
      Fast
    • 845
      Open source
    • 726
      Better than svn
    • 368
      Great command-line application
    • 306
      Simple
    • 291
      Free
    • 232
      Easy to use
    • 222
      Does not require server
    • 27
      Distributed
    • 22
      Small & Fast
    • 18
      Feature based workflow
    • 15
      Staging Area
    • 13
      Most wide-spread VSC
    • 11
      Role-based codelines
    • 11
      Disposable Experimentation
    • 7
      Frictionless Context Switching
    • 6
      Data Assurance
    • 5
      Efficient
    • 4
      Just awesome
    • 3
      Github integration
    • 3
      Easy branching and merging
    • 2
      Compatible
    • 2
      Flexible
    • 2
      Possible to lose history and commits
    • 1
      Rebase supported natively; reflog; access to plumbing
    • 1
      Light
    • 1
      Team Integration
    • 1
      Fast, scalable, distributed revision control system
    • 1
      Easy
    • 1
      Flexible, easy, Safe, and fast
    • 1
      CLI is great, but the GUI tools are awesome
    • 1
      It's what you do
    • 0
      Phinx
    CONS OF GIT
    • 16
      Hard to learn
    • 11
      Inconsistent command line interface
    • 9
      Easy to lose uncommitted work
    • 7
      Worst documentation ever possibly made
    • 5
      Awful merge handling
    • 3
      Unexistent preventive security flows
    • 3
      Rebase hell
    • 2
      When --force is disabled, cannot rebase
    • 2
      Ironically even die-hard supporters screw up badly
    • 1
      Doesn't scale for big data

    related Git posts

    Simon Reymann
    Senior Fullstack Developer at QUANTUSflow Software GmbH · | 30 upvotes · 9.2M views

    Our whole DevOps stack consists of the following tools:

    • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
    • Respectively Git as revision control system
    • SourceTree as Git GUI
    • Visual Studio Code as IDE
    • CircleCI for continuous integration (automatize development process)
    • Prettier / TSLint / ESLint as code linter
    • SonarQube as quality gate
    • Docker as container management (incl. Docker Compose for multi-container application management)
    • VirtualBox for operating system simulation tests
    • Kubernetes as cluster management for docker containers
    • Heroku for deploying in test environments
    • nginx as web server (preferably used as facade server in production environment)
    • SSLMate (using OpenSSL) for certificate management
    • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
    • PostgreSQL as preferred database system
    • Redis as preferred in-memory database/store (great for caching)

    The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

    • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
    • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
    • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
    • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
    • Scalability: All-in-one framework for distributed systems.
    • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
    See more
    Tymoteusz Paul
    Devops guy at X20X Development LTD · | 23 upvotes · 8.3M views

    Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).

    It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up or vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.

    I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.

    We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.

    If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.

    The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).

    Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.

    See more