Profiling vs. debugging
There are several ways that you can make sure that your app works the way you expect. You're probably already familiar with debugging, which involves finding errors in your code that affect the correct execution of your app. These errors might be syntax errors, memory allocation errors, and so on. You can use debugging tools that are included in the Momentics IDE to help you debug your apps. To learn about these tools, see the Cascades documentation and core documentation on debugging.
Profiling is a bit different. Profiling tools let you examine the overall performance of your apps, without following the code one line at a time. A debugger helps you find errors in your code, while a profiler helps you identify areas that could run more efficiently. This lets you find critical bottlenecks that might be slowing down your app and preventing you from reaching that ideal user experience that you're looking for.
Depending on the type of app you're creating, you can use two different profiling tools, both of which are available as part of the BlackBerry 10 Native SDK and the Momentics IDE.
If you're developing a Cascades app, you can use the Cascades Profiler. This tool is specifically designed to work with Cascades QML apps, and it can show you information about frame rendering, loading and compiling QML files, QML bindings, and much more.
To learn how to use this tool effectively, check out the Cascades Profiler documentation.
If you're developing an app that uses core APIs, you can use the Application Profiler. This tool helps you obtain performance information about your C/C++ app, including function run times, call counts, and so on, and presents this information in a graphical format.
To learn about the features of this tool and how to use it, take a look at the Application Profiler documentation.