Fitness apps have become much more than digital workout logs. Users increasingly expect technology to understand their workouts, reduce manual effort, and make exercise feel more interactive.
One interesting way to do this is to use the smartphone camera as part of the workout experience.
A good example is Motus, a fitness app built around camera-based body tracking, structured workouts, automatic rep counting, and social motivation. Motus Case Study — LoudOwls
The Problem: Tracking Every Rep Manually
Traditional workout apps often rely on users to enter information themselves.
Choose an exercise.
Complete the reps.
Record the number.
Move to the next set.
It works, but it interrupts the workout.
A camera-based approach creates an opportunity to make this process more automatic. Instead of constantly interacting with the phone, the user can focus on exercising while the app observes movement and handles parts of the tracking experience.
Turning the Camera Into a Workout Tool
The interesting part of Motus is its use of the iPhone camera for body tracking.
The camera can be used to understand body movement during an exercise. That movement can then become useful workout data, including automatically counting repetitions.
This changes the role of the smartphone.
It isn't simply displaying the workout anymore. It becomes part of the workout itself.
Automatic Rep Counting
Rep counting sounds simple until it needs to work reliably while someone is actually exercising.
A useful system needs to distinguish between movement and a completed repetition rather than simply detecting that the body has moved.
For the user, however, the experience should remain simple.
They shouldn't need to think about the underlying tracking technology. They should be able to start an exercise and concentrate on their form and movement while the app handles the counting.
That separation between technical complexity and user simplicity is one of the biggest lessons from building camera-based experiences.
Structured Workouts Matter
Automatic tracking is only one part of the experience.
A fitness app also needs to guide the user through the workout itself.
Motus uses structured workouts with exercises, sets, repetitions, and rest periods. This creates a more guided experience than simply displaying a list of exercises.
The technology becomes more useful when it supports the complete workout flow rather than functioning as an isolated feature.
Designing for Real-World Use
A feature can work perfectly in a controlled environment and still feel frustrating in the real world.
Fitness apps have an additional challenge: users are moving, changing positions, and often don't have their hands available to interact with the phone.
That means the experience needs to minimize unnecessary interaction.
The camera-based functionality should work in the background of the workout experience rather than constantly asking the user to tap buttons or enter information.
Adding a Social Layer
Fitness isn't only about numbers.
Motivation can also come from seeing what other people are doing and sharing progress.
Motus combines its workout experience with social features such as a feed, stories, kudos, and pokes.
This creates another interesting product lesson: technology can track the workout, while social interaction can help make users want to keep coming back.
Technology Behind the Experience
Motus was built natively for iOS using Swift and SwiftUI, with GuruSDK used for camera-based body tracking and Supabase supporting areas such as accounts and social data. Motus Case Study — LoudOwls
Choosing technology isn't only about what can be built. It is also about what can deliver the required experience reliably.
For camera-based applications, developers need to think about tracking accuracy, device capabilities, performance, interaction design, and what happens when real-world conditions aren't ideal.
The Bigger Lesson
Building a camera-based fitness app isn't simply a computer-vision challenge.
It is a product-design challenge.
The technology has to disappear into the experience.
Users shouldn't have to think about body tracking, movement detection, or rep-counting logic. They should simply feel that the app understands what they're doing and makes their workout easier.
That's perhaps the biggest lesson from Motus: the best technology isn't always the technology users notice. It's the technology that quietly removes friction from their experience.
For developers exploring computer vision in mobile apps, fitness is just one possible application. The same principles can extend to other experiences where understanding movement can make an app more useful, interactive, and intelligent.
Top comments (0)