-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove phone number from Assignments #2316
Comments
To my knowledge you cannot start filling forms in the app without having created a device id and user (going through the login screen). For existing devices, in Android we check if device has gone through setup (login) but we do not check specifically if the device id exists, maybe that would be time to add that check. Update: I have checked on akvoflow-7 datastore and found many devices without an id, last one created in May 2016 but one that was lastUpdated in Nov 2017. |
That does sound good. I also feel that you much have the device ID set up to use the app. I remember the issue was that the device had the ID specified but it not always showed on the workspace, but that should be resolved now. |
I believe our idea has always been to move towards having (clearly identified) users on the devices and as long as data is uploaded from an online device it should be associated with a user rather than a device ID. If data is in some way (we have to think carefully about this one) uploaded from an offline device, it should probably be associated with the uploading user rather than the presumed offline user. Such changes would obviously not be covered by the scope of this single issue but this issue could be a part of them. Perhaps for the time being we can leave in place information that is currently helping the users with orientation and identification and when we have the users in place we can start replacing this info. |
@muloem I fully agree with the case to move towards app users rather than having devices and indeed that it a larger change and we need a different issue for it. For this one, we removed phone numbers from the Device list with this change: #2299 because phone numbers are considered private information and we have other data we use to identify devices, thus we do not need to also store the phone numbers. As we need to become more responsible in how we handle personal data I thought we can start with stopping using phone numbers to identify devices and thus remove them from where they show in the UI (larger issue here akvo/akvo-product-design#282) |
With the new assignment UI we no longer show extra info on the devices, only the device name. |
Context
This issue is a follow up to the work done here: #2299
When the user creates an assignment she needs to also select the devices for the assignment. When she looks at the available devices, she chooses them based on the device ID given to the device in the app. But we also show with the device ID some other internal information. For some devices where we had the phone number available we show the phone number in the UI. Other devices show a different number.
Changes
Questions
@muloem and @valllllll2000 what are your thoughts?
Future improvements
Unifying and simplifying the device identification is a problem we will not solve with this issue but will deal with in a larger streak of changes - akvo/akvo-product-design#282 As we need to make sure we not only have a consistency in how we identify app devices but also fully remove all phone numbers from our database.
The text was updated successfully, but these errors were encountered: