Fully support custom field type names within existing fields
Let's say you have a contact and they have an office in London and Berlin. You then create a single contact, and enter the phone numbers and addresses for each office. You create a custom type for the first phone number of "London" and "Berlin" for the second. Same for the addresses. The fruux web app handles this perfectly. Unfortunately, the fruux Android app completely loses all these custom types. Please support this essential feature in the Android app. When supporting it, make sure to test with custom types that include spaces, such as "New Brunswick". Thank you in advance!

-
Anonymous commented
Full support of custom field names, and maintaining their order, is essential. Will this be implemented soon?
-
Frank I. commented
Second. But I donot get custom types in the web app. How to?
-
Frankie commented
Absolutely agreed. I have heaps of those now using Google contacts: private mobile, private land, mobile father, ... It's somewhat of a dealbreaker for me.
-
Jack commented
I just ran an experiment. Instead of importing all the contacts into fruux on the web and then syncing with Android, I tried importing all the contacts into Android and then syncing with fruux. Different results. Now all the custom field type names are in Android and in the web fruux, but the order of fields is wrong in the web fruux. In the example above, in Android it shows the "London" phone number first, and then Berlin, but in the web fruux they are in the opposite order. When there are 10+ phone numbers for a contact, this is a big issue. Hopefully you will be able to support a full "round-trip" for the data starting either with the web fruux or the Android fruux.