Currently developing a game with Android SDK, should I switch to a game engine in future projects?

| | August 4, 2015

I am an android developer, and I’ve made several apps on the Google Play Store. I’m currently working on my first game, which is just a simple RPG for android, that I’m coding in java with the android SDK. I went to an indie game conference recently, and one of the veterans, asked why I didn’t use Unity or another game engine to build my game, so it could be easily ported later on. Which got me to wonder if I should use a game engine, since I do want to port this game to other platforms.
So, my question is, should I try to adapt to a game engine to make my future projects, if so, which game engines should I look into?

2 Responses to “Currently developing a game with Android SDK, should I switch to a game engine in future projects?”

  1. As you mention that your current game is simple I assume you are learning, or at least expanding upon other non-game related knowledge. Game engines are useful tools in industry, the games you make will work more efficiently and turn around time will be faster.

    My opinion is that it is far better to create your own engine if not working on a commercial project (time/profit isnt an issue). As you will learn lots of things you would miss over otherwise in terms of how game engines work and how to structure a library and how to program for efficiency. These things are all possible to learn while on other projects but are integral with game engines.

    As you have already worked on an engine in your first game. How much have you learned from that process? and how would you change it if you start again.

    for commercial work use a published/professional engine,
    for personal projects work on your own as you will get allot more out of it.

    also building an engine specifically for your game, means you wont have excess code/variables taking up space in your program, and can be more efficient and do exactly what you want.

  2. YES. If we put cross-platform aside, I think you should use a game engine just for the basic features that many game engines provide:

    • Object/Layer management + Level loading
    • A Renderer for either 2D or 3D
    • Texture management (texture groups, texture sizing, texture-atlasing)
    • Physics
    • Animation engine (support opacity, rotation, position, etc.. with different easing curves)
    • Particle system (efficiently render many particles acting according to meta data)
    • Easy to use editors (level, animations, particle effects)

    Now some game engines also offer cross-platform deployments to mobile phones and desktops, some examples are Unity, Cocos2d-x and Unreal Engine. So if you are ok with the licensing terms then it’s a no-brainer question whether to use one.

    P.S: I can’t help you with a recommendation for a specific one because I do my own game engine development.

Leave a Reply