Before Building the Product, We Had to Prove It Could Work

ArmCare initially considered using Knack, a no-code platform, to build its application.

But the challenge was not simply creating screens, forms, or dashboards. The product depended on a specialized hardware integration whose technical feasibility had not yet been established.

Rather than commit immediately to a full application, Soluntech recommended starting with technical validation.

The initial work focused on proofs of concept, understanding the device's API, extracting its data, and translating the results into meaningful measurements.

This approach addressed the project's most consequential uncertainty before substantial investment in the surrounding software.

The objective was not to build as much as possible. It was to prove that the essential capability could work.

As the concept evolved, ArmCare transitioned to a smaller, lighter, and more portable dynamometer.

That change improved the physical experience of using the device, but it also introduced an important architectural consideration.

The new hardware offered an SDK designed for iOS and Android applications. Integrating with the device therefore required a mobile approach rather than relying exclusively on a web-based platform.

Soluntech adapted the development strategy accordingly.

An iOS application came first, followed later by Android. A web platform remained part of the product ecosystem, providing coaches with a more accessible way to review measurements, visualize information, and work with their athletes.

The architecture followed the realities of the hardware and the needs of its users, rather than forcing the product into a technology choice made earlier.

The first meaningful product milestone was straightforward: capture the measurements from the device and make them understandable.

That capability created the foundation for everything that followed.

Instead of attempting to deliver a fully featured sports performance platform from the beginning, ArmCare and Soluntech expanded the product incrementally.

As ArmCare developed its market presence and identified new customer needs, the software evolved alongside the business.

Soluntech assembled and coordinated a multidisciplinary team that included iOS and Android developers, frontend and backend engineers, UX/UI designers, QA specialists, and project management.

This allowed ArmCare to expand the product without having to independently assemble and coordinate every technical discipline required.

Over the years, ArmCare's product evolved well beyond its initial hardware integration.

The mobile applications became part of a broader system supporting athletes and coaches. The web-based Coach Portal continued to improve, with enhanced data visualization, player statistics, and capabilities for managing training programs.

Additional integrations, including payment systems, supported the commercial evolution of the platform.

Each new capability built on the technical foundation established during the earlier stages.

The relationship between ArmCare and Soluntech also evolved. What began as technical validation became an ongoing technology partnership supporting product development and continuous improvement.

ArmCare led the product vision, customer relationships, and market development. Soluntech provided the engineering capabilities and execution structure needed to support that evolution.

Today, ArmCare operates a commercial sports performance platform with mobile applications, hardware integrations, coaching capabilities, and training programs.

According to figures published by ArmCare, its technology has reached more than 100,000 athletes, alongside adoption across training facilities, schools, and collegiate programs.

Those figures reflect ArmCare's broader commercial success, rather than outcomes attributable solely to Soluntech.

For Soluntech, the most meaningful result is the continuity of the partnership and the progression from a technically uncertain concept to an established product that continues to evolve.

The initial integration challenges did not dictate the limits of the business. They became problems that could be investigated, validated, and resolved through a sequence of informed technical decisions.