App

There are 4 (levels) of users of the Clever Commute app…as defined by these badges

 (1) Tourists – Newbies, probies or anyone whose ability to send messages is limited/restricted
(this is quite rare)

(2) Commuters – these are the vast majority of users.

(3) Rail Warriors – These are trusted, elevated users with a strong history of constructive messages. The three most-significant features of Rail Warriors are:

(i) They have the ability to send messages to multiple communities at a time.
E.g., “All LIRR Riders”…”All NJT Midtown Direct Riders”…”All NJ Bus Riders”

(ii) Their messages bypass the app’s “duplicate checker” routine.
Even if our screening technology flags one of their messages as a possible duplicate of another one already sent, we give the Rail Warrior’s message the benefit of the doubt by letting it through.

(iii) They are not held to the same limits on the length of their messages

(4) Admin – That’s me: Conductor Josh. My messages have a light blue background.

Others:
This designates someone who (regardless of the badges above) is Premium user.

This designates an automated message (bot / robot, Twitter, etc.)

New Functionality

• Add the Commuter Forecast to the app

Usability

• Remove “Update” button from Profile page (use 1-step edit)
• Do NOT apply any filters to values captured via the Hashtag field (allow adult language 🙂 )
• Default the values for Continent and Country at Sign-up and Profile
• Let users know that their nickname may be publicly viewable
• Nicknames must now be at least 6 characters
• Crispen/Clarify the layout of Track Prediction page
• Expand time window for MyTrains

Bug Fixes

• Recent Alerts – Improved rendering of route name
• Allow e-mail address which contains hyphen
• Switch to the proper keyboard so users can easily use “@” key where needed

Departureboard
• Fix – switching between carriers
• Fix – formatting for small screens
• New Feature – added click-through
• Add auto-refresh (based on page_refresh_interval)

Other

• Improved map rendering from Origin station

Infrastructure

• Improve error handling when web/API fails to return data
• Back-end changes for data quality for UGC