I'm thinking about a Layer which supports model-compatible Objects, both derived from QAbstractItemModel, lists and jsons; and delegates responsible for drawing the data.
Pretty much like MapItemView in the QtLocation api, but with support for lists and jsons.
In our common scenario we have a model which is derived from QAbstractItemModel which cointains records that are points of interest and itineraries.
The available delegates should mimic ArcGIS symbols and also allow for custom components.
We represent geometry as a WKT string, so direct support for that is also welcome, to avoid non-optimal runtime conversions.
Does that make sense?