Automatic transactions based on user interactions

[bruno-garcia]

More context in the UI Event Transactions issue tracking Android and iOS: getsentry/team-mobile#4

• Get the idleTimeout support in .NET (Support transaction finishing automatically with 'idle timeout' sentry-dotnet#1074)
• Build on the original/old Input System to start transactions
• Build on the new Input System to start transactions

Potential targets for automated spans:

• Instances of Instantiate
• Loading of AssetBundles

[bitsandfoxes]

Alternatively, instead of Idle Transactions we could work strictly within frames. We'd have to assume that the action behind the button press is running synchronously.
Alternatively, we could cover or present this with the slow/frozen frames concept we have on other mobile platforms.

[bruno-garcia]

Alternatively, instead of Idle Transactions we could work strictly within frames.

Meaning have a transaction last 1 frame?

We'd have to assume that the action behind the button press is running synchronously.

Async stuff is very common though, any I/O will be done async and hence not connected to the user action

Alternatively, we could cover or present this with the slow/frozen frames concept we have on other mobile platforms.

Slow and Frozen frames are great but we rely on capturing "some frames" through transactions, at least for now.