Junichi Okamura discusses issues his development team faced when designing the user interface for a Japanese business application. The team struggled to concisely label fields and structures due to the flexible meaning of Japanese terms and the complexity of features in their product. This made the UI design difficult to explain to customers. To solve this, Okamura recommends thinking of designs and labels in English first before translating to Japanese, in order to focus on simplifying terms and structures rather than fitting whole meanings. Following this approach helped avoid similar problems when the product was released with multilingual support.
2. 2
LibreOffice Productivity Suite
About Me
Name: Junichi Okamura
Job: Software Engineer
Role: R&D Manager in SHANON, Inc.
Interests:
- Functional programming, PAAS, huge data analysis, O2O with
new devices(iBeacon, wearable..)
- Multilingual application, messaging software
- API driven business
Hobbies:
- Drawing, playing rocks, drinking (party)
IDs:
- Twitter&GitHub benzookapi
3. 3
LibreOffice Productivity Suite
About My Job (Company)
Name: SHANON, Inc.
Business: All-In-One Marketing cloud service
SHANON MARKETING PLATFORM
Customers: About 300 companies
Employees: About 120 people (Tokyo, Miyazaki, Shanghai)
My Job:
- Product planning (new features with new technologies)
- Team handling (scrum master)
- Development (code review, testing and documentation)
- Product evangerising (to sales staff)
- NOMIKAI (drinking party) arrangement
5. 5
LibreOffice Productivity Suite
Known Issues [1]
Japanese have KANJI and less characters can express more
meaning than English
- e.g.)
最終登録失敗時の通知先:
Notification target in the last failure of
registration:
6. 6
LibreOffice Productivity Suite
Known Issues [2]
Business application (BtoB) needs more complicated
(precise) UI than consumers' one because it covers
companies' complicated business activities
- e.g.)
VS
*Images are just for example! (not blaming)
7. 7
LibreOffice Productivity Suite
What Happened In My Team?
UI designers (developers in our case) have been lost in
deciding field structures and labels (re-naming, changing
positions and styles again and again...)
UI design given by teams is difficult to explain to business
owner and sales staff and describe in documents
11. 11
LibreOffice Productivity Suite
What Developers Did?
They started UI design by Japanese sentences and try to stuff
whole meaning to each field and labels
This made each field meaning and purpose uneasy to
understand
最終登録失敗時の通知先:
14. 14
LibreOffice Productivity Suite
If Our Customers Use English...
The UI may be restricted in small labels and inflexible terms
This enables developers to focus on refining structures and
simplifying the terms, not depending on Japanese flexible
expression
This makes each field meaning and purpose easy to
understand
Last Registration:
Notification Target:
[Only in failure]
17. 17
LibreOffice Productivity Suite
At The End
Our products already support multilingual (English) and avoid
these problem before released
The captured images are just for example (used applications
are both great!)
Japanese is a great language itself with good culture, I think
18. 18
LibreOffice Productivity Suite
All text and image content in this document is licensed under the Creative Commons Attribution-Share Alike 3.0 License
(unless otherwise specified). "LibreOffice" and "The Document Foundation" are registered trademarks. Their respective logos
and icons are subject to international copyright laws. The use of these therefore is subject to the trademark policy.
Thank you!
Junichi Okamura