Log My Run App is a full stack web application designed to simplify the tracking of runs.
JavaScript HTML CSS
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.


Log My Run App - Prime Academy Solo Project

Getting Started (if you want to play with this code on your own system):

  1. Download code.
  2. NPM install to download all of the dependencies.
  3. As of 5/5/2017 the app is hooked up to my personal MLab account. If you want to play with it, the DB setup is in server/modules/db.js
  4. 'Grunt' makes sure everything is copied right.
  5. NPM start runs it.
  6. Or, if you want to see this code in action without all the work, you can find it at: https://murmuring-wave-78849.herokuapp.com

Application Overview

Log My Run is a full-stack web application that provides a simple, user-friendly, way for users to track their runs and document their daily runs. This app is different from similar apps because it has fewer features, which reduces the learning curve and increases the chances of the app getting continued use.


Over the years I have used different ways to record my runs, including pen and paper, and the disaster known as excel. I also wanted something that was NOT feature rich (too much bloat), and was easy to use on my phone.


Log My Run App is my solution. It's simple, easy to use, and looks great (in my biased opinion), on mobile. What it sacrifices in features (you mean I can't map out my whole run?!), it makes up for in simplicity and usability.


  • While completing this estimate the following assumptions were made.
  • Facebook will allow a user to post from an app (for the stretch goals)
  • The https://openweathermap.org/api API will continue to operate (stretch)


  • Node
  • Express
  • AngularJS
  • MongoDB
  • Mongoose
  • HTML
  • CSS
  • Angular material
  • moment.js


  • Version 1.0

Application features

  1. Log in Screen
  • “Local” login
    • User will either login with their credentials, or they will go to a register screen where they will choose a unique user-name and a password.
  1. Home Page
  • User is then taken to the homepage after logging in.

  • On the homepage the user can select the date. When the date is selected, it will show the runs for that week (Sunday-Saturday). Below the runs it will show a (running) total of the week, month and year. If the user picked a date in the past, the week totals will change to reflect that week.

  • The second page after login shows the information of the run if the user clicks on that day. The user can edit or delete that run.

  1. Enter your run / Edit Your Run
  • When the user clicks the button to add a run, they are taken to the log run screen.

  • On the screen there is a:

    • dropdown to choose the date
    • dropdown items to select the distance
    • dropdown menus for time, allowing the user to select hours, minutes, and seconds
    • a place for the user to enter notes on the run.
  • Stretch goals for this view include:

    • A way to pull in the weather from a weather API and edit it.
    • An option to post their run on facebook.


  • Application will fully support browsers listed below. All browsers or versions not listed below are considered out of scope.

    • Android - 6.0
    • IOS - 10.0
    • Safari - 10.1
    • Chrome - Version 57.0.2987.133


  • MVP - Create a new run with text inputs for the run, time and date and connect it from the DB to the front end.

    • Set up file structure, grunt, package.json, readme
    • Spin up server
    • Connect server to mongo DB
    • Create POST route to DB that inputs distance, time, and date.
    • set up input fields on front end
    • Create GET route to DB that gets all of the runs
    • Display runs to DOM
  • User Login and register new user

    • Set up backend routes
    • put together routes in utility
    • Put together login view for homepage
    • Connect login view to JS files
    • connect JS files to Server Side
    • set up register view
    • connect register to JS
    • connect JS to Server side
    • Set up session to work with current material.
    • debug and make sure user authentication works.
    • Delete and Update Statements.
    • Dropdown menus, calendar, and notes for inputting a run
      • Way to select date
      • Dropdown menu to select distances
      • dropdown menu for time
      • Add notes functionality
  • Homepage that displays the information from the Database and shows the weekly, monthly, and yearly summary

    • Make sure flow is set up correctly, and that all the views are set up with ways to navigate
    • create function to take home from enter run page on click of submit
    • Figure out how to access the date in Angular
    • Logic to figure out weekly totals
    • Logic to figure out monthly summary
    • Logic to figure out yearly summary
  • View of all the week’s runs on homepage with the ability to select a different week from a calendar

  • View/Edit/Delete run view with all of the dropdown and select date features of the add run screen

    • Create views
    • Populate form with options from previous run on edit screen
    • Put and Delete functions in the DB
  • Style CSS

    • Set up login failed alerts
    • implement angular material
  • Week 2 left to Do

    • View of all the week’s runs on homepage
    • select a different week from a calendar
    • Style the APP
    • weekly, monthly, and yearly summary

Future Features

  • Set up different looks for desktop and mobile (stretch)
  • Post status to facebook (stretch)
  • Weather API to display the weather (stretch) (possible api: https://openweathermap.org/api)
  • Adding the ability to show different data and graphs(stretch)


  • Kevin Dahlberg


  • Prime Digital Academy
  • Scott Bromander
  • Chris Black
  • My fellow Chi cohort-mates