SlideShare utilise les cookies pour améliorer les fonctionnalités et les performances, et également pour vous montrer des publicités pertinentes. Si vous continuez à naviguer sur ce site, vous acceptez l’utilisation de cookies. Consultez nos Conditions d’utilisation et notre Politique de confidentialité.
SlideShare utilise les cookies pour améliorer les fonctionnalités et les performances, et également pour vous montrer des publicités pertinentes. Si vous continuez à naviguer sur ce site, vous acceptez l’utilisation de cookies. Consultez notre Politique de confidentialité et nos Conditions d’utilisation pour en savoir plus.
After months of hard work your app is on the stores and is being downloaded by iOS and Android users alike. But what now? Are all users happy? Do your users only use your app once, or do they keep coming back? Does it crash all the time? Without decent analytics it is hard to know how well your app is doing, and this is where Visual Studio App Center can help.
App Center has a whole suite of crash and user analytics tools. You can use these to see if your app is crashing, and if so under what conditions and on what devices or operating systems. You can also see details of your user base, including how often they use your app or where in the world you are. App Center also provides push notifications that you can send to different groups of users to help drive user engagement.
In this session we will look at how to use App Center, starting with how to integrate the App Center SDK into a Xamarin app. We'll then see crash analytics in action, catching and fixing a real bug in our code. Next up we'll look at the user demographics of our app to see how it is being used.
Who has published an app to the store? What were you worried about after publishing?
Imagine this – your app is now on the App Store. Published on a Friday! Party, celebrate, champagne or sparkling grape juice opened, pizza eaten The next Monday – headache from the ‘music’ you get in Email from the boss…
One-star reviews as the app crashes. Client/product team are not happy No idea how to reproduce. Scramble to reproduce the crash from limited information in the reviews. Can you get a fix out quickly?
You create anew version and push to the store. Does this solve your issue?
Nope! Because Apple. 2 week delay on the release while they approve your app Story – EROAD apple approvals for the second version
Older Android installs have app updates off by default Users not updating.
People uninstall apps for all manner of reasons
71% uninstall due to annoying app notifications Freemium games do this a lot Facebook messenger
62% due to errors Pennybox as example – error so I uninstalled it Meme app - freeze Some will wait if good reason – Office Lens on iOS 12 beta crashed, kept it as useful and my fault for beta
16% will uninstall before registering if the process is bad 8 seconds to give up
If customers leave your app, they will pick a competitor if they want the product. This can mean moving business elsewhere – banks, energy Lloyds to Monzo – app is primary way to interact so if it is bad, move American airlines Analytics - should be tracking what I do
How can you stop people leaving your app? By learning what your customers do, the problems they face. Using this to make your app better
AppCenter! Lots of tools for this, I like AppCenter, been using it for 2.5 years now Using it and talking about it before MS Supports swift/java/Xamarin/react native/cordova, Unity, UWP Windows/macOS/iOS/Android
AppCenter does a lot – build, test, distribute, diagnostics, analytics, push – recently added auth and data We’re going to focus on diagnostics, analytics
You can capture a whole range of data Language – good to see if you need to localize Session durations – does it align with expectation? Micro-interactions or prolonged use Are users updating Paths through the app
Users in language x – translate Feature not used – ditch it or make it more visible/easier Prove value of feature - definition of done
Nice visualization of the concept Users follow their path, not what you intend Ohio state university waited to see mud paths from students walking then paved that path Maybe gather this data before restricting or guiding users?
Experiments – difficult to enter text, can see this by errors Add new feature, validate it using data Help – count pages used
App Center data can be fed to Application insights for further analysis Can bring it together with other data such as back end data User flow chart
Detect crashes – either ones that take the app down or internal ones that are handles Use this to fix the app
Show crash code, catch handled exceptions Demo crash on cancel photo
Where in the development cycle should you start
Right from the get go Catch issues in dev and QA
Everything you track needs to be GDPR compliant If any personal information is in there, you need to be able to tie it back to a person If they want their data, or want it deleted you have to do this AppCenter has APIs for this
Only gather the data you need to improve your product Nothing invasive, focus on trends on individuals If your app uses GPS (e.g. branch finder in bank app), don’t track their movements Don’t sell this data NYT story December last year – apps selling your location information