The slot signature for JsonDbClient query result is a QVariant, documented to always be a QVariantMap, documented to carry a fixed set of values accessible by keys "data", "length", and "offset". All this useless dynamicity makes the API more tedious and error-prone in usage, and has a performance cost to wrap the result data inside the library and use it in native clients. Could there be a dedicated result type with fast property accessors for native clients, plus QML bindings for dynamic ones?