Android: Native: 2.1.1, JS: 2.2.1
iOS: Native: 2.1.0, JS: 2.2.1
No changes have been made to the app in the last 2 weeks.
Driver and Observer App Re-design:
A re-design of the driver and observer app appearance is in progress.
Website Updates - New UI/UX:
The Journey screen can now be accessed via a trip schedule calendar, 2 hours in advance of scheduled trip start.
Journey Screen Map:
There is a map shown at the top of the journey screen, with a time slider that allows you to track a vehicles location and events received from a driver device. Stops are initially shown in black with passing points shown in green. Once a stop has been visited and geo-fence triggered, the stop will turn blue with the next expected stop highlighted in pink. Any stops that were skipped in advance of journey start are highlighted in grey and any stops that were skipped during a journey, as the driver has used the I'm here feature in the app, are shown in red.
If you click on a waypoint marker this will open a modal showing the stop name and expected arrival time.
If you hover over the time slider this shows the time of event received, relating to the position of the slider.
The map can be zoomed to full screen if required. There is a traffic layer that can be added to see high congestion areas and you can change the appearance to light, dark or satellite view.
Journey Screen Passenger Status:
There is a table below the map showing passenger status for the journey. In advance of journey start this shows the name of all passengers scheduled on the trip. Passenger names are shown in alphabetical order with the table defaulting to 10 rows in view. You can increase the number of rows shown or search for passenger name, token, boarded time or disembarked time. You can also filter the table by boarded stop or disembarked to stop to only see events relating to the stop selected.
When a passenger boards or disembarks the vehicle the table will populate the name of the routepoint and the exact time of boarding or disembarking. If a token was used then the token number will be shown in the Token column. If the passenger was manually boarded or disembarked by the driver you will see that this was a manual board or disembark. This will be colour coded to show if the routepoint was that scheduled:
- Green: Expected Stop
- Amber: The passenger boarded or disembarked at an unexpected stop
- Red: The passenger wasn't scheduled on the journey
- No highlight: An expected passenger didn't board or disembark the vehicle
There is a column picker where columns can be removed from the view if required. The table can also be exported as a PDF file or csv file. Any export will contain the columns/rows in view, based on any search or filter criteria selected.
Journey Screen All Events:
At the bottom of the screen an all events table is shown. This contains all events received from a vehicle device. If a journey is in progress, new events will populate the table as they are received from the device. The events are sorted to show most recent event at the top of the table. The table defaults to 10 rows in view and you can increase this is required.
There is a column picker where columns can be added or removed from the view if required, for example speed, lat/lng, heading, received time, battery %. There is also a category column that can be added to view any actions; notifications sent or automatic alarms raised.
You can search by event time or token or filter the view to display individual or multiple event types or routepoints.
The table can also be exported as a PDF file or csv file. Any export will contain the columns/rows in view, based on any search or filter criteria selected.
If you click on a row in the table you will move to the top of the screen where the time slider and target location will reflect the event selected.