We should figure out what's the state of the art regarding default qml import paths for macOS app bundles, what to recommend going forward, and how to adjust our example projects.
Currently we have a few different ways we handle qml import paths for macOS app bundles.
Explicit addImportPath call to a PlugIns subdir plus manual copying around of qmldir and plugins files
Calling addImportPath via DECLARATIVE_EXAMPLE_MAIN pointing to PlugIns subdir + macro to copy around the qmldir
Using new Resources/qml import path introduced with https://codereview.qt-project.org/c/qt/qtdeclarative/+/384645
to be used with the Qt 6.3+ deployment API, an no manual addImportPath call
This manually calls addImportPath to Resources/qml, before the change above landed, but after deployment API was mostly done.
One concern was that we can't use the new API to place stuff correct in the bundle of our examples yet, because it's still in Technical Preview.
But the default import path is not in TP, so in principle manual addImportPath calls in our examples could be removed if we also adjust the location of qmldirs and plugins.
Recently a new default import path for user projects was introduced via
which is qrc:/qt/qml
Need to consider if that changes anything.
We also had some previous discussion at https://codereview.qt-project.org/c/qt/qtdeclarative/+/366961/comments/96650614_1b7b2adf