One Week Into Game Development: Why I Chose Unity and What I Finished So Far
Over one focused week, I compared Unreal, Unity, and GameMaker, explored publishing paths, and committed to Unity after building momentum through the Essentials pathway.
This week I finally stopped saying I wanted to learn game development and actually did it. I tested engines, looked at publishing channels, and tried to map effort to real opportunities like the Reddit Devvit daily game hackathon and the Swift Student Challenge.
The short version is simple: I chose Unity. It felt more universal, lighter to iterate in, and easier to move forward with quickly. Unreal is powerful but felt heavier for where I am right now, and GameMaker never clicked for me.
Key leadership takeaways
- Momentum matters more than picking the most powerful engine on day one.
- Publishing options should influence engine choice early, not at the end.
- Structured learning paths make experimentation measurable and motivating.
How I approached the week
I treated the week like a practical sprint instead of an open-ended rabbit hole. Explore engines, test publishing paths, and choose one stack to commit to.
I looked at Unreal, Unity, and GameMaker, then mapped each to where I could actually ship: Apple App Store, Reddit, and Unity Play. I also tested a separate Next.js text-based game concept for the Devvit daily game hackathon to explore faster web-native iteration.
Why Unity won for me
Unity felt like the best middle ground between capability and speed. It seemed broadly accepted across the places I might publish, and it did not feel as heavy as Unreal for early experimentation.
I wanted to spend this phase learning game design and systems, not fighting complexity too early. Unity gave me enough depth to grow into while still letting me build quickly right now.
- Unreal: impressive power, but heavier than I wanted for week-one momentum.
- Unity: practical, widely used, and easy to keep shipping in.
- GameMaker: useful for some creators, but not a fit for my workflow.
A long runway finally became useful
For the past three years, I collected free asset giveaways because I knew I would eventually go deep on game development. This week was the first time that library stopped being future prep and became active fuel.
Having assets ready removed friction. Instead of getting blocked on art every hour, I could focus on learning tools, testing mechanics, and finishing milestones.
What I built before the certification track
After choosing Unity, I completed a 3D tutorial project and had a blast. That project gave me exactly what I needed: confidence that I enjoy this enough to stay consistent.
From there I started the Unity Essentials Learning Pathway, which is split into Editor Essentials, 3D Essentials, Programming Essentials, 2D Essentials, and Publishing Essentials.
Completed so far in Unity Essentials
So far I have finished the Editor Essentials, 3D Essentials, and Audio Essentials portions listed below, for a total of 560 XP.
- Editor Essentials (130 XP): Install Unity, open the project, explore the interface, master 3D navigation, pass the Scene view flying test, design a mural, complete the quiz.
- 3D Essentials (110 XP): Build a kid bedroom scene, create a bouncy ball, stack prefab blocks, tune lighting/camera/background, complete the quiz.
- Audio Essentials (320 XP): Build an immersive kitchen soundscape, complete the extension activities, and pass the quiz.
What this week clarified
- I learn fastest when I alternate exploration with commitment.
- A clear publishing target improves technical decisions upstream.
- Small wins compound quickly when progress is visible and tracked.
- The right engine for now is the one I will keep opening every day.
What comes next
Next I will continue through Programming Essentials, 2D Essentials, and Publishing Essentials. I also plan to keep pressure-testing ideas through short prototypes tied to real submission paths.
This week was less about perfection and more about choosing a lane. That decision is made, and now the work is to keep shipping.
If you are also learning game development, I would love to compare notes on engine choice, publishing paths, and staying consistent.