I have decided to move my Apps to using AskingPoint as my rating widget. Although it does not appear to be a major player in the market, it does seem to be feature rich and its pricing structure will work out very well for my anticipated usage.
Here are my important requirements:
Leave me any comments on your experiences below.
From the requirements above, AskingPoint seems far better than any alternatives I have seen. Now the only question is can it perform. My results so far:
- Signup: Their website was a bit confusing on sign up. The Account->User Info page where you sign up from, does not show what Plan you have. And the confirmation of sign up was unclear. Thus, I did not realize that I had successfully signed up. I emailed them regarding this and got a quick and satisfactory response for my needs. But, I'm not sure they heard me that they need to show the user plan on the User Info page.
- Basic Setup: The basic setup and usage is Very Easy. As I mentioned above, I have customized because I want some very specific behavior. I think in the end, to get everything just like I want will take some real time, but initial feeling is that AskingPoint has most of what I need. The downside (for any tool) is that my investment of time will be lost if I run into or decide I'd rather use something else. At this point, I'm very happy with my choice of AskingPoint.
- Features: It has a rich set of built in analytic features you'd expect and a decent way to view them online.
- Ratings: I do not yet have enough data to comment on how well this will work for me, but as I said above, it has the controls I need. Initial results show that I will get the data that I need to evaluate the results. I also look forward to the "Custom Rating Booster Look" that they are advertising.
- Email Feedback: Unhappy users are moved to give email feedback rather than rate your app. This is good, but I'd really rather allow them to email from my app and have it come directly to my support inbox rather than go through AskingPoint. There may be a way to customize this behavior as there are lots of hooks, but I was not able to figure out any solution so far. I hope that someone will tell me how and I have not yet talked with their support about this.
- User Data: The ability to collect custom user data is good, but the AskingPoint implementation is pretty slim. It seems to primarily be focused on collecting broad groups events about your users like, how many users used GameFeatureA. In MySongbook app, I would like to understand the distribution of users and the number of Songs and Sets they have. I could either group them internally and setup custom events, but really want to do this externally. I kinda get this from the UI, but will need to download and massage the data and it appears some of the correlation (SongCount to SetCount) will not be available. I have a work-around that I'll implement in a future release.
- Issues Seen: I have seen one issue where the SDK prevented some code from working. The existing code called a method on the AppDelegate using performSelector:withObject:afterDelay. Although this code was in multiple places, with the AskingPoint SDK installed, which seems to insert a proxy AppDelegate, it failed from a popover view controller. -[ASKPManager sendEmail]: unrecognized selector sent to instance Worked around by using dispatch_after(). Unsure why this happens and different mutations could not fix. This is very disturbing, but not a show stopper by itself.
Overall, I'm pleased with my AskingPoint choice. I'll update this review as I learn more.