Grygoiry Gonchar at
summary
Concrete claims about when to localize and how to implement it: shows Typescript definition and a configurable React component pattern to toggle fields like ZIP code, contrasts Netherlands and France search widgets and a full German sell flow, recommends start global then add local components and fork into separate services only when complexity explodes, and covers performance fixes including multi-region deployments and CDN/Cloud Network acceleration. Organizational advice maps stream aligned teams to local vs global responsibilities and when to create market specific engineering teams.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 0:27Overview
- 2:51Car markets
- 5:19Localization
- 8:22Code example
- 12:06Entire flow example
- 13:30Modularization
- 16:55Latency
- 19:10Technical
- 22:11Business Team
- 24:07Engineering Team
- 25:35Verticals
- 26:16Teams
related talks
08mLocalization for Real-World Use-Cases: Key Learnings from Onboarding Global Brands
12mThere's always a better way to handle localization
22mInternationalizing React
33mBuilding modern React applications
30mMicro Frontends in React — a State of the Art Approach
37mBuilding Better Components — A Journey to a More Resilient Frontend
33mMaximising performance with React code-splitting techniques
36mFrom Local to Global Service Based on Symfony2