App Updates:
Android: Native: 3.0.6, JS: 3.0.10
iOS: Native: 3.0.6, JS: 3.0.10
There have been no updates to the app in the past two weeks.
Please note that versions of the mobile app, lower than native 3.0.6, have now been deprecated and app features will no longer work. Please ensure that users update to the latest app version from the relevant app store.
Website Updates:
Visibility of Unexpected Journeys:
Where a passenger boards a journey and they are not booked, to give observers visibility of unexpected journeys, the journey can now be accessed via their Kura app or portal schedule.
If unexpected boarding and disembarking notifications are configured in the Kura website, observers using the Kura app will be notified of unexpected events.
If they receive an unexpected boarding notification and tap on this they will be taken to the schedule screen in their app. If they manually refresh the schedule, using the refresh icon at the top right of the screen, the unexpected journey will be displayed. Please note that it may take a few minutes before the journey is available so a few refreshes may be required.
If the unexpected journey is selected, the journey information and map will be displayed. If a journey is in progress, the map will display the vehicle location as updates are received from the driver app.
The passenger boarded section displays the actual boarding location and associated time. The scheduled disembarking section displays the final stop for the route with expected arrival time.
Once the passenger disembarks, the actual location and time of disembark will be displayed:
Kura portal users can also access unexpected journey by refreshing their screen. Please note that it may take a few minutes before the journey is available so a few refreshes may be required. The journey will appear in the schedule calendar:
If the user selects the trip and the 'View Journey' button, this will open the journey information and map. If a journey is in progress, this will display the vehicle location as updates are received from the driver app.
The scheduled boarding section displays the stop that the unexpected passenger boarded and the scheduled time of departure from that stop. The passenger boarded section displays the actual location and associated time of boarding.
The scheduled disembarking section displays the final stop for the route with scheduled arrival time, until the passenger disembarks. Once the passenger disembarks the vehicle, the actual location and time of disembark will be displayed and the scheduled disembarking stop will be updated to display the stop where the passenger disembarked:
The journey will display in the passenger's schedule calendar, however, in all reporting (view journey and analysis usage and adoption reports) the journey will display as unexpected so that lost revenue can be captured.
Booking Request - Passenger Name:
When making a booking request as an Admin or Kura Ops user, the Passenger name was being replaced by an organisation title. This has now been resolved and the Passenger name will display in the booking request summary where Admins or Kura Ops are making a booking: