Skip to main content

Getting app feedback from windowsphone.com

I was chatting with my good friend Denis (@dhaman) about user feedback for the apps he's produced for the iPhone & droid app stores and just like the WP7 app store they all fall short in supporting your app once released out into the wild. I was also reading the final post in the '31 days of mango...' by @jeffblankenburg and he talks about promoting your app, he mentions the great work Nick (@spacescape) did originally for FINDaPAD in producing a template you can use to provide a bespoke site for WP7 app - Nick pushed this out to codeplex here.

Denis pointed out he started to explicitly put a feedback mechanism in the app blurb, ideally at the top. Initially I thought I don't need this, we've got http://findapad.biz with feedback via uservoice, but then I realised there isn't any way for a user viewing FINDaPAD in the app store to get in touch with us. This is a piece of functionality that should be in the app store and I don't mean a forum like feature to discuss the review\rating by a dissatisified user (1 star rating for FINDaPAD) I mean the ability to provide a contact point for any user to talk to you.

As you can see from the screenshot below they don't even provide anyway to show a support URL or email. I would have expected something down the left hand-side.


I don't really expect the app store to get a make over until Windows 8 platform is released (including to the phone). So what I am going to do to help us get better feedback in the mean time is put an explicit message in the blurb. Something like:

'We really want to hear from you, get in touch via feedback @ http://findapad.biz'

Now where this should be positioned is the difficult question, I'll try near the bottom at first and see what happens.






Comments

  1. Hey there - love that you're thinking about getting more customer feedback about your apps. We actually power feedback, directly within your app and would love to chat with you and your friend Denis about this problem. We're finding more and more developers saying things like you are and it'd be great to get your take on what we have and where we're going. You can find us at www.apptentive.com and connect with us via twitter (@apptentive) or just email me: robi [at] apptentive [.] com

    ReplyDelete

Post a Comment

Popular posts from this blog

WPF tips & tricks: Dispatcher thread performance

Not blogged for an age, and I received an email last week which provoked me back to life. It was a job spec for a WPF contract where they want help sorting out the performance of their app especially around grids and tabular data. I thought I'd shared some tips & tricks I've picked up along the way, these aren't probably going to solve any issues you might be having directly, but they might point you in the right direction when trying to find and resolve performance issues with a WPF app. First off, performance is something you shouldn't try and improve without evidence, and this means having evidence proving you've improved the performance - before & after metrics for example. Without this you're basically pissing into the wind, which can be fun from a developer point of view but bad for a project :) So, what do I mean by ' Dispatcher thread performance '? The 'dispatcher thread' or the 'UI thread' is probably the most

Showing a message box from a ViewModel in MVVM

I was doing a code review with a client last week for a WPF app using MVVM and they asked ' How can I show a message from the ViewModel? '. What follows is how I would (and have) solved the problem in the past. When I hear the words ' show a message... ' I instantly think you mean show a transient modal message box that requires the user input before continuing ' with something else ' - once the user has interacted with the message box it will disappear. The following solution only applies to this scenario. The first solution is the easiest but is very wrong from a separation perspective. It violates the ideas behind the Model-View-Controller pattern because it places View concerns inside the ViewModel - the ViewModel now knows about the type of the View and specifically it knows how to show a message box window: The second approach addresses this concern by introducing the idea of messaging\events between the ViewModel and the View. In the example below

Implementing a busy indicator using a visual overlay in MVVM

This is a technique we use at work to lock the UI whilst some long running process is happening - preventing the user clicking on stuff whilst it's retrieving or rendering data. Now we could have done this by launching a child dialog window but that feels rather out of date and clumsy, we wanted a more modern pattern similar to the way <div> overlays are done on the web. Imagine we have the following simple WPF app and when 'Click' is pressed a busy waiting overlay is shown for the duration entered into the text box. What I'm interested in here is not the actual UI element of the busy indicator but how I go about getting this to show & hide from when using MVVM. The actual UI elements are the standard Busy Indicator coming from the WPF Toolkit : The XAML behind this window is very simple, the important part is the ViewHost. As you can see the ViewHost uses a ContentPresenter element which is bound to the view model, IMainViewModel, it contains 3 child v