Overview
We are pleased to announce the release of Android v7.10.0. Version 7.10.0 introduces push notifications for visit clock-in reminders, variance capture at clock-out, geofencing, and rich text formatting support in form submissions on Android. This release also includes bug fixes across drafts, sync, Smart Notes, and device compatibility.
New Features
Geofencing – Location-Based Clock-In/Out
When a carer attempts to clock in or out of a visit on Android, the app now checks whether they are within the configured location boundary.
Note: This feature is not active on mobile in this release. It will become available on mobile once server version 8.2.10 is released, at which point it can be enabled server-side to activate mobile functionality.
How it works:
If the carer is within range, the clock-in proceeds as normal with no additional steps
If they are outside the boundary, or if their location cannot be determined, a prompt appears asking them to provide a reason before they can continue
The reason, GPS coordinates, and override are all logged for audit purposes and displayed in the case history
Organizations can set the geofence radius at the tenant level via tenant preferences when available. This functionality will only begin to operate on mobile devices after that server-side configuration
What this means for you:
Carers will now be prompted for a justification if they attempt to start or end a visit from an unexpected location, helping teams maintain accurate time and attendance records
Knowledge Base Article: Geofencing Boundary
Push Notifications – Visit Clock-In Reminders
Carers will now receive push notifications reminding them to clock in within their visit window.
How it works:
Notification timing adapts to the length of the visit window:
For windows under 5 minutes, the reminder fires 2 minutes before the window expires
For windows of 5 minutes or more, it fires 5 minutes after the visit start or end time
If the carer has already clocked in before the start notification fires, no redundant notification is sent
Tapping the notification opens the app directly to the relevant clock-in screen
Notifications respect device-level permission settings, if the carer has disabled app notifications on their device, no notifications will be sent
Notification timing depends on the clock-in/clock-out window preferences configured on the server ("How Late Can a Visit be Started After the Visit Start Time" and "How Long After The Planned End Time Can A Visit Be Ended"). The mobile app syncs these values and uses them to calculate when each reminder fires.
What this means for you:
Carers no longer need to rely on memory to clock in on time
This reduces missed or late clock-ins
Helps maintain compliance with visit window requirements
Visit Variance Capture at Clock-Out
When a carer attempts to clock out earlier or later than the planned visit end time, but still within the configured variance threshold, they are now prompted to select a reason before the clock-out can be completed.
Note: This feature is not active on mobile in this release. It will become available on mobile once server version 8.2.10 is released, at which point it can be enabled server-side to activate mobile functionality.
How it works:
The prompt displays how many minutes early or late the carer is clocking out
A list of predefined reasons is presented, configured at the tenant level
If none of the predefined reasons apply, carers can select "Other" and type a free-text explanation
The clock-out cannot proceed until a reason has been submitted
If the carer closes the prompt without selecting a reason, they are returned to the visit screen and must complete the prompt before ending the visit
Variance data captured offline syncs automatically to the server once connectivity is restored
The reasons are logged and displayed in the case history
Organizations can enable the feature and set the reasons at the tenant level via tenant preferences when available. This functionality will only begin to operate on mobile devices after that server-side configuration.
What this means for you:
Managers and coordinators get accurate, real-time explanations for schedule deviations captured at the point of care, before the carer has moved on to their next visit
Knowledge Base Article: Visit Duration Variance Tracking
Rich Text Formatting in Form Submissions
Android carers can now apply rich text formatting (bold, italic, underline, and strikethrough) to text and paragraph fields within form submissions.
Note: This feature will not be active in this release. Full activation will follow once server version 8.2.9 is released to all users.
How it works:
A native formatting toolbar appears when a carer taps into a text field
Formatted text is stored as HTML and is fully compatible with text entered or edited on web or mobile
This means that if a form is created on web with formatting applied, an Android user can open and edit it without losing that formatting, and vice versa
What this means for you:
Carers can now document care records with the same formatting capabilities available on web and mobile, including using strikethrough to clearly indicate amendments to existing notes
Bug Fixes
When a device went offline during Smart Notes audio transcription, no warning was shown and the app became stuck on the transcription dialog until connectivity was restored. A warning message now displays and the process is safely ended
Form drafts were not being saved correctly when the form contained images
The keyboard was overlapping UI elements on devices running Android 15 or later, due to a change in how Android handles window insets
Missing draft submission calls in certain form flows were causing draft data to not be saved as expected
The Android app was not functioning correctly when the device was connected via an ethernet adapter
Users with more than 1,000 images in their account were unable to sync due to a failure in the image download process
The Upload Transcript File plugin could not be updated via the Debug Screen in Smart Notes
How this version will be made available
This update will be made available in the Google Play Store starting April 14th.
Availability: The update will be available for download through the Google Play Store. Users will be prompted to update when they next launch the app, or can update manually via the Play Store.
Coming Soon
Enhanced Offline Mode - Server unavailability handling
Ai Visit Notes Summary
Minimum Requirements
Operating System | Android 11.0 |
Screen Resolution | 800*640 |
Memory (RAM) | 4GB |
Storage | 1GB |
GPS | Yes |
Camera | Yes *
*to use the following functions on the app: QR Codes for visit verification Taking photos to upload / annotate within forms Uploading pictures from camera roll to forms (i.e. blank body map to annotate) |
Recommended Specifications
Operating System | Android 14.0 or above |
Screen Resolution | 800*640 or higher |
Memory (RAM) | 4GB+ |
Storage | 1GB+ |
Camera | Yes |
GPS | Yes |
NFC | Yes |