4 ms·
"Users will only store phone numbers in your product's phone number fields" Not entirely sure what this point is trying to achieve. Do you read a birthday fiel
by lxmcneill 8y ago
"Users will only store phone numbers in your product's phone number fields"
Not entirely sure what this point is trying to achieve. Do you read a birthday field expecting a phone number 99% of the time? Should you read a phone number field expecting an email address? And at what point in that process did you decide that not having data validation on both ends was a good idea?
- reaperducer 8y agoIf you’re making an address book app, don’t expect people to put what you expect in the fields you give them just because you label the fields a particular way.
- clort 8y agoSo since I got a phone I have always used it as my address book (yeah, I export and back it up). In the early days Android was pretty nice. You can enter all sorts of things in there; multiple addresses, numbers, company information, birthdays of friends or other important dates etc.. But latterly, Android just won't do birthday dates. Oh sure, the dates are still in there and get exported from the database but there is no way to enter the information or look at it on the phone (I use BirthdayAdapter from F-Droid which causes a reminder on the day) I expect that some people just put the birthday of their friend in a phone number field. In fact I'm pretty sure that millions of people just use random fields for their own purposes full stop, they just don't care about any of that. So the article is saying that it is their phone, don't try to control them. If information is in the field and you can't parse it? You store it and export it as received but otherwise ignore it..