Confirm
336
edits
Changes
→3. Event loop responsiveness
'''What does it mean''': See http://paulrouget.com/e/fxoshud/ for an excellent description. Keeping the event loop delay is important to having a smooth and responsive app.
This step is very important. It's only listed 3rd to make sure the simplest problems have been resolved first.
'''Verification Steps''':
* In the Developer menu -> Developer HUD, turn on the 'Jank' counter.
* Perform all common interactions with the app. Track the 'Jank' number for each of the interaction. When that number is above 10ms your app is at risking of dropping frames. Once that number is 100ms painting will fall behind and input will be delayed. 500ms+ indicate that this interaction will be noticeable jerky.* Understand the worse case responsiveness for each interaction of your app. Consider various workload for your app (like 5000 pictures). '''Debugging''':* Profile the app' main thread, good if you can't make an educated guess: https://developer.mozilla.org/en-US/docs/Performance/Profiling_with_the_Built-in_Profiler#Profiling_Boot_to_Gecko_%28with_a_real_device%29* For Javascript related slowdown: Add function duration logging throughout the code.* Disable some functionality of your app to see if that reduces the event loop lag (jank).
