June does not have a way to calculate average time spent in app.
Understanding the Complexity
Calculating the average time a user spends in an app may seem straightforward, but it's a complex task due to the way user interactions are tracked. Consider the following sequence of events:
03:38 pm: Triggered identify, home_opened, reports_opened, and various other events.
03:39 pm: Triggered ran_prompt multiple times.
04:40 pm: Triggered home_opened.
Based on these timestamps, determining exactly when a user is still "in" the product is challenging.
The Challenge of Identifying Continuous Engagement
When analyzing the sequence of events, how can we definitively say that a user is still engaged with the product?
Is there a pause between actions that signifies the user has left, or are they still engaged but simply inactive for a brief moment?
These questions illustrate the difficulty in pinpointing the exact time between two events that would confirm a user is still engaged with the product. For this reason we prefer not to give an insight that might not be necessarily true.