Microsoft Clarity Flutter SDK - iOS: Eventing Assessment

Microsoft Clarity Flutter SDK - iOS: Eventing Assessment Aaron Gregory, Principal Technical Product Manager

Overview: This assessment evaluates the usability of the Clarity Flutter SDK session data for creating smart events. Specifically, it calculates the percentage of eventable key performance indicators (KPIs) in a defined user flow. By measuring how well Clarity can event on critical KPIs, we can identify gaps and make data-driven decisions for improvement.

Microsoft Clarity Flutter SDK – iOS: Eventing Assessment

2

Key Objectives:  Measure usability to assess how complete the product feature is,

based on the percentage of key KPIs captured for smart events.  Use the completion percentage to inform resource allocation decisions.  Align findings with the product release timeline to ensure full functionality.

Microsoft Clarity Flutter SDK – iOS: Eventing Assessment

3

Eventing Usability Criteria:  Find eventable data for each key performance indicator (KPI) in a

defined flow.  A KPI is the screen name or the identifier of the control the user has interacted with.  Each KPI must occur in order and the correct number of times.  Gestures must be the correct type and associated with the proper screen.  Future assessments will include the smart event creation process.

Microsoft Clarity Flutter SDK – iOS: Eventing Assessment

4

Eventing Usability Calculation: Eventable KPIs / Total KPIs = Eventing Usability %

Microsoft Clarity Flutter SDK – iOS: Eventing Assessment

5

Eventing Usability KPIs – Checkout Flow: Step KPI – Screen or Control Name

Result

1. Viewed “Login” screen.

2. Tapped “LOGIN” button.

3. Viewed “Categories” screen.

4. Tapped “Add to Cart” button.

5. Tapped “View Cart” button.

6. Viewed “Shopping Cart” screen.

7. Tapped “Checkout” button.

8. Viewed “Shipping” screen.

9. Tapped “Confirm Shipping” button.

10. Viewed “Payment” screen.

11. Tapped “Place Order” button.

12. Viewed “Order Confirmation” screen.

Eventing Usability --% Microsoft Clarity Flutter SDK – iOS: Eventing Assessment

6

1. Viewed “Login” screen.

Microsoft Clarity Flutter SDK – iOS: Eventing Assessment

✓

7

2. Tapped “LOGIN” button.

Microsoft Clarity Flutter SDK – iOS: Eventing Assessment

✓

8

3. Viewed “Categories” screen.

Microsoft Clarity Flutter SDK – iOS: Eventing Assessment

✓

9

4. Tapped “Add to Cart” button.

Microsoft Clarity Flutter SDK – iOS: Eventing Assessment

10

5. Tapped “View Cart” button.

Microsoft Clarity Flutter SDK – iOS: Eventing Assessment

11

6. Viewed “Shopping Cart” screen.

Microsoft Clarity Flutter SDK – iOS: Eventing Assessment

✓

12

7. Tapped “Checkout” button.

Microsoft Clarity Flutter SDK – iOS: Eventing Assessment

✓

13

8. Viewed “Shipping” screen.

Microsoft Clarity Flutter SDK – iOS: Eventing Assessment

✓

14

9. Tapped “Confirm Shipping” button.

Microsoft Clarity Flutter SDK – iOS: Eventing Assessment

✓

15

10. Viewed “Payment” screen.

Microsoft Clarity Flutter SDK – iOS: Eventing Assessment

✓

16

11. Tapped “Place Order” button.

Microsoft Clarity Flutter SDK – iOS: Eventing Assessment

✓

17

12. Viewed “Order Confirmation” screen.

Microsoft Clarity Flutter SDK – iOS: Eventing Assessment

✓

18

Eventing Usability KPIs – Checkout Flow: Step KPI – Screen or Control Name

Result

1. Viewed “Login” screen.

✓

2. Tapped “LOGIN” button.

✓

3. Viewed “Categories” screen.

✓

4. Tapped “Add to Cart” button.

5. Tapped “View Cart” button.

6. Viewed “Shopping Cart” screen.

✓

7. Tapped “Checkout” button.

✓

8. Viewed “Shipping” screen.

✓

9. Tapped “Confirm Shipping” button.

✓

10. Viewed “Payment” screen.

✓

11. Tapped “Place Order” button.

✓

12. Viewed “Order Confirmation” screen.

✓

Eventing Usability 83% Microsoft Clarity Flutter SDK – iOS: Eventing Assessment

19

Findings:  Most interactions are not usable for smart events.

 Only buttons with visible text have enough data to be used for smart

events.  All interactions are reported as taps.  Gaps exist in funnels due to lack of screen or gesture context.  Enhancements are needed to allow reliable event-based analytics and KPI tracking.  Unable to track form field completion.  Apps that use graphical UI elements without text will not be able to fully leverage smart event capabilities.

Microsoft Clarity Flutter SDK – iOS: Eventing Assessment

20

Recommendations:  Add support for identifying controls using accessibility identifiers (accessibility

id, label, and hint).  Leverage Flutter's Semantics widget to apply descriptive labels.  Encourage developers to assign unique semantics labels to key interactive elements.  Promote consistent use of accessibility labels across iOS and Android.  Reference best practices such as W3C Mobile Accessibility and Flutter Semantics documentation.

Microsoft Clarity Flutter SDK – iOS: Eventing Assessment

21

Next Steps:  Re-test eventing usability with updated SDK with semantics accessibility

features.  Develop proof-of-concept smart events using enhanced SDK features.  Share implementation feedback with Clarity team.  Evaluate cross-platform consistency (iOS vs. Android) and prepare parallel assessment.

Microsoft Clarity Flutter SDK – iOS: Eventing Assessment

22

References:  W3C Mobile Accessibility:

https://www.w3.org/WAI/standards-guidelines/mobile/  Flutter Semantics Documentation: https://api.flutter.dev/flutter/widgets/Semantics-class.html  Implementing Semantics in Flutter: https://www.geeksforgeeks.org/flutter/semantics-flutter/  Flutter Session Recording: https://clarity.microsoft.com/shared/recording/55d68a47-0908-4b19-bffaf567795754ae

Microsoft Clarity Flutter SDK – iOS: Eventing Assessment

23

Thank you.

Aaron Gregory Principal Technical Product Manager Houston, TX (US Central Time) Aaron@Gregory.bz +1.305.509.9280

Microsoft Clarity Flutter SDK – iOS: Eventing Assessment

24