As defined under T-1-1 of documentation & tools OKRs for 2025/10-2026/01.  

Define how QML profiler is added to the VS Code workflow (especially the visualization of the profiler data). 

As a backgrounder for the design work, utilize [the study conducted earlier|https://miro.com/app/board/uXjVJX3DGDI=/?share_link_id=119075475004 as the baseline, and supplement it with evaluation of other tools - including, but not limited to CLion, IAR workbench, VS Code solutions.  

Define the requirements for profiling - what are the jobs that the developer does while using profilers, what kinds of issues can be discovered using profiling. Utilize the list of jobs as a baseline to create repeatable processes that utilize profilers. 

Contrast single language tools (e.g. QML profiler) with holistic profiling - the ability to view the behaviour of the application across language barriers, initially C++, eventually encompassing the whole set of Qt Bridges languages - evaluate their goals and needs. 

Canonical list of C++ profilers: https://hackingcpp.com/cpp/tools/profilers.html

Pick profiler users for interviews from customer engineering (since they are likely to actually use the tool).