Regarding Location tracking as Critical Bizom functionality / Workflow

Regarding Location tracking as Critical Bizom functionality / Workflow

Request to Sales team
Location tracking MUST NOT be used a User workflow.
This functionality MUST NOT be used for linking with Claims etc.,

Please DO NOT SELL the functionality as User workflow.
It is NOT a critical functionality in Bizom.
It is an additional feature provided by the Bizom app. 
Why Location tracking can not be a User workflow / Critical functionality in its current Avatar
This functionality has dependencies on 
a. User behaviour (switching off GPS, internet etc.,)
b. Network condition (good signal) etc., 
c. Background thread restrictions from Android platform (Doze mode)
to work properly. 
These dependencies can not be overridden / controlled by the app as the Location tracking happens in the background (which does not require UI).
Hence the accuracy of the functionality is very hard to achieve.

Every Critical Bizom functionality (e.g.,Visit/Forms/Attendance etc.,) is based on User actions (done through UI). 
In this case, the above dependencies can be overridden / controlled by prompting User to enable GPS / Mobile data compulsorily.
And with Geo-fencing functionality additionally, User can be disallowed to do remote transactions.

Regarding bug fixes
Any bug in Bizom app (including this functionality) will be taken up and fixed.

Already, there have been bug fixes while getting Location to
a. Remove Out-of-Sync locations
b. Sync pending non-EOD Bizom transactions before EOD is synced (to avoid difference in EOD / User map view distance travelled.)



What NEXT? (Solution)
So, what happens to the distance travelled information in User mapview / EOD?
Should it not be used for User Claims?

Use case 1: User captures ONLY Attendance and EOD in Bizom
User does not capture any data in Bizom (apart from Attendance and EOD).

In this scenario, distance travelled information will not be accurate and not dependable.
Bizom will NOT support this use-case.

And frankly, User just roaming around without doing anything in Bizom does not make any sense.

Use case 2: User captures data in Bizom
User captures some data (e.g., Forms / Transactions etc.,) in Bizom app on Outlet/User visit etc., (along with Attendance and EOD)

If User captures data, then the distance travelled information will be closer to reality.
Irrespective of this, Distance travelled will always be an approximation.
Please convey this accordingly to Bizom Customers.

Conclusion
Use case 1 will not be supported.
Distance travelled information will be more acceptable in Use case 2.

Using it with User Claims should be based on the assumption that the distance travelled is an approximation.
Presently, the exceptions / conflict resolution is not in Bizom app.
So, exception handling has to be taken at Company policy level.

Final NOTE:

In Bizom, we do not have functionality to find the Distance travelled accurately.

If this functionality is required (as used in Ola/Uber), Bizom App has to enable the GPS at all times. 
Bizom app does this through Geo-fencing to an extent. 
But even here, location captured every 10 second is not synced to Bizom server.
And always on GPS and Phone screen has implications on 
a. Battery life and 
b. User experience (Phone has to be plugged in / Power bank to be carried) etc.,

So if this functionality is Critical Requirement, it needs to be though through properly.
Till then, please DO NOT sell this functionality as a Critical Business workflow.