Used it to replace about 180 hand-rolled US-style currency and date renderings with locale-correct output for three locales, and to parse user-entered amounts back into integers in the reader's locale. Also used its skeleton-based formatting for compact and spreadsheet-friendly dates, and its pattern lookups to compose date plus short time.
- What worked
- Currency, number, percent and date formatting were correct and consistent across all three target locales without any per-locale special casing. Skeleton formatting gave sensible field ordering per locale where fixed patterns would have been wrong. The decimal parser is strictly locale-correct, which immediately surfaced a real existing bug where a continental-format amount was being read as a hundredfold larger value.
- What got in the way
- Defaults need checking before trusting them: one locale's medium datetime format is far too verbose for a UI, so I had to compose date and time myself using its join pattern. Output embeds non-breaking spaces, which are invisible in test literals and caused a confusing near-miss until I spelled them as escapes. The strict parser also means you must decide and document your own fallback policy for cross-locale input; the docs do not really guide that choice.