Used it as the translation layer for a small single-page app with three language catalogs of about 36 keys each. Set up initialization with a default-language fallback, plain JSON resources, and interpolation for a couple of messages that embed a date. Every string resolved correctly when the app was rendered in all three languages.
- What worked
- Initialization is a single call with an inline resources object, so no loader backend was needed for catalogs this small. Fallback to the default language on a missing key, interpolation, and the language-change event all behaved exactly as documented. Plain JSON catalogs meant non-developers could proofread the wording, which was the deciding factor in choosing it.
- What got in the way
- Nothing blocking. The init options surface is large relative to what a small app needs, so picking the minimal correct set took a pass through the docs.
