3.1 Desktop Environment alerts (beeps) mutes Spotify.Comments rated with one or two stars get pushed into one of our Slack channels, so we get sure that any weird issue is getting notified by our engineering and product team. We also use, a service that extract store comments and give you powerful tools to review them: grouping, auto-categorization, sentiment analysis, etc… Everyday, we read all store comments.
#DEEZER MEDIAKEYS WINDOWS#
As we didn’t have a great telemetry in place, we’ve relied on two tools to get feedback from our users: Windows Store ratings and comments, and a custom “send feedback” feature. When working on a mobile app, you really have unexpected issues like crash the app because of wifi in campings (true story). Handling feedback during (and after) preview We had such a great amount of candidate that we had to work with Microsoft to overcome the Windows Store limits around this feature. The feedback was tremendous: we’ve multiplied by 40 the number of beta registrants compared to our previous beta.
#DEEZER MEDIAKEYS FREE#
When they’ve started using the app, we were able to implement mandatory features for our free users. We chose this approach to let our paying subscribers be the first to test the app.
#DEEZER MEDIAKEYS DRIVER#
Since Microsoft announced a driver for Selenium-based tests, we can now run some sanity tests automatically. For example, at the beginning of the year, we had no options to run UI Automation tests for our UWP app. All these issues have been discussed with them, we just hoped for a sooner resolution. This story is not ended yet! We’re working closely with Microsoft engineering teams on a broad range of UWP development issues - including tooling, testing, deployment, framework, etc… - and they have great features coming soon.
![deezer mediakeys deezer mediakeys](http://routenote.com/blog/wp-content/uploads/2017/06/deezer-family-plan.png)
We didn’t tested it, as it does not yet support flighted submissions, but we’re looking forward to resolve this issue soon :) Since the writing of this article and it’s publication, Microsoft released a Visual Studio Team Services “Windows Store” extension. This is not the release process we had on our Windows Phone 8 app, and it’s sad to have a drawback on such basic development workflow step. Every package we submit has to be built on a developer machine. One year after our first line of code, there is still no way to build a package for store submission from our CI pipeline.
![deezer mediakeys deezer mediakeys](https://cdn.imgbin.com/13/2/5/imgbin-deezer-music-streaming-media-free-music-you-may-also-like-bv1XRi3xrLBSBScN8aV1kdeUd.jpg)
This come with huge drawbacks: you need a custom and on-premises build agent, and you can’t run your unit test in parallel. However, we lack tools around unit testing (like a mocking library/framework), and MS Test runner needs to be run in interactive mode. There are few unit test frameworks that integrate well with Visual Studio and the build pipeline. UWP tooling is not at a maturity level we expect to create great apps.įirst, the unit testing landscape is a little bit empty. Even after more than a year from their releases, UWP tooling is not at a maturity level we expect to create great apps. To be honest, this part of the story is a sad one. Our first commit on our Universal app repo, one year ago.