Skip to content
GOGodswill
All projects
In development

Run Buddy App

A Flutter application that connects two people who want to run together — anywhere in the world.

  • Flutter
  • Dart
  • Mobile UI
  • Auth
  • State Management

The Problem & Product Solution

The Problem

Running with someone is a different activity from running alone — but finding a partner at your pace, in your area and on your schedule rarely happens by accident.

General social apps connect people in the abstract; none of them are built around the simple outcome of two people actually going for a run together.

The Product Solution

Run Buddy is built around one outcome: two people connect and run together, wherever they are in the world.

A runner creates an account, discovers other runners and reaches out to connect — the app handles the introduction so the run can happen.

My Role & Ownership

Mobile development: navigation architecture, authentication flows, runner discovery and the connection flow.

How It's Engineered

FrameworkLayer 01

Built with Flutter and Dart — a single codebase rendering a native-feeling mobile UI, with widgets composed into reusable screen and component layers.

Navigation & routingLayer 02

A route structure with protected guards: account-only screens are unreachable when no session exists, so introductions always happen between two real accounts.

Authentication stateLayer 03

Session persistence keeps runners signed in across app restarts, with a single source of truth for auth state driving the UI.

State managementLayer 04

Discovery results, connection status and form input live in one managed layer, so screens rebuild predictably instead of passing data down through the widget tree by hand.

Engineering Challenges & Solutions

Challenge 01

Two people who have never met need enough context to feel comfortable starting a run together.

Engineered Solution

Profiles and the connection flow do the introducing — the app keeps that first step structured, short and consistent, so the decision to connect is easy to make.

Challenge 02

Discovery has to work across cities and countries without turning into an endless directory to scroll.

Engineered Solution

Discovery is shaped around finding one person to run with: focused lists, clear actions and a direct path from a profile to a connection request.

Shipped Features

Implemented and working in the codebase today.

  • Sign up and sign in with authentication persistence
  • Runner profiles with the person front and centre
  • Discover other runners and reach out to connect
  • Connection flow between two runners — next door or on the other side of the world
  • Protected screens that require a signed-in account
  • Structured navigation across the app
  • Responsive interface across phone sizes

Interface, Responsiveness & Performance

Interface Design

The interface is built for one-handed use on the move: large tap targets, simple cards and very few steps between opening the app and reaching another runner.

Screens stay deliberately quiet — the connection between two people is the event, so layout and spacing do the work instead of decoration.

Discovery reads like a short list of people rather than an endless directory: the goal is one good match, not infinite browsing.

Responsive Behaviour

Built for phones first: layouts adapt across small and large devices, and every interactive target is sized for touch.

Screen structure stays consistent across device densities, so the app looks intentional rather than stretched.

Performance & Accessibility

Widgets are kept lean and lists are built to avoid unnecessary rebuilds while scrolling.

Assets and routes are organised so the app starts fast and navigates without stutter.

Outcome & Takeaways

The app is in active development, with the core journey — account handling, discovery and connecting with other runners — built first.

It is the mobile half of my product work: where Molearn and PocketGuard prove the web side, Run Buddy proves the Flutter side.

  • A connection product is only as good as its first introduction — the path up to connecting has to feel safe, short and obvious.
  • Mobile forces discipline: hierarchy and touch targets have to be decided early, especially for an app people use outdoors on the move.
  • Centralising auth state removes a whole class of routing bugs in apps with protected screens.