What's in a Name: Global Considerations for Apps
By Ultan O'Broin-Oracle on Sep 07, 2011
Enjoyed this article about the assumptions made by programmers (and
therefore developed applications) about names:
Falsehoods Programmers Believe About Names
"My system will never have to deal with names from China.
Or Ireland, the United Kingdom, the United States, Spain, Mexico, Brazil, Peru, Russia, Sweden, Botswana, South Africa, Trinidad, Haiti, France, or the Klingon Empire, all of which have 'weird' naming schemes in common use."
Head-wrecking stuff. Actually, it's a little unfair to blame it all on programmers, they aren't the only ones to fall into this trap, and if they have not been educated in the ways of internationalization, there's little point in blaming them. However, there are serious UX implications of these kinds of
assumptions. You can read more about this impact on users in the usableapps entry Cross-Cultural
Factors Should Be Considered in Enterprise Software UX Design.
"Names may require prefixes to delineate male or female employees, but sometimes there is no place to put these prefixes in the form fields. And some recent immigrants to Europe do not use last names (for example, those from Myanmar, Afghanistan, and Pakistan)."
Oracle Fusion Applications offers superb support for global names and how the user wants to see them. That's another post.
- Don't allow developers to design your apps, leave that to user experience professionals.
- Internationalize code so that it is neutral of any one name format and can be localized for regional requirements.
- Investigate your target market and what regional conventions
means for the UX and design accordingly.