OOX Limited

Luka Pikula

Senior Unity Developer, Co-Founder
PIKULA

A developer at core and a builder by mindset, Luka is a key part of our game development team, combining deep technical expertise with strong product ownership. As a co-founder, he bridges engineering and strategy, turning ideas into shipped features and prototypes into scalable systems.

Focused on clean architecture, practical solutions, and fast validation, Luka plays a critical role in building reliable systems across mobile game development and app development projects.

SKILLS

  • System Architecture
  • Mobile Game Development
  • Backend & Game Logic
  • Performance Optimization
  • Scalable Systems Design

PROGRAMS

  • Unity
  • Unreal Engine
  • Git
  • Firebase
  • REST APIs

Luka Pikula

Senior Unity Developer, Co-Founder

A developer at core and a builder by mindset, Luka is a key part of our game development team, combining deep technical expertise with strong product ownership. As a co-founder, he bridges engineering and strategy, turning ideas into shipped features and prototypes into scalable systems.

Focused on clean architecture, practical solutions, and fast validation, Luka plays a critical role in building reliable systems across mobile game development and app development projects.

Q&A

A strong desire to create and to understand how things work under the hood. I was never satisfied with just using software, I wanted to understand the logic behind it. Programming felt like the perfect balance between creativity and structure. You build something from nothing, but through logic and precision.
The first time I worked on a paid project. Until then, programming was something I enjoyed, but it still felt like a hobby. Once I saw that my skills could create real value, and that someone was willing to invest in that value, it shifted my perspective completely.
Drinking good coffee, traveling when possible, and going out with friends. I like switching off completely from work when I can.
“There is nothing more permanent than a temporary solution.” My own quote.
Graduating. Releasing our first commercial game. Starting my master’s studies in game development. Each milestone marked a step forward in turning long-term goals into tangible results.
I focused on programming from high school through my bachelor’s and now master’s studies at the Faculty of Technical Sciences in Novi Sad. I’ve always known what I wanted to do, so my education was structured around building depth rather than exploring different directions. That consistency helped me develop discipline and a structured approach to problem-solving.
Idle Hooligans: Club Fights was my first large-scale production project. It taught me how to write production-ready code, collaborate within a team, and work under real-world constraints. Academic projects are controlled environments; production teaches you about trade-offs, deadlines, and maintainability.
In fast prototyping phases, speed is important, but readability still matters. Even quick solutions need to be understandable by the rest of the team. We rely on peer reviews and internal standards to maintain consistency. Scalability comes from modular systems and avoiding unnecessary complexity early on.
I start with functional testing to confirm expected behavior. After that, I involve testers or external feedback. In mobile game development, UX validation is just as important as technical correctness. A feature can work perfectly from a technical standpoint but still feel wrong to the player.
I follow industry-focused YouTube channels, LinkedIn discussions, and Reddit communities. Recently, I’ve been especially interested in AI tools and workflow optimization within game development processes.
A simple typo in a bundle ID that took two days to track down. It was a small mistake with a disproportionately large impact. That experience reinforced how critical attention to detail is in production environments.
Clear communication and early alignment are essential. I aim to understand the intent behind design and art decisions before implementation to reduce rework. Transparent discussion about technical constraints helps teams make better decisions and keeps development efficient.
Learning how to use AI tools effectively. They won’t replace developers, but they already improve productivity and automate repetitive tasks. Developers who understand how to leverage AI will simply work smarter.