Release Notes: iOS Bringg Driver App

BRNGG-3292

(App2) You can now require drivers to fulfill orders according to the sequence of the route. This aligns functionality with Android. Contact your Bringg representative to enable this setting.    

BRNGG-6263

(App2) Drivers using the Driver App can now change delivery statuses and manage inventory on clustered orders, all in one go. A clustered order contains several distinct orders for different customers with the same destination. This aligns functionality with Android.    

BRNGG-10524

(App2) Bringg's Driver App now allows drivers to perform a cluster delivery for a group of unrelated orders which share a delivery destination. For example, if a driver brings several orders of merchandise from a warehouse to a store location, they can perform a single action to confirm their collective delivery.

BRNGG-11299

After a fix, the automatic check-in and out triggers, and subsequent reporting, functions correctly.

BRNGG-6527

Drivers can now perform actions related to starting or ending their shift directly from the Driver App. For example, if a dispatcher requires a signature when the driver begins a shift, the driver will receive a prompt to add it immediately. This aligns functionality with Android.

BRNGG-3370

Bringg now displays handling units in the Driver App, allowing drivers to understand how many units they need to account for at a glance. For example, a driver can now locate the four pallets indicated in the Driver App and know they collected all the items for delivery on their route.

BRNGG-3293

Drivers can now add a second destination to an order with a single destination. For example, a driver arrived to replace a flat tire, which is a single destination service order, and discovers the reserve tire is missing and now needs to tow the vehicle to a garage. The driver can now add the garage destination as a second destination by selecting "Add Waypoint" in the Driver App, instead of calling the dispatcher to adjust the order.

BRNGG-6526

To ensure drivers do not miss any canceled order notifications, we added a new configuration "enable_cancel_task_notification_snoozing" for the notification to reappear when drivers do not confirm they saw that an order is canceled. The interval is fixed to one minute.

BRNGG-6555

When a new order is assigned to a driver, in addition to "Accept" or "Reject", drivers can select "Not Now" to leave the order as unaccepted, drivers see it in their list of orders to tap and decide whether to accept or reject it.

You can set the order to auto-reject after x minutes and return to the AutoDispatch pool (merchant_configurations.auto_reject_unaccepted_task_after_minutes).

BRNGG-3315

The driver app now displays prices using the currency format based on the language settings in your phone. For example, for US Dollars 151767 appears as 151,767.00.

BRNGG-7533

(App2) Drivers can now call phone numbers directly from notes in the Driver App, instead of copying and pasting them into the dialer. This way, drivers can easily contact consumers who have a second phone number listed in the order.

BRNGG-7526

(App2) Drivers using App2 can now easily take ownership of an order during handoff, by scanning a barcode/QR code placed on a package. For adhoc orders, drivers can add the goods related to the scanned code to a new order.

BRNGG-7527

(App2) "Driver unavailable" is now supported in iOS App2, along with Android. See the help content for this feature.

MOBILE-7608

Now drivers can log in to Bringg using Google's SSO (Single Sign-On using OpenID connect) on Android and iOS devices. This allows drivers to login quickly using their Google credentials, so they can skip typing in their email and password while keeping their data safe.

MOBILE-6636

(App2) Now you can persistently notify drivers of new orders until they respond (e.g. accept or reject the assignment). Set reminders as frequently as every 60 seconds. Set the time between each reminder in B-Control > User Configurations > New_Task_Alert_Snooze_Time_Interval_In_Seconds. Also available in Android.

MOBILE-6858

(App2) The hands free feature in the Driver App provides automatic check-in and out of home (fulfillment center) and delivery destinations, allowing drivers to focus on their work. After a fix, the check-in and out trigger, and subsequent reporting, functions correctly even if a driver starts multiple orders at once in the Driver App.

MOBILE-7242

In keeping with our policy to support the last three iOS versions, the Bringg Driver App now supports iOS 13.x, 14.x and 15.x, running on at least iPhone 6s and iPhone SE. iOS 12 is no longer supported.

MOBILE-7412

When you edit an order in iOS App2, you can now change the "Scheduled At" field to update the date and time.

MOBILE-7186

(App2) It is now possible to allow drivers who are listed on more than one team to choose which to work with each shift. Alternatively, a dispatcher can start a shift for the driver using the API and select the active team in advance.

MOBILE-7382

If you built routes without yet assigning them drivers, drivers can now view and self-assign those routes directly from the iOS driver app (App2). For example, if you plan routes based on particular vehicles rather than drivers. This aligns functionality with Android and App1.

MOBILE-7316

(App2) When an order has a long description, drivers can now see the whole description in the app, not just the first line.

MOBILE-6486

Drivers can now trigger route optimization directly from the iOS driver app (App2), aligning functionality with Android and app1.

MOBILE-7212

(App2) Drivers can work for several organizations or several locations that use Bringg, by joining multiple teams. Each shift the driver logs in to the relevant team. The driver can now see the name of the team they are currently logged in to, the "active team," in the Driver App side menu, allowing them to clearly see that they have logged into the correct account.

MOBILE-7293

Added functionality to iOS App1 to be the same as App2, where drivers who are listed in multiple teams can (upon configuration) select the team they will join for a specific shift. This feature cannot be used with Delivery Blocks.

Note: If you start the same shift on multiple devices, the second device will not auto-select the active team. To resolve, end the shift on the first device and restart the shift on the second device.

MOBILE-7124

(App2) Drivers who are listed in multiple teams can (upon configuration) select the team they want to join for a specific shift. This feature can not be used with Delivery Blocks.

Note: If you start the same shift on multiple devices, the second device will not auto-select the active team. To correct this, end the shift on the first device and restart the shift on the second device. Coming soon: Work for multiple teams during a single shift.

MOBILE-7188

(App2) The Driver App now displays the name of the route and its start / end times at the top of the list of orders, just like in the Android app. This makes it easier for loaders to find the items for each driver, and for drivers to identify the route assigned to them.

MOBILE-6528

The Driver App now snoozes the notification of a new order according to the interval configured in new_task_alert_snooze_time_interval, which aligns it with the Android app.

MOBILE-6835

(App2) When drivers leave their home base in hands-free mode, the iOS app can now automatically start the first order on the route, just like the Android app. Set this behavior with user_configuration.automatic_start configuration.