Skip to content

Work / Founder experience

HapticRun: building an eyes-free running coach for Apple Watch

A native iOS and watchOS app that guides runners through a heart-rate training zone with distinct haptic signals, so they never need to look at the screen.

Selected prior experience of KRATT founder Martin Kambla

HapticRun was independent product development through Funktsioon OÜ. It is presented here as prior engineering experience of KRATT’s founder, Martin Kambla. It is not KRATT client work.

The challenge

Most fitness applications rely on visual information to communicate training performance. For runners trying to maintain a specific heart-rate zone, this means repeatedly checking their watch, interpreting the data and adjusting their pace.

HapticRun started with a simple question:

Could a smartwatch guide a runner through an entire workout using touch instead of visual notifications?

The concept was straightforward, but implementing it on wearable hardware introduced several engineering challenges: collecting physiological data during exercise, responding to changing measurements, delivering meaningful haptic feedback and working within the background execution constraints of watchOS.

The approach

Real-time heart-rate monitoring

HapticRun was designed around continuous heart-rate guidance using Apple Watch sensors and HealthKit.

Rather than treating heart rate as a passive measurement, the application uses it as an input to a feedback system, allowing runners to define their preferred training zone and receive guidance when they move outside it.

An important design consideration was the variability of sensor readings. Heart-rate measurements can fluctuate, arrive at irregular intervals or momentarily become unreliable.

The application’s architecture therefore needed to account for signal stability, response thresholds and notification frequency to avoid distracting users with unnecessary feedback.

An interface built around haptics

The central design principle was to communicate useful information without requiring the runner to look at the screen.

The interaction model uses distinct haptic signals for different conditions:

  • Above the target heart-rate zone: a short vibration indicating that the runner should reduce intensity.
  • Below the target zone: a different vibration pattern indicating that intensity can increase.
  • Within the target zone: no interruption is necessary.

This creates a minimal interaction model where the runner can focus on the activity rather than the device.

Input

Apple Watch heart-rate sensor

Physiological measurements through HealthKit

Processing

Heart-rate processing

Signal filteringThreshold evaluationAlert control

Below zone

Increase intensity

In zone

No interruption

Above zone

Reduce intensity

Output

Eyes-free haptic guidance

Feedback delivered through the wrist

HapticRun conceptual processing flow. Conceptual design, not a verified representation of the current implementation.

Engineering within watchOS constraints

Wearable development introduces constraints that are less prominent in conventional mobile applications.

HapticRun required consideration of background execution, workout session management, sensor availability, power consumption and the reliability of haptic notifications while the watch display is inactive.

The project also involved native iOS and watchOS application development, device testing and preparation for distribution through Apple’s TestFlight environment.

Workout ecosystem integration

The product architecture was designed around Apple’s HealthKit workout infrastructure, with the intention of recording workouts and allowing users to access their activity through their existing fitness ecosystem.

Integration with third-party services such as Strava was considered as an extension of this model.

The outcome

HapticRun progressed from an initial product concept and technical specification into iOS and Apple Watch beta builds distributed through TestFlight.

The project demonstrates the practical challenges involved in developing software that must respond to real-world sensor input while operating within the resource and interaction constraints of wearable devices.

It also illustrates how a narrow user problem can be translated into a focused product concept, technical architecture and working application prototype.

Capabilities demonstrated

  • Native iOS and watchOS application development
  • Apple HealthKit and wearable sensor integration
  • Real-time data processing and event-driven application design
  • Haptic interaction and accessibility-oriented UX
  • Background execution and device resource constraints
  • Product prototyping, testing and beta distribution

Building for sensors, wearables or devices?

Describe the hardware, the data it produces and what the user needs to know without looking at a screen.

Discuss a project