RunSync

A Simple Running Tracker Designed for Consistent, Connected Runs

Role: Product Designer & Developer Project Type: Personal Product / Fitness Application Platform: Web & Mobile-focused Experience

Overview

RunSync is a personal running tracker designed to make it easier for runners to record, review, and understand their running activities.

The idea came from a simple need: tracking a run should feel effortless.

Instead of making runners deal with complicated screens or unnecessary information while exercising, RunSync focuses on the essentials—starting a run, tracking progress, viewing the route, and reviewing previous activities.

The product was designed around a mobile-first running experience while also providing a larger dashboard for reviewing running history. The Problem

Many running applications provide a large number of features, but this can also make the experience feel complicated.

For a runner who simply wants to:

Start a run quickly See their current progress Track their route Know how far they have run Finish and save the activity Review previous runs

the experience should be straightforward.

I wanted to create something with a simple and focused running workflow, where the user can concentrate on the activity instead of managing the application.

The Goal

The main goal of RunSync was to create a running experience that is:

Simple Users should be able to start and finish a run with minimal interaction.

Useful The application should provide meaningful information during and after a run.

Connected Running activities should be associated with the user's account so they can review their history across devices.

Mobile-friendly The running experience should work naturally on a phone while the larger dashboard provides a better environment for reviewing records.

Understanding the User Journey

The experience was designed around the natural lifecycle of a run:

1. Start

The runner opens RunSync and starts a new activity.

The interface prioritizes the running experience rather than requiring users to navigate through multiple screens.

2. Run

While running, the user can monitor important information such as:

Running time Distance Current route Activity progress

The interface is intentionally focused so the runner can quickly understand their current status.

3. Finish

When the run is complete, the user ends the activity.

The recorded information becomes part of their running history.

4. Review

After the run, users can return to their dashboard and review previous activities.

This creates a simple feedback loop:

Run → Record → Review → Run Again

Key Features Running Mode

The core experience is a dedicated running mode designed around the activity itself.

Instead of presenting a dashboard full of controls, the experience keeps the most important running information visible and easy to understand.

GPS Route Tracking

RunSync allows the runner's route to be visualized on a map.

This gives users a visual representation of where they ran rather than relying only on numerical statistics.

Distance & Time Tracking

The application records fundamental running metrics so users can understand the duration and distance of each activity.

These metrics also make historical activities easier to compare.

Running History

Completed activities are saved so users can review their previous runs.

This transforms individual runs into a longer-term record of their running activity.

Account-Based Experience

Users can create an account and access their running records through their personal profile.

This provides a foundation for keeping running history synchronized across devices.

Dashboard

The dashboard provides a broader view of the user's running activities.

Instead of focusing on the active run, the dashboard is designed for reviewing past activities and understanding progress over time.

Design Approach Keep the Running Experience Focused

The most important design decision was to avoid making the running screen feel like a traditional dashboard.

When someone is running, they should not need to interact with many controls.

The interface therefore prioritizes the information that matters most during the activity.

Mobile First

Running naturally happens outdoors and on the move, so the mobile experience became a major consideration.

Controls need to be easy to understand and interact with, while information needs to remain readable at a glance.

Separate "Run" From "Review"

Another important decision was separating the active running experience from the historical dashboard.

During a run:

Focus on the activity.

After a run:

Focus on the data.

This distinction keeps both experiences simpler.

Challenges Designing for Movement

A running application is different from a typical productivity application.

Users may be walking, running, moving quickly, or looking at the screen only briefly.

This means information hierarchy becomes especially important.

The interface needs to communicate useful information without requiring prolonged attention.

Balancing Simplicity and Useful Data

It can be tempting to add more statistics and features to a fitness application.

However, adding too much information can make the product harder to use.

The challenge was deciding which information provides genuine value to the runner and which information can remain secondary.

Synchronizing the Running Experience

Another consideration was how a user's running activity should transition from the active session into their historical records.

The experience needs to feel continuous:

Start → Track → Finish → Save → Review

The user should not have to think about what happens behind the scenes.

Product Decisions

One of the biggest product decisions was to avoid trying to build an overly complex fitness platform.

Instead, RunSync focuses on a smaller core experience:

Track your run. See your route. Save your activity. Review your progress.

This creates a product that can potentially grow over time without making the initial experience unnecessarily complicated.

What I Learned

Building RunSync reinforced an important product principle:

More features do not always create a better product.

For activity-based applications, the quality of the core workflow is often more important than the number of available features.

I also learned that designing for real-world situations requires thinking beyond a normal desktop interface.

A runner interacts with the product differently from someone sitting at a desk. The interface needs to account for movement, attention, readability, and quick interactions.

Future Improvements

RunSync could be expanded in several directions while maintaining its simple core experience.

Potential improvements include:

Personal running goals Weekly and monthly progress Pace analysis Running statistics Personal records Activity filtering Route comparison Running streaks Improved activity insights More detailed progress visualization

The key principle would remain the same:

Add useful information without adding unnecessary complexity.

Outcome

RunSync evolved from a simple idea into a focused running experience that combines activity tracking with historical review.

The project demonstrates my ability to think beyond individual screens and consider the complete product journey—from starting an activity to reviewing the result later.

It also gave me an opportunity to explore how a product can be designed around a real-world behavior rather than simply around a collection of features.

Final Takeaway

RunSync is built around one simple idea:

Make tracking a run simple enough that the runner can focus on running.

The project demonstrates my approach to product development: identify a real user problem, simplify the experience, focus on the most important workflow, and create a foundation that can grow without sacrificing usability.