The Official RunTrackr Blog

Main menu:



Previous location now saved

Just a quick note, we’ve added a nice little feature that saves your previous location when you create a route, so creating multiple routes in the same location should be a fair bit easier now as the location will default to the last used.

Hope you enjoy the feature, and do let us know if you encounter any problems!

Training Log now showing pace times

We’ve made a minor update to the Training Log feature of RunTrackr.  It now shows the pace times for each of your runs, in minutes:seconds per mile or kilometer, depending on what you’ve set in your profile.  Furthermore, we’ve enhanced the training log so that you can input your distance in either miles or kilometers, again, depending on your preferences.  This is something we obviously should have had since the start and the reason that it only supported kilometers up until this point was more an artifact of our metric upbringing than anything else.

First, select your preferred distance units from below:


The Training log will now happily respect your choice!


You now no longer need to rely on tools to do the conversion and can instead work in your native units of choice.

Training Log Totals

Training isn’t easy. With all the obligations of modern life, it can be hard to find time to exercise. But we find time, whether it’s waking up before the sun rises, sacrificing lunch time or running late at night after work. One thing that can help you keep up the habit is a proper training log, where you can record your progress. By keeping track of your goals and progress, you provide yourself with a powerful incentive to maintain your regimen.

We’ve always provided a training log since day one, which easily allowed you to link your running records directly with your created routes or your favorite routes. However, it’s been a little primitive. In order for it to be more valuable, your training log needs to show cumulative totals, so that’s what we’ve added.

Currently, we show your totals for current week (starting from Sunday), current month and the current year. Eventually, we plan to allow for more detailed statistics, showing total for every previous week/month/year, along with charts and graphs. (Here at RunTrackr, we’re geeks for things like stats)

Persistent Login now working

It happens all too often: You’ll be so preoccupied with so many details that you’ll often overlook something so simple yet so essential. For us, that was persistent login, known to many as the “Remember Me” feature. Well, today we’re happy to report that this has finally been fixed!

Your login will now persist for four weeks instead of an indeterminate amount of time. We’ve debated on exactly how long we should allow login to persist and whether or not to reveal the length on the login page since most people won’t care. Some tweaks are likely.

For now, enjoy not having to enter your password each time – and do let us know if you run into any issues.

Improving search with suggestions

Search is the most important feature. If you can’t find what you’re looking for, it might as well not exist. So today, we’re rolling out a small, but useful feature that allows you to search for routes better: Suggestions.

The Google Maps API we use is very robust and good in finding the location you’ve searched for. However, sometimes it returns multiple matches or suggestions for commonly-used names for locations, like “Whitfield” or “Belleville”. Before, when this happened, you got a somewhat nasty-looking message like this:

This was basically using a JavaScript window.alert and it isn’t very user-friendly. Besides being bad since it interrupts your work flow, the look & feel of the dialog will not be consistent with the UI of your site, since the browser generally determines the appearance of the alert windows. (In particular, Opera presents an alert window that looks very exotic, but all of the browsers have this to some degree) This is why many web applications opt to use their own UI for notification, even when it involves a more complex solution.

To fix that we now display the suggestions directly under the search field if the need arises. Let’s say you search for “Belleville”. Instead of getting that nasty pop-up alert box, you now get something a little more soothing:

Clicking any of the suggestions sets the location to that one. Neat and simple – the way all software should be.

Browse over search

Over here at RunTrackr, we’re firm believers in the power of search. You shouldn’t have to spend an inordinate amount of time manually looking for what you want.

To this end, we made sure that a robust search function was available from day one – though we’re working on improving that as well. (Nothing is perfect or ever will be!)

However, we do realize that some people like to browse, perhaps because they don’t yet know exactly what they’re looking for and just would like some general ideas of running routes, not necessary in a certain area or location.

Thus, we’ve launched a browse section where you can peruse routes at your leisure. This feature is still somewhat in beta, so that’s why it’s not yet “official”. It’s fairly basic, but it allows you to easily run through the available public routes on the site.

Upcoming improvements

The mantra on Google Code’s hosting page is “Release Early, release often”. No where else does this apply more than to web applications; with traditional desktop software, releasing often means you have to have a robust upgrade solution in order to push out releases to your users. With web applications, the virtually the entire package runs on a server that you control, mitigating any such worries. (Though things like Gears help bridge the gap between web and desktop applications)

When we first launched RunTrackr our aim was a basic, yet functional application that would appeal to 90% of our users, who just wanted to create a running route and get basic stats like distance. However, it has never been our intention to stop at this.

Time permitting, we’re planning on the following improvements:

  • Training Log: Weekly/monthly/cumulative totals along with graphs and charts
  • Annotation of routes/maps to point out interesting features
  • A `Browse` section for those who would rather do this than search
  • Performance: Making the map-enabled portions of the site faster

These are just a few things we have on our minds at the moment. As always, don’t hesitate to contact us if you have any comments! (Or post them below!)

Route Privacy options now available

RunTrackr was designed with one underlying principle in mind: To help others accomplish their fitness goals. To this end, we encourage sharing; up until this point, all routes created by all users have been public and viewable by anyone, whether they’ve registered or not.

However we also recognize that many would like to maintain their privacy online. Since one’s own running routes will naturally correlate with one’s geographic location, it is understandable that many will not want to post their routes online for all to see. To fix this, we have implemented Route Privacy options. You will now be able to mark any routes you’ve created as private, meaning only you will be able to view or do anything with them. Here’s a quick overview of the new options.

Marking a route as private

Marking a route as private can be done when creating a new route or editing an existing one. The option is a checkbox clearly marked with a Lock icon.

By default routes are not marked as private (as we encourage sharing) so you will have to check it yourself. After the route has been saved, when viewing it you will be reminded that you are the only one who can see it.

Additionally, when you view the route under “My Routes”, it will be marked as private:

It’s important to know that the best measures for ensuring online privacy is to choose a username that doesn’t match with your real one. (We never reveal your e-mail address) By default, you don’t have to supply any other personal information to RunTrackr, and we intend to keep it that way for the time being. Any other concerns can be addressed by our Privacy Policy.

Thanks, and keep RunTracking!