How MeetMe went international on Android. Presented in 2012 to Android Alliance Philadelphia: http://www.meetup.com/AndroidAlliancePhilly/events/84300832/
§ Sr. Architect @ MeetMe
§ Amateur photographer and
§ Programmer, Developer,
Engineer, Architect, ScienFst
§ MeetMe sees internaFonalizing as mutually beneﬁcial
– Users get a beKer experience with naFve language support
– Large potenFal market outside of English-‐speaking market
(before and aHer)
§ Use strings liberally
§ Got a string that has a variable number in it? Use plurals!
Hello, one world!
Hello, %d worlds!
§ Use ‘em how they’re designed to be used (and more)
– (more) Gender-‐focused OR gender-‐neutral strings
§ First thing we had to reconcile out of the gate
§ We started with ~850 pre-‐exisFng strings entries (we were lucky to
have had the foresight to do this much)
§ Ended with ~910
§ IniFal translaFons
– Machine translate!
– Prove it out. Test it.
§ Designed to ﬁt
– Determine ways to abbreviate. Brevity will typically
beneﬁt you anyway.
§ Designed to ﬂex
– Update the layout to resolve any hard-‐coded
dimensions and be more ﬂexible
o ScrollView is your friend
o HorizontalScrollView too
o AutoResizeTextView (online)
– Calendar, Date
o Grouping (thousands)
§ Success/error messages
– Error types and codes corresponding to speciﬁc errors
o Invalid credenFals? AuthExcepFon#0x01
§ Huge and/or variable lists of anything
– Region names
– Random quesFons
§ NaFve speaker translaFons (outsourced)
§ NaFve speaker reviews (in-‐house)/QA review
§ In-‐house reviews
§ TranslaFon management can be a lot of work. Automate.
§ Ongoing development includes automated translaFon process
– Keeps developers from having to deal with logisFcs of translaFon management
BE AWARE OF…
§ Don’t assume you understand internaFonalizaFon
§ Wikipedia is your friend!
§ Nexus One
§ Nexus S
§ Galaxy Nexus
§ Nexus 7
§ Nexus 4