digiQC enables companies to get authentic site inspections through mobile and monitor them on web browsers. To run inspections and monitoring reliably, your mobile and web should meet the following requirements.
4G or 5G internet speed (for offline, see "Working offline" below)
Fingerprint or Face ID enabled phone
GPS-enabled phone
Good battery health
Working camera (to take real-time photographs)
Latest version of Chrome / Edge / Firefox browser (for the web app)
For the app to work fully, allow these permissions when prompted:
Camera — to take real-time inspection and issue photos.
Location — for geo-tagging and geo-fencing; allow location access as prompted.
Notifications — for alerts on assignments, responses and approvals.
Storage — to hold data and photos for offline use.
Biometric (fingerprint / Face ID) — for authentication before an inspection.
RAM: minimum 4 GB
Android 11.0 (Red Velvet Cake) and above
Free storage: minimum 10 GB
Supported brands: Samsung, OPPO, Motorola, VIVO, XIAOMI, OnePlus, Google, Sony
iOS 16.6 and above
Free storage: minimum 10 GB
iPhone 8 and above
Devices running outdated or unsupported Android/iOS versions may face performance issues — for reliable operation, we recommend not using such devices.
digiQC's support is aligned with the OS versions officially supported by Google and Apple. Versions no longer supported by Google or Apple will not be supported by digiQC.
On an unsupported OS version we'll try to help, but a solution can't be guaranteed. Unsupported versions carry security risks, may not support new features, and have a higher chance of bugs, threats and vulnerabilities.
Rooted or jailbroken phones are not supported. A rooted (Android) or jailbroken (iPhone) device has had its built-in security removed, which compromises data integrity — digiQC will not run on such phones.
Below-spec phones aren't guaranteed support. If your phone doesn't meet the minimum requirements above (RAM, OS version, free storage), digiQC may still install, but if you hit a problem we'll log the bug and try to help — we cannot guarantee a fix or full support on under-spec devices.
Keep your OS and the app up to date. Where possible, update your phone to the latest Android or iOS version, and always use the latest digiQC app version — this gives the highest level of support, the newest features, and the fewest bugs.
Devices that no longer receive OS updates are not supported. Once a phone model stops getting Android/iOS updates from Google or Apple, digiQC no longer supports it (see the OS support policy above).
A good location signal is required for geo-fencing. At any site where you enable the geolocation boundary (radius), the phone must get a strong, accurate Google location fix — otherwise inspections that depend on being inside the radius may fail or be blocked.
Keep automatic (network) date & time switched on. Every inspection and issue is time-stamped and cannot be edited afterwards, so the record depends on the correct time. If the phone's date/time is wrong or set manually, it affects the authenticity of the record — always let the phone set the time automatically from the network.
digiQC runs on secured AWS servers — your inspection data and photos are stored securely in the cloud.
digiQC is enabled for offline working, but limited connectivity changes how it behaves — here's exactly what to expect:
You won't see new changes while offline. Anything added or changed on the server (new checklists, users, assignments) will not appear until the phone is back online.
Fetch your data while online first. Before going to a site with poor connectivity, open the app while you still have internet so it downloads (caches) all the data you'll need — you can then work fully offline.
Offline actions upload only when you reconnect. Inspections, responses and photos you record offline are stored on the phone and are sent to the digiQC server automatically the next time you have an internet connection.
The next stage waits for the previous one to sync. For an EQC that hasn't synced yet, you can start its next stage only after the previous stage has been synced (uploaded) to the digiQC server.
Sync and photos use mobile data. Downloading data and uploading photos consume mobile data, so sync over Wi-Fi where you can, and keep enough free storage before a long offline session.
Android (Google Play): Click Here
iPhone (App Store): Click Here
4G or 5G. Offline working is supported if you pre-fetch data while online.
Android 11.0 or above, 4 GB RAM, 10 GB free storage.
iOS 16.6 or above, iPhone 8 or later, 10 GB free storage.
Camera, Location, Notifications, Storage and Biometric — allow these for full functionality (photos, geo-fencing, alerts, offline, and authentication).
No — support is aligned with Google's and Apple's supported versions. On an unsupported version we'll try to help, but there's no guarantee, and it carries security and stability risks.
On secured AWS servers in the cloud.
From the Google Play Store (Android) or the Apple App Store (iPhone) — links above.
Records are time-stamped and immutable, so a manually changed device time can affect their authenticity — keep network date & time on.
Yes — fetch data online first, work offline, and it syncs when you reconnect.
The previous stage must be synced to the digiQC server first.
4G/5G; a GPS + camera + biometric phone; the latest browser for the web app.
Android 11+ (4 GB / 10 GB) or iOS 16.6+ (iPhone 8+ / 10 GB); support follows Google/Apple — no rooted/jailbroken or outdated devices.
Allow Camera, Location, Notifications, Storage, Biometric; keep auto date & time and the latest app version.
Data is stored on secured AWS servers.
Geo-fencing needs good Google location; offline works with pre-fetched data and syncs on reconnect (sync on Wi-Fi where possible).
2.2.3 How does the Sync feature work?
2.2.16 How to do the next stage in offline mode from the Sync tab?
1.4 Who can benefit from digiQC & its features