Bad stuff happens! There is no way around that. It’s a fact; your apps, out there in the wild on consumers devices, will crash. This in itself is ok but only if you can get the information about those crashes and use that information to fix the bugs that cause them. The Windows Phone platform actually captures stack traces and provides those to you, the publisher of the app. You can get a view of the number of crashes that are happening as well as download an Excel file with all the appropriate information and stack traces. This is a good thing and you should take advantage of that information as it may give you some good clues as to what to fix to make your app a higher quality product. There are a few things that App Hub does not give you though. The first thing is that it may not give you enough information about the bugs that you are hitting. One example of that is that the version number of the app is not provided so if you have published a few different versions of your app it is possible that a user is hitting a bug that you may have already fixed in a later version. The other issue is that stats on App Hub are delayed. As a result you don’t see the issues that your end-users are hitting for a few days. If something is happening out there that is causing a lot of crashes then you may not see it until after users start posting lots of low ratings and negative reviews. Another thing to keep in mind is that App Hub does not provide any sort of notification of issues. It’s up to you to visit App Hub regularly and pull down those stack traces to see what’s going on. Finally (and I realize this is more a perception thing than an issue) end-users have no idea that the platform is gathering up those stack traces and making them available to you. And, of course, they have no idea if you are looking at those traces and working on bug fixes. As a result, when they see a bug most will assume the worst and give bad ratings and reviews. As I’ve mentioned o

Misaligned elements is probably one of the most common issues I see with apps in the marketplace. In this episode of Top Ranked, I delve into why this is an issue and how easy it is to check for that and fix it. Alignment is a part of the overall Metro design language. I’ve even seen some designers in our UK COE group actually put post-it notes on their screens or on a device to verify that elements align properly. This acts as a sort of forcing mechanism for them to check alignment. The reason they do that is that you may not explicitly notice that stuff is out of alignment but when it is, you intuitively feel like something is off. In general your app will feel a little sloppy when the element alignment is out of kilter. The Metro design language does take alignment into account and as a result there are some things that you can keep in mind when designing and building pages. The magic number 12 seems to resonate throughout the experience. Most elements in the native apps align up in a grid of one form or another. The ingenious Jeff Wilcox built a development utility that makes getting the alignment right super simple. This utility is called MetroGridHelper is also simple to find since you can grab it with NuGet. Once included in your project you turn it on in App.xaml.cs in the same place where you turn on and off the frame rate counters and redraw regions etc. You simply add MetroGridHelper.IsVisible = true; in the if block where the profiling info is included. By doing it there you are assured that you will only ever see that grid when the debugger is actually attached (i.e. only in development). When you run your project with the MetroGridHelper turned on, you’ll see a series of red squares layered over every screen in the app. Those squares are strategically placed to make it really easy for you to see when elements are out of alignment. Another thing to keep in mind while we’re talking about element alignment is the amount of space you leave to

The About page is usually one of the last things you think about when building an app. It’s just not core to the whatever it is you’re trying to build. And yet you’ll soon find out that it’s pretty much a necessity for most apps. Not only is it something you can use to help build a better relationship with your users; it’s also something that can help you to fulfill some of the marketplace certification requirements. Having a place in your app that encourages the user to reach out to you and connect somehow is a very good thing. It could be used by them to send you an email to report a bug or a wish list item (before they use the app rating to express their frustrations) or it could be another place where you encourage end users to rate and review or actually buy your app. By communicating with users you will become more connected to them and your app’s ratings and reviews will tend to be more positive. The other area where the About page can be useful is in fulfilling some of the Marketplace Application Certification Requirements. One requirement in particular (5.6) states that your app must “include the application name, version information, and technical support contact information that are easily discoverable.” In the video, I show a very simple app that surfaces an about page as a manually created page providing information about the app and myself. Once you start thinking about what else you might include in the About page, manually maintaining that in code is probably not ideal. You can add all sorts of things e.g. rate and review the app, a buy link for users using a Trial app, legal terms of use, credit to others who may have helped you (like open source projects) or a development change log. As you can imagine this can start to get quite complicated and become a project in and of itself. Fortunately someone has already done some of the heavy lifting for you. Peter Kuhn aka Mister Goodcat has open sourced a project called Your Last About Dialog

In this episode, I focus on another small tweak that developers can add to their apps that will help make those apps look a lot more like native apps. I’m referring to the addition of the Tilt Effect to controls. By default, when you add controls to the canvas in Visual Studio or Expression Blend they do not get the tilt effect. This may seem like a small thing but as I’ve mentioned before the experience is something that users will notice and their ratings and as a result your rankings will be affected by that. The thing is, that there is, in fact, a really easy way to add the tilt effect to your apps using the Silverlight for Windows Phone Toolkit . You can grab the source code for that from Codeplex or, even easier, you can just pull it in to your project and reference it using Nuget. Adding the Tilt Effect is as simple as adding the namespace for the toolkit and then adding the effect to either the individual controls or to the entire page. In most cases it shouldn’t take you more than a few seconds on each of the pages in your project so there’s really no reason for you not to take advantage of this. Let me know what you think about this episode of Top Ranked. If you have questions about any of the videos, about problems or issues you’re hitting or if you have topics that you think would be of interest to other devs on the Windows Phone platform then drop me a note. I’d be particularly interested in hearing about some of the best practices you’ve adopted that you think have raised your quality or your ratings/ranking in the Marketplace. I’ll be sure to give full credit and link love whenever I can. The Top Ranked series is hosted on Channel 9. You can view all the past videos there. You can also subscribe to the entire series via Zune or iTunes. All that is available here: https://channel9.msdn.com/Series/Top-Ranked Let me know what you think by dropping me a note via the comment form below. Or better yet follow me on twitter and drop me a note there: htt

