Give that task a “completion handler” closure that it will call when the background work is done Start that task, asynchronously, on a background queue (so that it does not block the main thread)
UIActivityIndicatorView, aka a “spinner”, or whatever) If you want the app to let the user know that a time consuming process is about to start, add that chrome to the UI (e.g. So, with that in mind, if you are starting some process that takes a little time, you should: (You can disable the UI if your app requires that, but never block the main thread, regardless.) I want to know the precise moment at which the app is again able to process touch events in a responsive manner. knowing how different interactions affect hang time).įor example, a user taps a button and the app performs work.
Using MetricKit to watch for Hang Time is not an option as I cannot those results to a specific interaction (i.e. Is there any downside to this method? Is there any other method I could/should be using to do this? The sampling only occurs until the queue is again consistently responsive for some time again (ex. With this I would want data like "On average, the app becomes responsive 55ms after a user interaction".Ĭurrently, immediately after a user interaction, I watch the main queue and have a heuristic for submitting samples to it in order to estimate responsiveness based on the main queue's responsiveness, with the assumption that the main queue's responsiveness directly correlates with the apps' responsiveness. In hopes of using it as a performance metric, I want to know the precise moment at which the app is again able to process touch events in a responsive manner.
Is there a way to know when an iOS app becomes responsive to user interaction? For example, a user taps a button and the app performs work, this work may dispatch other work asynchronously to the main thread.
0 kommentar(er)
