40 Almighty Ramses 2

How to play 40 Almighty Ramses 2

“Just being a content studio is great, but if you can bolt engagement products onto your offering, you’re going to stand out from the crowd.”

For Splash Tech founder Adam Wilson, RubyPlay’s acquisition of his company is not simply the coming together of two complementary suppliers. It is an early indication of where the wider supplier market may be heading.

The deal adds Splash Tech’s free-to-play games and supplier-agnostic jackpot engine to RubyPlay’s existing portfolio of free spins, rewards, missions and tournaments. In doing so, it strengthens RubyPlay’s evolution from a content-led provider into a broader content and engagement tools company, giving operators a way to add engagement mechanics across existing and third-party portfolios without building those capabilities from scratch.

How to play 40 Almighty Ramses 2

“I always found it funny when Colombia was starting, operators were saying ‘players here do not like slots’, as if they have a different DNA. Five years later, they would say, ‘well, they do like slots, but simple slots’. And five years later, they were playing all the usual [slots]. It’s not that they didn’t like slots.

“If someone takes the time to understand what they’re used to playing, what they like, what their history is and take that into consideration, then you can bridge that gap. If operators take that time to understand where players are at, it does make a difference.”

Local operators, meanwhile, have tried to close the gap by strengthening their technology, including working with world-class suppliers.

About 40 Almighty Ramses 2

“I would not necessarily prioritise senior Java or front-end specialists in the same way as before,” Grenstad explains. “Technical skills remain important, particularly for people who can assess architecture and ensure systems remain reliable, but domain knowledge is becoming increasingly valuable. I’d rather take someone who’s good in the domain but doesn’t know any Java.”

That raises a question about how future developers will enter the industry. If Cubeia no longer needs front-end traditional junior Java developers in the same way, the traditional path from junior programmer to senior engineer becomes less clear.

“How do we avoid ending up with lots of old Java developers and nobody who understands Java because the juniors were never hired? That’s a super-interesting question. How do we fill up with younger people over time? That’s something we’ve been discussing.”