4 ms·
There is some nice advice in comments and articel I had a few more things that helped with a platform that I built that went global: - Internationalization -
by j45 9y ago
There is some nice advice in comments and articel
I had a few more things that helped with a platform that I built that went global:
- Internationalization - bake it into the bread from the beginning, the cost is marginal, relatively speaking. Internationalize the UI for sure, and make design decisions relative to having reasonable multi language support for any user type content. It won't be perfect out of the box, but you will have a huge head start when you have to optimize rendering of languages.
- Localization: The forgotten sibling of internationalization can be critical when going for an experience to show a native experience that is local and inviting to the user.
- Equality for the international user: Consider your browser configuration globally and not just North America, which is typically better equipment, higher screen resolution, faster internet connections, the latest browsers, etc. This doesn't mean avoiding using the latest and greatest, but consider it. As much as I like React, lighter libraries like Vue can be a little less heavy. Lean, mean, and fast go a long way when you have a user on an off-shore platform needing to access something required to do his job.
- Mobile first - the world is mobile first, North America is a mix. For many people, depending on the country, the mobile is the only device they have, through which they have to accomplish tasks that others may complete on tablets or laptops. Consider this in your design and also try using only a phone for a week to do what you do normally on a laptop - it can be eye opening.
Thanks to folks who have reccomended services like Chargebee - sharing current resources that solve neccesary problems like this help a lot. It's great to be able to take money in any form rather than force a user down a particular path.