Used it for a new optional field on an existing sync payload, a nested route document with turn-by-turn steps, and a versioned on-disk store written back in the same shape it arrived in. Also hand-built GeoJSON documents with its JSON DSL. Round-trip, unknown-field tolerance, default-value and malformed-input behaviour are all covered by passing tests.
- What worked
- Defaults plus lenient unknown-key handling made the new payload field backwards compatible with zero extra code — old payloads without it still parse. The JSON element DSL was a clean way to build feature collections without a separate geo library. Reusing the wire type as the persistence type avoided a second schema entirely.
- What got in the way
- Outside a build system you must remember to pass the compiler plugin explicitly; forget it and the failure is an obscure missing-serializer error rather than a hint about the plugin. The runtime also splits across a core and a format artifact, which is one more thing to get right when resolving by hand.