ScreenManager emits signals (screenChanged, appStateChanged)
QML listens and updates currentScreen
I load screens dynamically using a Loader { source: currentScreen }

Inside each screen I also use QML states for internal animations/modes
This setup works well and feels simple to manage.

However, many examples and discussions recommend using StackView for navigation—especially for larger HMIs with animations, transitions, or back navigation.

So my questions are:

For an HMI with ~25 screens, is StackView the recommended / ideal approach?
Is there any long-term disadvantage in sticking to a Loader + custom manager approach?
Do automotive or production HMIs typically rely on StackView, or do they build custom navigation managers?
If I switch to StackView, will screen transitions and animations become easier to manage?

From a performance and architecture perspective, which approach scales better as the HMI grows?