Shake Report: Overview and Usage

A "shake report" in an app refers to a feature that allows users to report issues or provide feedback by physically shaking their device. This action triggers a reporting mechanism that often includes automatic data capture, such as screenshots, logs, or other context-specific details about the app's current state. Shake reports are especially useful for quickly and seamlessly gathering user feedback or debugging information without requiring the user to navigate through complex menus.

In this article you will learn:

• How to create a Shake Report

• Why are the Shake Reports useful

• What are the most common mistakes in creating Shake Report

How to Create a Shake Report

1. Initiating the Shake Report

Users can simply shake their device to initiate the process, making it accessible and straightforward. Once the device detects the shake action, a message will appear on the screen stating: 

iOS: "Shake action detected. If you would like to continue with creating the shake report, press Confirm. Otherwise, you can press Cancel and proceed with normal usage of the application."

Android:  When submitting a shake report for the first time  on Andorid devices, the following message will appear:  "You have discovered quick issue report. If you would like to continue with creating the shake report, press Enter. Otherwise, you can press Cancel and proceed with normal usage of the application."

Once this is confirmed this message will not appear anymore. When shaking the phone the following message will appear on the screen:" Shake action detected. If you would like to continue with creating the shake report, press "Yes". Otherwise, you can press "No" and proceed with normal usage of the application."

2. Confirming and Providing Details

iOS: If you press Confirm, you will be redirected to the quick issue report page, which includes the following sections:

• Issue Type: Choose the type of issue you are reporting from the dropdown options:

  • Crash

  • Sync Issues (missing or incorrect data)

  • Unexpected Behavior (missing elements, buttons not working)

  • Other

Android:

If you press Yes, you will be redirected to the quick issue report page, which includes the following sections:

• Issue (Select a reason): Choose the type of issue you are reporting from the dropdown options:

  • Crash

  • Sync Issues (missing or incorrect data)

  • Unexpected Behavior (missing elements, buttons not working)

  • Other

• Description: Provide detailed information about the issue you are experiencing. For example: "I am trying to enter space consumption, but the confirm button does not work."

This ensures the support team understands the issue, where it occurred, and who it affects.

• Screenshot: The screen where the shake action occurred will be displayed, allowing you to verify if the report corresponds to the correct issue and location.

3. Submitting the Shake Report

Once you have completed the required fields:

iOS:

1. Press the small arrow icon in the upper right corner to submit the shake report.

2. Your report will be successfully created and sent directly to the support team.

Android: 

1. Press "send" to submit the shake report.

2. Your report will be successfully created and sent directly to the support team.

After submission, you can continue using the app for other daily operations.

Why Are Shake Reports Useful?

Shake reports offer several advantages, including:

1. Automatic Context Capture: The app gathers relevant data such as logs, screenshots, and user activity leading up to the issue, reducing the need for users to manually provide technical details.

2. Streamlined Debugging: Developers receive all the necessary backend information, enabling faster identification and resolution of issues.

3. Immediate Support Integration: Shake reports link directly to customer support, ensuring immediate visibility and action.

Common Mistakes When Creating Shake Reports

To ensure your shake report is accurate and actionable, avoid these common pitfalls:

1. Poor Descriptions:

   • Avoid vague or incomplete descriptions.

   • Provide clear, specific details about what happened, where, and when.

2. Incorrect Screen:

   • Ensure the shake report is created on the screen where the issue occurred.

   • Reporting from the wrong screen can lead to confusion and delays in resolving the issue.

By following these guideliness, you can helo the support team adress your concernc efficiently and effectively.