WorkoutCloud

A premium fitness app from a local gym in Hanover, Germany.

Background

Physicalpark in Hanover, Germany, is a premium gym with lots of amenities for their clients. They focus on providing medical physiotherapy and numerous courses for various audiences.

For the past few years, I've been collaborating with them on the mission to build a dope fitness app named WorkoutCloud. The client had filmed hundreds of exercise videos ready before I walked in, and we started to assemble a catalog for all the content, garnishing it with some terrific features.

Challenge

Physicalpark wanted to provide something extraordinary to its members: A full-blown native fitness app for iOS and Android as another way to present their exhaustive know-how of medical fitness and improve their customers' workout experience. The design has been provided all the way along.

Another critical requirement was to provide their in-house trainers with a simple and content management system for the partially convoluted and extensive data. Crucial here are the workouts, which consist of a sequence of specific workout components (e.g., cardio units, tabata units, and notably more), which in turn consist of multiple exercises.

As the project had advanced, new challenges arose from the ground. E.g., at one point, we solely focused on building a white-labeled off-spring of the app with a custom exercise catalog for another business partner (Wilkhahn). On another occasion, we replaced an essential part of our tech stack and created another off-spring to work as an approachable info point inside the fitness center.

Solution

Because Physicalpark wanted to serve both platforms (iOS and Android), they suggested using a hybrid framework, Ionic at the time. This idea would save resources finance-wise and speed up the development process.

I created the full technical foundation for the project, utilizing the convention-driven approach of Ruby on Rails to speed up the bootstrapping. Then I turned it into a custom administration panel, as well as into the serving REST API.

As time passed, we switched to React Native and GraphQL to increase the quality of the software and unblock significant bottlenecks.

Benefits

By now, the whole project has unfolded into a reasonably large tree of subprojects, which are still maintainable and extendable even with limited resources. Such efficiency is made possible only through modern tooling and layered architecture.

Physicalpark is now able to provide its customers with a broad range of digital or digitally enhanced services and products, while still maintaining its primary role as a fitness center. In a just slightly different universe, it easily could have transitioned to a software-first company.