In this episode we talk about pricing and more generically about market testing. I know, I know, marketing is probably not every coders favorite subject. I bring it up as I’ve noticed many apps in the marketplace that are underpriced. Apps that are cool, differentiated or do something of great value to the consumer can clearly support higher price points. No user is ever going to ask you to charge them more for your app so the task of picking the right price point falls on you. The easiest way to do that is to do market testing aka A/B testing (or split testing, bucket testing etc). In this episode I refer specifically to price testing for paid apps but this technique could easily be used to test for other things that might increase revenue in paid apps or downloads in free apps. All sorts of things like categories, descriptions, keywords, or artwork can be affect the performance of your app and so could be optimized. As I mentioned above, from what I’ve seen in the marketplace many developers will underprice their apps. They seem to be optimizing for number of downloads. That is indeed what you want for free or ad-supported apps but for paid apps you probably want to optimize for revenue and that formula is a simple one everyone knows: revenue = paid downloads x price. If you optimize for downloads then likely you are in a race to the bottom; i.e. how fast you can get to the $0.99 price point. Since you have 2 variables to optimize and only one which you have any control over, the easiest way to optimize for revenue is to test different price points and watch the number of paid downloads at each point. Obviously if you want to maximize revenue then you want to get the highest price possible for your app. To do that start at a high price. Over time you may need to drop the price (e.g. for competitive reasons or for sales or promotional events). So the obvious question is: how do I do market testing on the Windows Phone marketplace? Since you canno

In this episode of Top Ranked I talk about Trial mode. Trial mode is one of the most important features available to you as a developer if you’re building a paid app. By implementing Trial mode in your app you give consumers the opportunity to take your app for a spin while ensuring that you’ll get paid for your hard work if a consumer sees value in it. We know from what we see on the back end that apps which include trial mode get 70x more downloads on average. Of those 70x more downloads about 10% will get converted into purchases so doing the math you can expect on average about 7x more sales just by doing the small amount of work required to include a trial capability into your app. We make it very easy for your app to know whether it is running in trial mode or if the consumer has purchased a license. What we cannot do is decide what trial mode means for your app. In fact, I would say probably the most important part of including trial mode is deciding how trial mode should work in your app. There are various scenarios that you could use. You might make the trial time-based (e.g. full functionality for 10 days), launch based (e.g. full functionality the first 10 times the app is launched on a device) or partial functionality (e.g. only the first 2 levels of a 30 level game are available in trial mode). You should be careful when allowing full functionality in a trial as a consumer could easily uninstall and re-install the app to completely reset the trial. When you provide full functionality you may want to consider storing the info about a user or a device in the cloud so that it persists across reinstalls. There is a performance cost related to checking for trial mode so you should be careful about how often you actually do the check. It’s a synchronous (blocking) operation that can take 60ms or more to complete. Note that you will not see this when in development as that 60ms penalty is not there then but you will see it when the app is published.

Note: This video is the first in the series so I spend some time at the beginning introducing myself and the goals for the series. To get directly to the content in this episode skip to about the 4:00 mark. When we launched the Windows Phone platform we released initially for the EFIGS (English, French, Italian, German and Spanish) markets. In all that was about 16 markets. With Mango we added a bunch more and just a few days ago we added another few. We’re now up to 41 markets where we as a developer can choose to make an app available. Since we cannot know what the rights are related to your app we cannot just publish to new markets as they come on-stream. In order for an app to made available in these new countries you will have to go into your App Hub account and cross-submit every time new markets come online. I was surprised at how many apps don’t do this. I suspect many developers don’t know that they have to do this. It’s such an easy thing to do that I thought I would do this as part of the first episode. It may be easy but if you stay on top of it you may find that you get a nice boost in downloads as new markets come online since you’ll be there first. Rather than try to describe what needs to be done go ahead and watch the video (topic starts at about the 4:00 mark). Let me know what you think about this episode of Top Ranked. If you have questions about the videos, or about problems or issues you’re hitting or if you have topics that you think would be of interest to other devs on the Windows Phone platform then drop me a note. I’d be particularly interested in hearing about some of the best practices you’ve adopted that you think have raised your quality or your ratings/ranking in the Marketplace. I’ll be sure to give full credit and link love whenever I can. You can drop me a note via the contact form on my blog here:https://blogs.msdn.com/b/benriga/contact.aspx Or better yet follow me on twitter and drop me a note there:https://twitter.co