FossifyOrg
[Feature request] Add support for structured addresses
Checklist
- [x] I made sure that there are no existing issues - open or closed - to which I could contribute my information.
- [x] I have read the FAQ and my problem isn't listed.
- [x] I have taken the time to fill in all the required details. I understand that the feature request will be dismissed otherwise.
- [x] This issue contains only one feature request.
- [x] I have read and understood the contribution guidelines.
Is your feature request related to a problem? Please describe. At the moment there is only a single field for addresses. Therefore addresses are not synced correctly when also syncing with other clients like Thunderbird which have structured address field support.
Describe the solution you'd like Add individual fields for the different address parts. Could be done as an option to support simple mode also for people who preferre this.
Describe alternatives you've considered The different fields could be merged into one during sync. This would not improve editing behavior.
Additional context This fork of Simple Contacts already contains structured address fields and I think the author would be willing to contribute. https://github.com/stephanritscher/Simple-Contacts
It would be great if @stephanritscher's patches could be merged into Fossify Contacts. I’ve been using his fork for a while and it works very well. Not only does it implement the correct address separation the vCard standard requires, ~~it also provides country-specific formatting of the whole address on the contact info screen. (I can only attest the latter for German addresses where the postal code is shown correctly before the locality, whereas most apps just format every address according to US rules.)~~ [Edit: I should have checked this first; apparently the app shows the postal code before the locality independent of the country of the address. I’ll have to investigate further if that is somehow specific to my phone's setup.]
Right now Fossify Contacts, same as the main-line Simple Contacts before it, stores the complete address in the street address field, which is just wrong; so I wouldn’t even consider this a feature request but a bug ticket.
Update: Since I’ve made the mistake of assuming the formatting feature mentioned above, I’ve made a corresponding feature request at https://github.com/stephanritscher/Simple-Contacts/issues/18. Should proper address handling find its way into Fossify Contacts, the same would be nice to have here as well.
For context, here is the original Simple Contacts discussion of this issue: https://github.com/SimpleMobileTools/Simple-Contacts/issues/364
Apparently the developer @tibbi thought making the address format standards-compliant was too much of a “complication.”
Must needed as now a days many people have structured addresses in Google Contacts. Import will be not proper without it.
It would also be useful to have address autocompletion using the Google Maps API, like it's the case even you're using the Google Contacts app or website. It ensures that addresses are spelled properly and in the right format (most of times).
the Google Maps API
Can't do that. All Fossify apps operate without internet connection.
the Google Maps API
Can't do that. All Fossify apps operate without internet connection.
True I forgot the core principle 🫠
Well, for what it's worth, there may be "connected" flavors in the future but only for apps and features that really make sense.