GimmeSomeTune

gimmesometune

One 180 turn plus another 180 turn means – we’re back where we started.

A few months back, I said GimmeSomeTune would make a 180 turn by using Gracenote as its source of information (lyrics, song info, artwork).

Although I really wanted this to happen, for all the reasons I mentioned in that previous blog post, it doesn’t seem like it will happen. I’ve contacted Gracenote numerous times and never heard back. Either they’re very, very busy or they just don’t care and don’t want my business. So be it.

So be it!

I’ll do what lots of other apps (including GimmeSomeTune) do – turn to websites that have the according information available. I’ve done it before, I’ll do it again – only better. I’ll use several sources for lyrics and artwork, many of which you, the users, have suggested – thank you for that. I have several sources for lyrics and artwork, so if one service goes, there’ll be a backup service I can turn to.

Truth be told…

I really was looking forward to using Gracenote, because they do offer a great service.

When it became clear that Gracenote couldn’t be bothered to at least write me a “buzz off” e-Mail, I looked into other options. I still have no clue what Gracenote is charging, but it can’t be more than what the others are. It is really hard for an indie developer to use these services and not go hungry while doing so.

Who knows, maybe I’ll get an e-Mail from Gracenote some time this lifetime, then I may reconsider.

Status right now

So what’s the status of GimmeSomeTune right now?

Well, I lost a little time due to my work on Records (which is currently exclusively available through the MacBuzzer bundle) which had to be done for the bundle, so there’s that.

That being said, artwork, lyrics, last.fm and song recognition are all working right now, and beautifully, might I add. It’s almost magical.

Now you might ask, great, so when’s the release, because what’s there left to do?

Everything else. The interface, the popup window, keyboard shortcuts and testing, testing, testing (especially for song recognition, which is quite tricky).

One more thing on iPod last.fm scrobbling

In the blog post I mentioned before, I promised you last.fm scrobbling for tracks you played on your iPod. Turns out it’s not that easy to do.
I will try to implement it for the 1.0 release, but if it takes too long, I’ll move on to other things and get back to it when I’m working on a later update.
Sooner or later, it’ll be in there. But I don’t think it’s that important for a 1.0 release to spend a lot of time on it if I want a timely release (which I, and I assume most of you, do). I hope you understand.

 

As always, I’m open for suggestions and feedback, so please leave a comment, contact me on twitter (see below) or write me an e-Mail. Whichever you prefer is fine with me 🙂

Thank you for your time and interest,
Matthias

 

[twitter-follow screen_name=’eternalstorms’ show_count=’no’]
[twitter-follow screen_name=’gimmesometune’ show_count=’no’]

Read more

Dear reader, honored customer.

I’m sure you’ve noticed – the Mac App Store is upon us. Finally.

What a great idea, a great, comfortable way to purchase software (and to sell, for developers). I’m excited. I hope you are, too.

Now, you might have noticed that flickery, well, really none of my software, is on it, yet.

There is a good reason for it:
There’s this whole dilemma about not being able to transfer existing customers over to the Mac App Store. That is a big deal. And it’s confusing as well, because some apps show as “Installed” even though they were not purchased on the App Store. So people naturally assume they are able to update that version through the Mac App Store. That is, sadly, not the case.

Here’s what I’d like to do:
flickery is “close” to version 2.0. “Close” because it’s only close in version numbers (the current version is 1.9.2), not in execution/development.
I’m planning to go Mac App Store exclusive with flickery with version 2.0! 
Now there’s a caveat for existing customers. On my website, I currently promise that users who purchase flickery get a discount on version 2.0. With the Mac App Store, I can not keep that promise, because it doesn’t have an “upgrade” model.

So I’d like to put it in my customers hands:
Would you be offended if I moved to the Mac App Store exclusively and you and didn’t get that discount for version 2.0 of flickery? Please leave a message in the comments, mail me, tweet me or write me on facebook to let me know what you think. I will decide by majority of votes.

New software by me will be exclusive to the Mac App Store as well (new software as in the upcoming rewrite of GimmeSomeTune, ProjectX and ProjectiX.)

What’s the difference for the user?

  • Keep informed on updates
  • A centralized place for your software
  • Easy updating and installing
  • They have to have OS X 10.6.6 at least to run software
  • The security that they get quality software
  • A ton of other things I’m probably not thinking of right now

What’s the difference for the developer?

  • Having to maintain only one version of their software
  • This is a very big deal, because time is precious and better spent on new features / new software.
  • Centralized updates – yes, it’s also a plus for the developer
  • Higher visibility to the user

To summarize:
I’d like to go Mac App Store exclusive with all my software. Starting with flickery 2.0 when it is available (quite a couple of months off – and there surely will be other updates before that which will not appear on the Mac App Store but through the current updating mechanism). To do that, I’d have to break my promise to give the existing customers a discount on the upgrade.

Future software not yet released will appear on the Mac App Store exclusively, as well. That means that all my software will require Mac OS X Snow Leopard 10.6.6 at the least. So, please let me know what you think about that in the comments, by mail, twitter or facebook.

I hope I’ve covered about all of what’s important in this regard.

Thank you for your time,

Sincerely,
Matthias

[twitter-follow screen_name=’eternalstorms’ show_count=’yes’]

Read more