科技回声

Showing the CPU+Battery utilization graph for a sample app is a pretty dubious way to demonstrate the performance impacts of swizzling sendAction:to:from:forEvent:<p>It may indeed be a negligible impact as they claim, but using the Time Profiler instrument they could show exactly how much time is spent in the main queue on their swizzled code which would be a much better indication of whether or not the performance impact is negligible than eyeballing a cpu utilization graph.

Swizzling? Why not just override the event method in a class derived from UIApplication? That's what I do if I want to see all user events, works just fine.

That's even better of use heap than for web pages. Usually for any web development it's so much easier/faster to deploy new version than release new version of mobile application.

My concern are the costs. If you track by visits, even trivial apps will need to pay $500/month.

I would like to know specifically how impactful method swizzling is on performance. I understand it's "negligible" but what does that mean exactly? Nonetheless, I like what you guys are doing; Heap's approach to analytics its pretty clever.

Is there an advantage to method swizzling instead of just subclassing UIApplication?

Swizzling? Why not just override the event method in a class derived from UIApplication? That's what I do if I want to see all user events, works just fine.

That's even better of use heap than for web pages. Usually for any web development it's so much easier/faster to deploy new version than release new version of mobile application.

My concern are the costs. If you track by visits, even trivial apps will need to pay $500/month.

Is there an advantage to method swizzling instead of just subclassing UIApplication?

Building Automated Analytics Logging for iOS Apps

6 条评论

Building Automated Analytics Logging for iOS Apps

6 条评论