Being a game developer with the skills you have
Download as PPTX, PDF1 like131 views
The document outlines the journey and options available for game developers, including various roles, programming languages, platforms, and game engines such as Unity3D, Monogame, and Phaser. It emphasizes the importance of evaluating personal goals and market trends while also encouraging participation and feedback through the DevSum app. Additionally, it highlights the challenges of game development and the need for flexibility and adaptation in skill sets.
Being a game developer with the skills you have
- 1. Being a game developer with the skills you have Johan Lindfors @johanlindfors johan.lindfors@coderox.se #devsum18
- 2. Don’t forget to evaluate this session in the DevSum app!
- 3. Want the code? git clone git@github.com:programmeramera/DevSum2018 git submodule update --init --recursive Git, Unity3d, Python, CMake, OpenGL, DirectXTK, C++/WinRT, MonoGame, Defold, LUA, Phaser, JavaScript/TypeScript Contribute?
- 4. Who are you? • Framework developer? • Client developer? • Backend developer? • Full Stack developer? • Web developer? • UX developer/designer? • Database developer?
- 5. Where do you want to end up? • Get hired • Consulting • Startup/entreprenour • Hobby
- 6. Depth Where do you want to end up? • Get hired • Consulting • Startup/entreprenour • Hobby
- 7. Breadth Where do you want to end up? • Get hired • Consulting • Startup/entreprenour • Hobby
- 8. Who can you be - depth? • Game engine developer • Game developer • Backend developer • Full stack developer • Web developer • Technical artist • Data engineer
- 9. Who do you need to be - breadth? • Game engine developer • Game developer • Backend developer • Full stack developer • Web developer • Technical artist • Data engineer • Graphics designer • Audio engineer • Marketeer • PR • Operations • CxO • Social media expert
- 10. Why do you want to do it? • Make lots of money • Keep my skills on par • Learn something new • Teach programming
- 11. Choice: Language(s) • C/C++ • C# • Javascript/Typescript • LUA/Python/Ruby • Objective-C/Swift • Java/Kotlin
- 12. Choice: Platform(s) • Web • Desktop • Mobile • Consoles • Wearables • VR/AR/MR
- 13. Supplier(s) • Apple • Google • Microsoft • Sony • Nintendo • Facebook • Amazon • Steam
- 14. Engine • Unity3D • Unreal Engine • CryEngine • Phaser • Monogame • Defold • BYO
- 15. What’s important? • Productivity – time to market • Market potential – make some money • Breadth – reach lots of users on many devices • Exposure – in demand tech skills
- 16. Unity3D • Pros • High in-demand tech skill • Vibrant community • Huge asset store • C#/mono/Visual Studio integration • Cons • Abstraction layering • 3rd party dependency
- 17. P M B E
- 18. MonoGame • Pros • C#/mono • Lots of content • XNA • Cons • 3rd party dependency
- 19. P M B E
- 20. Phaser • Pros • JavaScript/TypeScript • Visual Studio Code • Tons of demos and tutorials • Cons • Web and mobile • Phaser/Phaser-CE
- 21. P M B E
- 22. Build Your Own Engine • Pros • Absolute flexibility and choice • C/C++/C#/Java/Python/Ruby • No engine – no external dependencies • Cons • Time to market • OpenGL/DirectX/Vulkan • Tech stack++
- 23. P M B E
- 25. Some final notes • When you are 90% done, you have 90% left! • There’s so much more than coding and architecture • The market is a beast • You should at least evaluate Unity!
- 26. And…. Last but not least – don’t forget to evaluate this session in the DevSum app!