3 Cases of devtodev Integration (RemiVision, SneakyBox, Stepico)

How fast can you integrate the devtodev analytics platform into your product? Here are three real use cases that will help you understand the time frame and the entire process
3 Cases of devtodev Integration (RemiVision, SneakyBox, Stepico)

Any growing company sooner or later will face the following question: are we going to develop our own in-house analytics system or use an out-of-the-box solution available on the market? In-house analytics undoubtedly works best when it comes to flexibility. This means, however, that you will engage in a multi-year project with an unpredictable outcome.

So, an out-of-the-box solution, given it is flexible enough to answer all your questions, might be the best value for money. devtodev users on average manage to complete integration in one week and can enjoy a variety of useful reports and dashboards right away. Meanwhile, they don't lose in flexibility, since the platform provides access to raw data and SQL editor.

Eduardo Duarte

We’ve asked our clients about the time it took them to integrate devtodev with their projects and here’s what they have to say. 

Michal Wiśniewski, BI Engineer at Remi Vision 

Analytics system integration Wisniewski

Not that easy to say, as we were also doing some cleanup/reorganization in our analytics stack - I guess it took even longer than what I say below. On the other hand, we were recently adding D2D to our new production and there we made it in 50% of what I give below.

1. Creating an account and basic setup (~2-4 h)

I think that's a matter of 1h on the account side. SDK integration may be 2-4 hours per platform, depending if any problems with building/packaging appear.

2. Creating a document with the structure of events (~16 h)

It took us 8 hours to understand basic events well - I include here some testing/consultations. Initially, the devtodev approach seemed a bit strange for us (although now I understand the reasons behind it). For custom events - it is a matter of how many events you have. We were doing some cleanup and reorganization also - so it took us probably 16 hours, but I would normally expect 4-8h hours with testing.

3. Integrating events in the game (~12 h)

I think it can be 8h with basic events and like 4 hours for 20 custom events (but we had all the code for sending them to other analytics systems, it was just about new calls, names, parameters handling, etc.)

Liudas Ubarevičius, CEO at SneakyBox

Liudas Ubarevicius

It usually takes 1-2 days to implement the SDK itself depending on how advanced the project itself is.

Around 4-5 days to implement the event structure you provided us with during the analytical consultations.

But then again event structure really depends on the project itself, so it may really vary.

Volodymyr Pleskaniuk from Stepico

Volodymyr Pleskaniun

All in all, integrating devtodev into a project will take 8-16 hours. You can add a bit of time required for creating a document with an event structure (if you don’t have a ready one).

While making exact time estimations is hard - it highly depends on the complexity of the game, the number of custom events you need, and your team’s experience with integrating SDKs in general - one thing is clear: you can save a lot of time if integrating a ready solution, such as devtodev.

By the way, devtodev analysts helped the Stepico team with developing the event structure for their game. It was done online and took us just 10 hours!

Curious about the flexibility of our platform and which tasks it can solve? Wait no more, schedule a demo call with us.

Read more