Results of Spaz webOS Pricing Survey

Smell the Money

Yesterday I put together a short survey that asked some questions about what people would be willing to pay for Spaz webOS. It’s been my plan all long to change a small fee (when possible — you can’t yet in the Palm App Catalog) for Spaz webOS, and use the revenue to support further development. Since I believe strongly that Spaz must be an open, transparent project, here are the results so far from 145 responses:

…and here are some comments on the results:

What is the most you would pay to purchase Spaz in the Palm App Catalog?

From doing a little math on this, it seems like $2 is the optimal price point in terms of revenue generation, followed closely by $3.

What 1-3 features would make you more likely to purchase Spaz in the app catalog?

First off, lots of people ignored the request to pick 1-3, which isn’t surprising (you couldn’t set a max number of choices). That being said, 4 items were far and away the most popular choices

  1. Faster Performance (56%)
    Spaz does seem to perform slower than comparable apps. Part of this is because we use a combined timeline, and therefore it takes longer to build results. We also initially requested a LOT more messages from Twitter at startup than comparable apps, and processing them takes more time. We’ve lowered the default numbers (you can up them in prefs), but it’s still higher.

    We’ve also had some CPU usage issues. Those have been dramatically lowered since initial release, but there’s probably more we can do. This shows up especially while processing new messages.

    The other issue I think this response refers to is sluggish scrolling speed. This one perplexes me a bit, but I’m guessing we may be running into performance limits of the Pre’s webkit renderer. We’re going to do some experiments with stripping out CSS styling and markup on our timelines to see if the scroll speed improves in either case. If so, we will need to modify how we style and/or build the markup for our timeline.

  2. Direct uploading to image hosting services like Twitpic (54%)
    This was really close to #1, which tells you how badly the lack of direct file upload APIs in webOS is hurting devs. What’s most frustrating is that the email-based workarounds actually took longer to implement than direct uploads would — we already have plenty of code from the desktop app we could have adapted. Here’s another plead to Palm to please expose the file upload APIs to 3rd-party developers ASAP!

  3. New message notifications even if the app is closed (42%)
    I’ve heard this a lot. I kind of assumed people would just leave an app open if they wanted it still running, but how I use things isn’t necessarily how others will. One consequence of implementing this will be reduced battery life, so we will need to be careful about it. Note that Palm recommends not doing background network requests more than 15min per hour. We won’t exceed that if and when we do implement this.

  4. Facebook support
    This one kinda surprised me. I only added it as a bit of an afterthought, but I suppose it makes sense, especially since there’s not a good native Facebook app for the Pre. I actually know very little about the Facebook API and am not super duper excited about building for their walled garden, but if someone wants to build a SpazCore lib for it, we’ll probably implement something.

Also of note were some of the “Other” responses. They included:

  • “More optimized code (use less cpu!)”
    This falls under Faster perf, fo sho.

  • “tweet with google maps link to current location”
    This is on the list to get implemented

  • “hit user pic in timeline to @reply”
    We’re going to implement something that lets you do actions on a message without going to the detail view. Kinda sucks right now.

  • “low power consumption”
    The way you do that is to make fewer network requests. This responder will not want background checking, then 8)

  • “more identica/laconica support”
    I’d like to see this happen too. If you want it to happen, volunteering to code a Laconica-specific API (or somehow scraping up funding to sponsor development) would help us out a lot. We don’t have time to do much with non-Twitter APIs right now.

  • “Livejournal support”
    Seems like a microblogging client isn’t a good match for this, but if we add ping.fm support, you should be able to post to LJ through that. As for reading LJ posts, I think RSS feed support would allow that.

  • “It needs a non-offensive name before I would purchase it anywhere”
    We had to get one of these, although I’m surprised we only got one in nearly 150 responses. It’s not changing. Read the FAQ. Sorry!

  • “Since last 2 updates it really drains my battery. LOVE it’s look and feel though.”
    These are the kinds of things we need to get reported to us. Can’t fix it if you don’t report it. Go to our support site and file an issue, please. Please make sure Spaz is the only culprit involved, though.

  • “Direct blip.fm support (streaming via clicking a link)”
    That would be interesting. If someone’s willing to look into it dev-wise, I have no issue with it.

  • “Why? When tweed is free. And there’s more twitter apps to come.”
    No applications are allowed to charge for apps at the moment. That will change in the future, though. I wouldn’t assume Tweed will remain free, but I have no idea what their plans are.

  • “Copy and paste”
    Talk to Palm, dude. 8)

  • “Change the name!!!”
    Okay, maybe we got another one, but this didn’t claim I was making fun of physically or mentally disabled people. Sorry, not changing.

  • “None”
    This surprised me a little. You could have written “shits money and cleans my house.” Surely that would make you more likely to buy it, yes?

  • Javi
    http://javierdimauro.com
    08/05/2009 09:36:31 AM

    App stores should support free apps receive donations. That’s the most reasonable way, IMO.

    “This app is free software. You can download it for free, but you can also make a donation for the project”

    And, in the second case, let the users choose how much they want to pay for the app.

  • funkatron
    http://funkatron.com
    08/05/2009 09:55:23 AM

    It would be great, but my experience has been that you’re better off charging a $1-2 than asking for donations, as almost no one donates. ever.

  • Seth
    08/13/2009 11:30:37 AM

    I know that I’m unusual about this but I would pay as much as $9.99 if the app was good enough. I’m a previous Symbian user and I purchased “Gravity” for my Nokia 5800. It was expensive- but the app was very capable.

    Realistically, your app should probably be $1.99-2.99

  • Jim Whitaker
    08/14/2009 09:33:37 AM

    Personally I get the impression that most of the folks you survayed about priceing arnt prevouse “Palm” users. Paying $100 for a good app in pretty much the rule, if I can get it for $5 I wont know how to act ;-)

  • ssrjazz
    09/04/2009 03:16:50 PM

    re: LJ support.

    RSS works only for non-private entries. A LJ client that could authenticate and get private friends entries too would rock.

  • Philippe Gamache
    http://www.ph-il.ca
    10/24/2009 11:35:53 PM

    identi.ca, Laconi.ca, status.net have a twitter compatible API… So this is not a real reason.

  • funkatron
    http://funkatron.com
    10/24/2009 11:56:01 PM

    Actually it is, Philippe.

    Spaz on webOS already is usable with any system that has a Twitter-compatible API, including StatusNet. I interpret “more identica/laconica support” as meaning support for StatusNet-specific features. The Twitter-compatible API does not expose these features, so a StatusNet-specific library would need to be created.

    Would you like to work on this, Philippe?