In today's enterprise landscape, Mobile Device Management (MDM) software is essential for securing and managing applications across a variety of devices. Ensuring the Wello Field Service App is fully compatible with MDM solutions enhances usability in professional environments and strengthens compliance with security standards.
1. Application Packaging and Deployment
The Wello Field Service App is available in standard formats compatible with most MDM platforms:
Android:
.apkiOS:
.ipaWindows:
.appx
Additional formats such as.msifor Windows can be provided upon request.
Note: Executable files for Windows Store apps can be retrieved using tools like the Microsoft Store Apps Executable Downloader or the Windows Package Manager (WinGet). Similar tools exist for Android (APK) and iOS (IPA).
All app versions are securely signed with the appropriate certificates to ensure trusted deployment.
2. MDM Configuration and Policy Support
The Wello app supports key MDM policies, including:
Remote installation
Automatic updates
Remote uninstallation
The application adheres to standard enterprise security policies, supporting encryption, secure authentication, and user data protection.
Data Safety
Definitions and description of the data collected/used can be found here Data types
The application exclusively establishes outbound connections to our backend infrastructure over the HTTPS protocol via TCP port 443. All traffic is directed to a fixed DNS hostname, which can be explicitly whitelisted through the Mobile Device Management (MDM) solution.
The local database used to cache data and allow 'offline usage of the app, is also encrypted on the device.
Users can request deletion of their data upon cancellation of their subscription. In fact, mobile users can themselves remove all data from their device whenever requested.
Application Version Management
When a new version of the app is released, the immediately preceding version remains supported without an end date, while the version before that receives a default three-month end-of-support period.
Example:
If version v3.0.3 is released on 01/05, then:
v3.0.2 remains active without an expiration date (until v3.0.4 is released).
v3.0.1 receives an end-of-support date of 01/08.
This three-month period ensures sufficient time for all company devices — including those in storage, with technicians on leave, or in less active use — to be updated accordingly.
The purpose of this policy is to prevent outdated versions from being used in production, ensuring all users benefit from the latest improvements and security updates.