Tech @ Runtastic

In the backend team we usually try to automate things. Therefore we have tons of tests to verify correctness of our code in our gems and services.

At Runtastic we face an increase in traffic on our servers every year. We usually have a higher number of requests in the spring…

Despite our best intentions, software projects often get delayed. We, the members of the Premium team, try our best to make realistic predictions, yet we often fail.

The Runtastic app for iPhone has an Apple Watch counterpart that offers the same great tracking experience. On iOS, our persistence layer is managed by a library on top of Apple’s Core Data framework.

Imagine any repetitive task you are working on. If you increase the time spent on the task, you would expect a better output — “better” in terms of more quantity or “better” in terms of higher quality.

There are millions of thoughts about the architecture; each solution could lead to hours of discussions.

In this article, we want to share our approach to implementing such scenarios using UIStackView…

In my previous posts about the message bus, I wrote about using RabbitMQ for decoupling our services and how we defined our message content.

Working with databases on iOS can be difficult. Powerful but complex APIs can be a reason for subtle mistakes, slow development, and hard verification of code.

I believe that many of us are missing out on the more advanced features of Git. Are they needed or can we cover our bases without them?

A message can become a dead letter for various reasons. I want to provide more insights into dead letter handling.

In our last post we talked about how Quality Assurance works at Runtastic. This post continues the journey by telling you the “behind the scenes”…

Putting your coding skills to the test in a coding challenge gives you the chance to prove yourself and your expertise. Here’s how it works…

Do you think about the internal implementation of the collection? Do you think about the advantages and/or disadvantages that it comes with? Should you care?

In this post, we will reflect on how the Runtastic QA team is working now, following up on our last post on why we think the transition was important…

This post explains how we make our receivers resilient and fast, and why we choose to do this.

This post gives deeper insight into the actual content of our messages, explaining what we send within a message, what other possibilities we considered…

This post discusses the benefits and challenges of transitioning from Waterfall to Agile methodology, specifically from a Quality Assurance perspective…