I'm currently writing a prototype of an AVOD Portal application for embedded systems using Qt and QML.
Basically, I have a catalog of media (music, stream, movies etc.).
I plan to have different views of media according to the choice of the users:
A proxy model is a model that happens to query other models behind the scenes. That a model is a proxy is an implementation detail invisible to the user of the model (e.g. to the view). There's nothing otherwise special about a model being a proxy from the model user's point of view. A proxy model is "just" a
QAbstractItemModel with some convenience code added if you happen to derive from one of the proxy base classes.
In other words, there isn't much to a proxy model: it must fulfill all of the requirements placed on a
QAbstractItemModel, because it is one.
So yes, your approach will work.