Telerik blogs

Everyone in the mobile apps business needs real-time feedback about their app’s crashes. These have to be quickly fixed, so that you are not losing converted leads. Instead, these users need to be treated with the utmost attention. To get the feedback you have three ways to go:

1)    Use the error reporting procedure on App Hub, but you’ll have to wait for 3 to 4 days for the crash reports to be ready, which may result in losing some of  your users.
2)    Put some time and efforts and write the functionality yourself.
3)    Use Telerik ready-to-use Error Diagnostics control that allows the end-user to send real-time crash data. 

The 3rd option has two obvious advantages:

  • No time is wasted writing something that already exists.
  • The time lag issue that you face with the App Hub reports is solved.

Check out this short video:

Here are some details about the control. Implementing Telerik Error Diagnostic control in your Windows Phone app enables you to receive crash reports, get specific debug and run-time information from your end users when an issue (such as ApplicationUnhandledException) in your application is encountered. Whenever an exception occurs, a MessageBox dialog is displayed and users can send the report via e-mail. It will only take them a few seconds and you will get tons of data about the crash helping you to resolve the problem faster. Diagnostic data include: app version, app total runs, app runs after last update, device model, navigation stack and more. Optionally a screenshot of the current application state can be provided. Developers can also add custom data when an exception has occurred and to collect runtime logs. You may even send the data anonymously with the help of Web Services as detailed in this blog post. If you still need help in getting up to speed with Error Diagnostics, then you can watch our Q1 2012 webinar and check out the additional resources found here.

Apart from the automatic data which is provided out of the box developers can extend the component in two other ways:

  • Add their own custom data when the exception occurs (using the ExceptionOccured event). Read how
  • Add debug data in their application while it runs. When an exception occurs this debug data is sent along with the crash data. Read more

And the other good news is that it only takes three lines of code to implement the functionality in your app.

Telerik Error Diagnostics for Windows Phone can be downloaded as part of the RadControls for Windows Phone suite. Free trial is available here.

Share this blog post if you found it useful.


About the Author

Ina Tontcheva

(@pakostina) is a Product Marketing Manager at Telerik. She is a digital and mobile marketing explorer and works at Telerik with a focus on the native mobile UI family.

Comments

Comments are disabled in preview mode.