People helping people as they get from here to there


Another Dog Days Example

August 20th, 2017  |  Published in examples

Here is a fairly typical example of how Clever Commute provides information that is faster and better than the actual transit providers.

This is a picture of the Recent Alerts feed in the app.

This happned on the morning of 18-Aug 2017
(click image to enlarge)


Regarding on-time performance. Let’s just say…

August 14th, 2017  |  Published in examples

A big Thank You to everyone who has been pitching in on our fledgling metrics project.

It’s generating a ton of data…and we are actively organizing and analyzing it. Click to enlarge the report below which shows summarized info for some NJT AM trains.

Oh…and that last colum?
Red values mean that the month-to-date average actual arrival time is later than the scheduled arrival time.

Let’s just say that NJT’s claims of on-time performance are subject to some interpretation.

Thanks again…and look for a proper report in the Fall.
The folks who were consistent sharers will indeed get a copy.


Dog Days Example

August 7th, 2017  |  Published in examples

Here is a fairly typical example of how Clever Commute provides information that is faster and better than the actual transit providers.

This is a picture of the Recent Alerts feed in the app.

The train in question is the 6:29 PM train from Hoboken on 7-Aug 2017
(click image to enlarge)

TOP: From Clever Commute’s feed of actual NJT alerts.
(yes, we offer these in the app,
for free, during Summer Of Hell. Other times.
Other times, it’s Premium feature)Note:
Timestamp is 6:51 PM
NJT says the train is up to 10 min late

BOTTOM: A commuter, already shared the news.

Timestamp is At 6:41 PM
user Bcretella shared the news that it was “T+12”
…and we were still in the station.

(I say “we” because I was on that train…
and I was pleased to see Clever Commuters pitching in!)

Some NJT Metrics on Day 1 of Summer of Hell

July 10th, 2017  |  Published in examples

Clever Commute is much more than a place to share Twitter-style messages.

This page shows examples of how we use technology to harvest actual train arrival and departure information.

Learn more at this link: 

There are two tables below for the “Day 1” commute on NJ Transit

  1. Morning (to NYC / Hoboken)
  2. Evening (from NYC / Hoboken)
NOTE: This is actual data from today…published as a service to the commuting community.
The process of collecting and rendering this data is new.
The depth and breadth of the content will improve…as will the approach to presenting it

Here is the morning view. Scroll down to see the evening view 

LineTrainScheduled ArrivalReported ArrivalPlus or Minus
Gladstone Branch4148:42 AM8:46:13 AM+ 4 m 13 s
Main/Bergen County Line11527:40 AM7:45:56 AM+ 5 m 56 s
Main/Bergen County Line11548:14 AM8:15:57 AM+ 1 m 57 s
Main/Bergen County Line12027:23 AM7:30:41 AM+ 7 m 41 s
Northeast Corridor31248:18 AM8:17:52 AM- 0 m 8 s
Northeast Corridor31268:36 AM8:30:15 AM- 5 m 45 s
North Jersey Coast Line32228:24 AM8:26:17 AM+ 2 m 17 s
North Jersey Coast Line33127:14 AM7:18:51 AM+ 4 m 51 s
Northeast Corridor37108:22 AM8:22:30 AM+ 0 m 30 s
Northeast Corridor37189:44 AM9:38:38 AM- 5 m 22 s
Northeast Corridor39329:40 AM9:42:40 AM+ 2 m 40 s
Montclair-Boonton Line62046:46 AM6:46:58 AM+ 0 m 58 s
Montclair-Boonton Line62067:40 AM7:42:02 AM+ 2 m 02 s
Montclair-Boonton Line62148:59 AM8:59:13 AM+ 0 m 13 s
Montclair-Boonton Line62169:50 AM9:54:50 AM+ 4 m 50 s
Morris & Essex Line66107:10 AM7:13:41 AM+ 3 m 41 s

Here is the evening view.

LineTrainScheduled DepartureReported DeparturePlus or Minus
Main/Bergen County Line11736:36 PM6:37:36 PM+ 1 m 36 s
North Jersey Coast Line32695:34 PM5:36:13 PM+ 2 m 13 s
Northeast Corridor39555:43 PM5:46:37 PM+ 3 m 37 s
Northeast Corridor39637:03 PM7:15:08 PM+ 12 m 08 s
Montclair-Boonton Line62634:52 PM4:51:34 PM- 0 m 26 s
Montclair-Boonton Line62796:10 PM6:12:02 PM+ 2 m 02 s




What’s new in version 2.4.5

July 4th, 2017  |  Published in examples


  • Click-through on a message to see Hashtag, Speed and Station
  • Metrics: Published list of NJT NYP trains to consider avoiding
  • Metrics: New functionality to capture and report on train on-time performance
  • New routes: ParkNRides for NJT
  • New routes: LIRR Buses for SummerOfHell

Bug Fixes and Technical Updates

  • LIRR MyTrains now shows proper list of pre-5:00 PM trains
  • Upgraded processing for datafeeds such as PABT
  • Refined Google Analytics implementation

What’s new in Clever Commute version 2.4.4

May 22nd, 2017  |  Published in examples


New Features

  • Allow users to share metrics about their train
  • New “Resources” Menu (Schedules, Transit Police, Customer Service, Best Practices, KOTW, Clever Blog)
  • Use emoji for alert categories (on pick list and Recent Alerts)
  • Add (1) station and (2) scheduled-arrival-at-station-time to Recent Alerts

We say “no” to duplicate messages

May 14th, 2017  |  Published in examples

[Coming in version 2.4.1]

We all want good commuter data…and we love it when the commuters pitch in and share it.

However, nobody wants to notified multiple times about the same issue.

When people press the Send button, our algorithm does a real-time check to see if the message appears to be a dupe.  If our technology determines a likelihood, the user sees this:



The sender has 3 choices 

  1. Send the message “as is”
  2. Edit the message
    (and then send it)
  3. Cancel the message






Tags: ,

Premium User – you are in control

May 5th, 2017  |  Published in examples

Clever Commute Premium has dozens of amazing features.
This page explains one or more of them...

We’re doing our best to keep the data volumes manageable…and will be enhancing our duplicate-checker soon.
A future version of the app will allow you to limit your alerts by
  • message category
  • duration of the underlying issue


Tags: ,

“How To” Homepage

March 5th, 2017  |  Published in examples

This is a write up of how to use one of the many features of the Clever Commute service. See also:



Tags: ,

What’s new in Version 2.3.7

February 21st, 2017  |  Published in examples

Improved End-user Experience

  • Added contextual train details to Recent Alerts
  • Added train details to push notifications
  • Removed train details from click-through
  • Improved CSS / look-and-feel for Recent Alerts
  • Added App Help menu option

New Premium Features

  • Holiday reminders / Advice
  • Added train details to Premium e-mails
  • Improved rendering of train location and origin when viewing on a map

Bug Fixes

  • Reset iOS badge when the alert expires
  • Train picklist on certain devices
  • Fixed link to FAQ
  • Nickname length error message (and confusion with zip code)
  • Added “None Selected” option for “Your Train”