Mobile app forced updates

Overview

Twice a year, on 1 May and 1 November, the Urbantz driver app requires an update before drivers can keep using it. We announce each forced update ahead of time so IT teams have time to roll it out to managed devices.

How updates work:

• After every release, a reminder. From one week after a new version is released, drivers see an update screen every 9 days. They can always dismiss it.
• Twice a year, a required update. On 1 May, drivers must move to the latest app version. On 1 November, the oldest Android and iOS versions are no longer supported. After the deadline, the app can't be used until it is updated.
• Once a year, the oldest OS version is dropped. Each autumn, one major Android version and one major iOS version leave support.

The yearly calendar

The newsletter warns customers months ahead. On the last reminder, the countdown switches on in the app.

Schedule and supported versions

We announce every forced update in our customer newsletter months before the deadline. With the last reminder, a countdown also appears in the app so drivers know the date is coming.

Currently supported operating systems:

Important: Planned minimums can change; Please read the newsletter announcement for each deadline, which confirms the final versions.

What drivers see

When the app is out of date, drivers see a full-screen update page in your brand colour. Its Update button opens the app store. There are three versions of the page, and the app always shows the strictest one that applies.

The app checks for updates when the driver opens a main screen, such as My mission, the task list or the parcel scanner. At sign-in, only the Required screen can appear.

How to prepare

Roll out the update before each deadline so no driver is blocked on the road.

1. Watch for the announcement in the Urbantz newsletter and share the deadline with your IT team.
2. Check your devices. Make sure every driver's phone runs a supported Android or iOS version. Phones that can't reach the new minimum will no longer be able to use Urbantz after 1 November.
3. Update the app on all devices before the deadline:
   • Google Play (Android)
   • App Store (iOS)
4. If you use APK hosting (a paid option for managed devices that can't use Google Play), your IT admin installs the new APK from the download page Urbantz shared with you. The new APK is published once the Google Play release is complete. On these devices, the in-app Update button still opens Google Play, so your IT admin must install the update.

Why we drop old OS versions

• Security. Google and Apple only patch recent OS versions. Driver phones hold customer addresses, phone numbers, signatures and delivery photos, and an unpatched phone puts that data at risk.
• App store rules. Google Play and Apple require apps to be built with recent tools, and the maps, scanning and reporting features we rely on keep raising their own minimum.
• Reliability. Older versions bring their own camera, location and background bugs.

On Android, a phone stuck on a dropped version is usually one its maker stopped updating, typically 7 or more years old. On iPhone, most dropped versions only affect phones that haven't installed available iOS updates.

FAQ

What happens if a driver doesn't update before the deadline? The app shows the Required screen and can't be used until the driver installs the update.

Can drivers dismiss the update reminder? Yes, until the deadline. Recommended updates reappear after 9 days, and announced mandatory updates after 3 days.

Our drivers can't install apps themselves. What should we do? Ask your IT team to push the update to managed devices before each deadline. That's why we announce forced updates months in advance.

What if a phone can't upgrade to the minimum OS version? That phone can no longer run Urbantz after the 1 November deadline and needs to be replaced.

Where can I see the exact versions for the next deadline? In the newsletter announcing it. Contact your Custoemr Success Manager or support if you have questions.