Great article, thank you so much. I'm jumping back into development from a long absence (10+ years) of programming and I'm starting with mobile games. There's a lot I know that I don't know so I was looking for an article like this to answer these questions without even knowing what to ask. Namely, how well it integrates with native android and ios features. Looking over the article, it seems as if a few of the things you mentioned now have libraries or at least documented help (ie push notifications, analytics etc and kinetic scrolling). I tried looking up the features on Unity as well and it seems like Unity does support most if not all of them (or there is community code available), but not sure how well they work. One thing you didn't cover was working on larger projects with others. That's not something I need at the moment, but one day might be a concern.
I am curious, what engine would you guys work with if it wasn't godot? I am really looking to make sure that I spend my time learning an engine that is going to work well for me as I advance my abilities. Thanks again, and I'm looking forward to your answer!
Thanks for your comment. When working with an engine that is meant to work on multiple platforms, you should always keep in mind that it'll never integrate as good as if you'd do it natively.
When it comes to cooperation with other devs, it's really cool that Godot holds everything in diffable text files. This way, we could merge our changes that we did to the same scenes. I'd still recommend to plan tasks on your team to avoid such conflicts, but for Godot it's at least possible. For Unity (at least at the time of writing this article) it would not be possible, as it holds scenes in binary format.
If i had to pick another engine, it would be obviousely dependent on the project's requirements. Defold defold.com/ seems really cool, however I haven't tried it in practice, so I don't know if it delivers what's promissed or only shines on the surface ;) Unity is always a solid choice, however non-open source licensing is a disadventage here, especially if you aim to do a commercial project, working in a team. Also, for single platform projects, that are UI heavy and have simple game mechanics, working on native canvas and building the UI with native controls should be worth to consider.
In your situation, I'd also consider your previous experience in programming and plans for future. GDScript is a totally custom language. If you plan to use it as a hobby, that shoudn't be a problem. If you ever used Python, your learning curve would also be low. However, if you plan to re-learn programming and start looking for a job in the industry, you should think twice if that's a good idea to start with a niche technology.
What's good is that today access to knowledge is sooo easy comparing to 10+ years ago. I hope you'd have a great journey, learning new tech. Figers crossed! 🤞
Cheers!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Great article, thank you so much. I'm jumping back into development from a long absence (10+ years) of programming and I'm starting with mobile games. There's a lot I know that I don't know so I was looking for an article like this to answer these questions without even knowing what to ask. Namely, how well it integrates with native android and ios features. Looking over the article, it seems as if a few of the things you mentioned now have libraries or at least documented help (ie push notifications, analytics etc and kinetic scrolling). I tried looking up the features on Unity as well and it seems like Unity does support most if not all of them (or there is community code available), but not sure how well they work. One thing you didn't cover was working on larger projects with others. That's not something I need at the moment, but one day might be a concern.
I am curious, what engine would you guys work with if it wasn't godot? I am really looking to make sure that I spend my time learning an engine that is going to work well for me as I advance my abilities. Thanks again, and I'm looking forward to your answer!
Thanks for your comment. When working with an engine that is meant to work on multiple platforms, you should always keep in mind that it'll never integrate as good as if you'd do it natively.
When it comes to cooperation with other devs, it's really cool that Godot holds everything in diffable text files. This way, we could merge our changes that we did to the same scenes. I'd still recommend to plan tasks on your team to avoid such conflicts, but for Godot it's at least possible. For Unity (at least at the time of writing this article) it would not be possible, as it holds scenes in binary format.
If i had to pick another engine, it would be obviousely dependent on the project's requirements. Defold defold.com/ seems really cool, however I haven't tried it in practice, so I don't know if it delivers what's promissed or only shines on the surface ;) Unity is always a solid choice, however non-open source licensing is a disadventage here, especially if you aim to do a commercial project, working in a team. Also, for single platform projects, that are UI heavy and have simple game mechanics, working on native canvas and building the UI with native controls should be worth to consider.
In your situation, I'd also consider your previous experience in programming and plans for future. GDScript is a totally custom language. If you plan to use it as a hobby, that shoudn't be a problem. If you ever used Python, your learning curve would also be low. However, if you plan to re-learn programming and start looking for a job in the industry, you should think twice if that's a good idea to start with a niche technology.
What's good is that today access to knowledge is sooo easy comparing to 10+ years ago. I hope you'd have a great journey, learning new tech. Figers crossed! 🤞
Cheers!