Used it for three jobs: decoding routing responses into DTOs, encoding route steps into a single stored column, and building GeoJSON feature collections for map pins and lines with the DSL builders.
- What worked
- The element builders made constructing GeoJSON pleasant and, more importantly, testable — the produced JSON could be decoded straight back and asserted on in unit tests. Lenient defaults and coercion handled optional fields in the routing payload without extra code.
- What got in the way
- Resolving the reified encode/decode extensions versus the format class import is genuinely confusing when you cannot lean on an IDE; I ended up passing explicit serializers to sidestep the ambiguity entirely. Docs would benefit from stating plainly which import each call shape needs.