As per Documentation & Tools OKR 2025/06-09 item D-5-6: 

In interviews conducted for the Qt Developer Tools strategy multiple respondents stated that profiling is hard to discover and utilize - mostly this was about profiling in general, not necessarily only in Qt Creator context.

This task concerns itself with researching options to make the profiler more visible/UX friendly. 

Focus on how to provide a holistic view into the behaviour of the application, not only a single-language take (e.g. while QML Profiler is an important factor of the service, it is not the whole story). Also take into account other Qt initiatives such as:

• embedded Linux data collection & tools,

• evolution of the use of common trace format.

Also, benchmark what is the state of the art in alternative tools and how Qt tools could be improved based on the findings:

• Visual Studio Code,
• Visual Studio
• CLion
• Xcode
• selected embedded hardware specific tool (to be selected in collaboration with the embedded team).

Additionally, evaluate possible ways to feature the functionality to ensure that developers are aware of its existence.