Tracking user interactions with a mobile UI to facilitate UI optimizations

1. A computer-implemented method for tracking user interactions with a mobile user interface (UI), the method comprising:

collecting data while a user interacts with the mobile UI through a touchscreen, wherein the collected data includes tap-attempt data that specifies coordinates for touchscreen locations that the user has tapped while interacting with the mobile UI;

examining the tap-attempt data to identify a cluster of tap attempts that are proximate to a non-tappable element in the mobile UI; and

when such a cluster is identified, notifying a UI designer about the cluster of tap attempts that are proximate to the non-tappable element, to enable the UI designer to make adjustments to the mobile UI;

wherein the collected data additionally includes swipe-attempt data that specifies coordinates for a “touch down” location and an associated “touch up” location for each swipe attempt, and wherein the method further comprises:

comparing the swipe-attempt data with locations of swipable elements in the mobile UI, wherein each swipable element has an associated swipe target size;

for each swipable element, using results of the comparison to determine a percentage of swipe attempts that have succeeded or failed for the associated swipe target size; and

making the percentage information available to the UI designer to enable the UI designer to adjust swipe target sizes for the mobile UI.

2. The computer-implemented method of claim 1 , further comprising:

changing an appearance of the non-tappable element to indicate that the non-tappable element is not tappable.

3. The computer-implemented method of claim 2 , wherein changing the appearance of the non-tappable element comprises at least one of the following:

changing a size of the non-tappable element; and

changing a color of the non-tappable element.

4. The computer-implemented method of claim 1 , further comprising:

making the non-tappable element tappable upon determining that there is a function that users are expecting the non-tappable element to activate.

5. The computer-implemented method of claim 1 , further comprising:

comparing the tap-attempt data with locations of tappable elements in the mobile UI, wherein each tappable element has an associated tap target size;

for each tappable element, using results of the comparison to determine a percentage of tap attempts that have succeeded or failed for the associated tap target size; and

making the percentage information available to the UI designer to enable the UI designer to adjust tap target sizes for the mobile UI.

6. The computer-implemented method of claim 5 , wherein comparing the tap-attempt data with the locations of the tappable elements includes:

associating tap attempts with proximate tappable elements in the mobile UI; and

for each tappable element, determining whether the associated tap attempts have succeeded or failed based on the tap target size for the tappable element.

7. The computer-implemented method of claim 1 , wherein the collected data additionally includes gesture data associated with other user gestures in addition to the tap-attempt data and the swipe-attempt data.

8. Apparatus that tracks user interactions with a mobile user interface (UI), the apparatus comprising:

one or more processors; and

memory storing instructions that, when executed by the one or more processors, cause the apparatus to:

collect data while a user interacts with the mobile UI through a touchscreen, wherein the collected data includes tap-attempt data that specifies coordinates for touchscreen locations that the user has tapped while interacting with the mobile UI;

examine the tap-attempt data to identify a cluster of tap attempts that are proximate to a non-tappable element in the mobile UI; and

when such a cluster is identified, notify a UI designer about the cluster of tap attempts that are proximate to the non-tappable element to enable the UI designer to make adjustments to the mobile UI;

wherein the collected data additionally includes swipe-attempt data that specifies coordinates for a “touch down” location and an associated “touch UP” location for each swipe attempt, and wherein the instructions further cause the apparatus to:

compare the swipe-attempt data with locations of swipable elements in the mobile UI, wherein each swipable element has an associated swipe target size;

for each swipable element, use results of the comparison to determine a percentage of swipe attempts that have succeeded or failed for the associated swipe target size; and

make the percentage information available to the UI designer to enable the UI designer to adjust swipe target sizes for the mobile UI.

9. The apparatus of claim 8 , wherein the instructions, when executed by the one or more processors, further cause the apparatus to:

change an appearance of the non-tappable element to indicate that the non-tappable element is not tappable.

10. The apparatus of claim 9 , wherein changing the appearance of the non-tappable element comprises at least one of the following:

changing a size of the non-tappable element; and

changing a color of the non-tappable element.

11. The apparatus of claim 8 , wherein the instructions, when executed by the one or more processors, further cause the apparatus to:

make the non-tappable element tappable upon determining that there is a function that users are expecting the non-tappable element to activate.

12. The apparatus of claim 8 , wherein the instructions, when executed by the one or more processors, further cause the apparatus to:

compare the tap-attempt data with locations of tappable elements in the mobile UI, wherein each tappable element has an associated tap target size, and

for each tappable element, use results of the comparison to determine a percentage of tap attempts that have succeeded or failed for the associated tap target size; and

display the percentage information to the UI designer to enable the UI designer to adjust tap target sizes for the mobile UI.

13. The apparatus of claim 8 , wherein while comparing the tap-attempt data with locations of tappable elements in the mobile UI, the instructions further cause the apparatus to:

associate tap attempts with proximate tappable elements in the mobile UI; and

for each tappable element, determine whether the associated tap attempts have succeeded or failed based on the tap target size for the tappable element.

14. The apparatus of claim 8 , wherein the collected data additionally includes gesture data associated with other user gestures in addition to the tap-attempt data and the swipe-attempt data.

15. A non-transitory computer-readable storage medium storing instructions that, when executed by a computing device cause the computing device to perform a method for tracking user interactions with a mobile user interface (UI), the method comprising:

collecting data while a user interacts with the mobile UI through a touchscreen, wherein the collected data includes tap-attempt data that specifies coordinates for touchscreen locations that the user has tapped while interacting with the mobile UI;

examining the tap-attempt data to identify a cluster of tap attempts that are proximate to a non-tappable element in the mobile UI; and

when such a cluster is identified, notifying a UI designer about the cluster of tap attempts that are proximate to the non-tappable element to enable the UI designer to make adjustments to the mobile UI;

wherein the collected data additionally includes swipe-attempt data that specifies coordinates for a “touch down” location and an associated “touch UP” location for each swipe attempt, and wherein the method further comprises:

comparing the swipe-attempt data with locations of swipable elements in the mobile UI, wherein each swipable element has an associated swipe target size;

for each swipable element, using results of the comparison to determine a percentage of swipe attempts that have succeeded or failed for the associated swipe target size; and

making the percentage information available to the UI designer to enable the UI designer to adjust swipe target sizes for the mobile UI.

16. The non-transitory computer-readable storage medium of claim 15 , wherein the method further comprises:

comparing the tap-attempt data with locations of tappable elements in the mobile UI, wherein each tappable element has an associated tap target size;

for each tappable element, using results of the comparison to determine a percentage of tap attempts that have succeeded or failed for the associated tap target size; and

making the percentage information available to the UI designer to enable the UI designer to adjust tap target sizes for the mobile UI.

17. The non-transitory computer-readable storage medium of claim 16 , wherein comparing the tap-attempt data with the locations of the tappable elements includes:

associating tap attempts with proximate tappable elements in the mobile UI; and

for each tappable element, determining whether the associated tap attempts have succeeded or failed based on the tap target size for the tappable element.