Streamlining the UX

[michaeleisel]

It may be helpful to reduce the number of launches and interactions to do each profiling. It also could be helpful to more closely match the Time Profiler UX for ease of migration. For example, what if we did ettrace --launch --bundle_id <bundle id> --device <optional device flag if multiple devices are applicable> ... and then ETTrace actually launched the app, perhaps with an environment variable set to initiate tracing? And then, upon exit, with an atexit handler or something (wouldn't work if the app gets killed with SIGKILL though) it writes out the data, which the ETTrace process collects? And likewise for measuring an in-progress app. The user could either terminate through exiting the app or, say, hitting ctrl-C on the ettrace process.

[noahsmartin]

So the proposed flow is:

• app is not launched
• run ettrace to launch app
• manually kill app to exit

That sounds like a good option to me, as long as bundle_id is also optional so the original behavior is preserved. Personally I find it more user friendly to not require the extra options and just let you select the app you want to profile by opening it on the device/simulator - but can see how some would prefer this so seems like a good addition