Response to Kristan

Kristan (July 7, 2011)

The app is not always accurate as of lately. Im using the same phone (Evo) and when I go to cta's website their information is accurate.

For Krist Sake - Now this is what I'm talking about!

Completely fair, concise, and well articulated feedback! Thank you!

I almost don't know how to give you serious answer, but I'll try!

OK, so I've heard from people that sometimes the data in the app is behind the data on the website by 1 or 2 minutes.

This is a known problem and I just put up a FAQ about it.

Basically, for whatever reason, sometimes the data I get for the app is slow by a minute or two compared to the CTA website.

I believe it is an issue with the data I get, although it could certainly be something I'm doing wrong. Either way, I need more details from users about when it happens.

What would be most helpful is data like what route, direction, and stop the predictions were off for, the predicted times both at the website and in the app, and the time of the occurrence.

With this information I can go back to the CTA and try to work with them to determine the root cause of the problem.

In the meantime, there is a "Prediction Offset" setting you can set to up to 3 minutes to account for these discrepancies.

However, if "it's not accurate" means the app is off by 2 hours and not 2 minutes, that's a much bigger problem!

In that case, please shoot me an email to discuss!

Hope that helps!

My Rating:

Comments are not always accurate as of lately. Im getting used to strange comments but when I go to this comment it is completely reasonable.