Skip to Content

Interview: Growl's project lead on coming to the Mac App Store

After the news yesterday that the popular notification service Growl was officially coming to the Mac App Store with the release of OS X Lion, TUAW tracked down Project Lead Christopher Forsythe and had a quick conversation about the reasons behind the decision and the future of Growl in general. Forsythe says that the change to the Mac App Store has been discussed "amongst ourselves for probably about two or three months now," and that using Apple's official store "just makes sense."

Perhaps the biggest piece of news we learned from Forsythe is that in the Mac App Store, for the first time since its creation seven years ago, Growl will not be free. Devs working on the project are "still talking" about the final price, but "it most likely will be a dollar or two dollars at most," according to Forsythe. Some may turn up their noses at paying anything for the results of an open source project, but Forsythe says the reasoning behind the charge is simple: "I'm a grown adult," he says, "and my wife wonders why I spend time working on my open source project and not with my two-month old." For all the work Forsythe and his fellow devs have put into Growl, a few bucks seems little to ask.

Money is also involved in the other main reason the team wants to move to the Mac App Store. If nothing else, they're offloading the issue of actual distribution to Apple. "We don't have to worry about supporting a download infrastructure any more," says Forsythe, "and that's huge for us." Currently, bandwidth for distributing Growl is all handed by CacheFly pro bono, but Forsthye has seen huge charges covered by them in the past, and the one time the project switched to Google Code, Forsythe says all of Google's bandwidth was eaten up in "a couple of hours, a very short period of time."

Yesterday, we heard that some of the more technical Growl services would be dying off because of the switchover, but Forsythe says that's not exactly true. While perception has it that the Mac App Store is ruling out a few Growl services, many of the changes are just so he can focus his team on what customers actually use, and not as much on edge use cases. Services like GrowlMail and GrowlSafari won't be officially supported in the Mac App Store version, but anyone who wants to use those services will still be able to download a PKG installer from the Growl website and be off on their merry way. That's good news for average users like myself and others. Forsythe plans to put his team working on the core Growl app, and let other developers deal with the more complicated function and addons.

As for developers of apps that hook into Growl, Forsythe says it's pretty simple: if anyone currently uses the Growl with Installer framework (which allows third-party apps to actually install Growl if users don't have it), they'll have to switch over to the one standard framework the app will be using. The Growl team has had a lot of complaints from users who believe Growl is spyware because a developer uses it to post less-than-helpful notifications ("It's really annoying," he says), so the new Growl framework won't actually install the whole app.

The way it will work is that in the new framework, developers who want to use Growl without having it on the user's system will get a simplified version of the notification to run, with just one style in just one place on the screen. "So if the user doesn't have Growl installed," says Forsythe, "they can use Smoke notification in the top corner. If the end user wants to configure that, they'll need to install Growl." That seems like a good balance; it allows devs to take advantage of Growl and its basic function, then send customers on to the full app if they want more features out of it.

Finally, Forsythe says that revamping the code like this is giving his team an opportunity to really focus on what they want Growl to be going forward. While the average user won't "miss anything," according to Forsythe, it's true that some services will need to be worked on outside the official Growl team. "If [a service] takes up the same amount of resources it takes to put a cool feature into Growl itself, I'd rather we put the work into Growl itself." That work means we'll see updates to the core app, like a new feature called RollUp that will help get rid of what Forsythe calls "screen spam." Instead of having your screen fill with a bunch of notifications, you'll get just one note after a while that will then expand out into a log of notifications you may have missed.

That sounds great, and hopefully we'll see more helpful features like that going forward. Growl has been a solid addition to the Mac lineup throughout its history, and it's exciting to see the open source effort join Apple's official store. There will undoubtedly be some growing pains, but in general, this seems like an excellent move for Growl, and it should be a nice app to add to the Mac App Store's offerings.



Categories

Developer Mac OS X

After the news yesterday that the popular notification service Growl was officially coming to the Mac App Store with the release of OS...
 

Add a Comment

*0 / 3000 Character Maximum Comment Moderation Enabled. Your comment will appear after it is cleared by an editor.

45 Comments

Filter by:
firesign3000

I love Growl. I will gladly pay a couple of bucks for it.

July 13 2011 at 12:30 PM Report abuse rate up rate down Reply
Rob

Countdown until Apple buys Growl or comes up with their own OS X notifications... 10... 9...

July 12 2011 at 5:23 PM Report abuse rate up rate down Reply
Rick A

I got Growl when I adopted Dropbox. I had to turn off the notifications because they were extremely annoying and in the way.

It's still running, but what is it doing?

July 12 2011 at 11:54 AM Report abuse rate up rate down Reply
1 reply to Rick A's comment
Christopher Forsythe

Go here we have a page about Dropbox and others doing this:

http://growl.info/thirdpartyinstallations.php

Chris

July 13 2011 at 6:47 PM Report abuse rate up rate down Reply
Roy Andrew

Standard practice these days. Make free software/service. Once it gets popular, charge them for it. :) Can't blame Chris when everybody else is doing it.

July 10 2011 at 4:03 PM Report abuse rate up rate down Reply
bob

I'll pay, i'll skip a soda and use the money for something that I use every single day.

I've already moved from QuickSilver to Alfred (with the powerpack) and have donated to other apps that I frequently use.

It would be cool if the developers make enough to get the latest/greatest mac or throw some bucks towards other bills that we all have.

I think that the people who won't pay aren't bringing much to the project anyway.

Good luck with the app,
bob

I will miss the prefPane though.

July 10 2011 at 12:24 AM Report abuse -1 rate up rate down Reply
jwa

here is my take-away.
1) cost a couple dollars
- I can afford it, I may not be thrilled about it. call me cheap but fine i'ld still pay if this were the only change, I don't mind supporting other developers for useful tools. (though I prefer the free ones ;-) )
- I can see this hurting adoption and continued bundling with apps. Speaking as a software developer, it will be much less attractive to use this framework since it means that I would be either using a gimped version in my or would be including/endorsing a hidden extra cost for my users. It will certainly make any developer who is making free software think twice to have their work driving business to a paid library. We can definitely assume that google chrome will never ever have a growl option now (it was originally a contender for their desktop notifications on mac before they decided to write their own, primarily to have consistent linux/win/mac behavior).
2) convert from prefpane to app
- I just plane hate this and may just not buy/upgrade for this reason alone. It may be a silly distinction but I want my infrequently altered, system-wide preferences for headless frameworks to be centralized in my System Preferences.app and I want to minimize my Applications folder.

Honestly the sole benefits for end user (IMO) seams to be that updates can be delivered via the app store, and that I can one-click install it on other *authorized* macs.
I'm just not hearing anything that is making me excited, and I really think 1.b could lead to diminished usage of Growl as a whole.

July 08 2011 at 9:01 PM Report abuse +1 rate up rate down Reply
1 reply to jwa's comment
Christopher Forsythe

Actually, there are other benefits as a developer:

1) You still don't have to build your own notification window. The 1.3 framework will provide one which doesn't require Growl, for free. End users are not required to have Growl for them to get notifications from your app. They are to configure them more than just a basic on/off.

2) You don't have to tell users to "just trust me, growl is cool". Apple will vet Growl.

3) We're trying to motivate more people to work on Growl, just the same as SoC motivates more people to work on OSS partly by a cash payment. I don't see how this is different.

There's more than that. I think you're just overlooking some things.

Chris

July 09 2011 at 11:20 PM Report abuse +1 rate up rate down Reply
Jasoco

I'll gladly buy it. I've used Growl for years, it's indispensable.

July 08 2011 at 5:42 PM Report abuse +1 rate up rate down Reply
nznordi

Hi there,

with the move to Mac App Store, will Growl remain a preference pane? I find that a brilliant architecture for these system wide extensions (Perian, Growl, TextExpander etc...) but the latter has already moved away from it and a search in Mac App Store for pref pane yields no results. Is that type of app not supported?

I just think pref panes are such a neat way for these types of apps rather than cluttering the dock and / or menu bar with 100 icons just to access their preferences once in a blue moon.

Whether OSS or not, $2 is a bargain for an app that I have been happily using since ages ago...

Thanks for the feedback...

July 08 2011 at 5:16 PM Report abuse rate up rate down Reply
1 reply to nznordi's comment
Christopher Forsythe

Appstore rules require a .app, no prefpane.

Chris

July 08 2011 at 5:48 PM Report abuse rate up rate down Reply
2 replies to Christopher Forsythe's comment
isthisreallybad

That's a shame. Hopefully Apple will ease up on that limitation.

July 08 2011 at 5:56 PM Report abuse rate up rate down
nznordi

Thanks for the clarification Chris.. that is quite an omission indeed...

July 08 2011 at 5:59 PM Report abuse rate up rate down
Mike Pulsifer

I'd be happy to drop a buck or two for it.

July 08 2011 at 2:40 PM Report abuse rate up rate down Reply
MPercentTwentyM

Any word on whether network notifications will be part of New Growl, or if someone's planning to write an add-on for it? Last I checked, it works barely or not at all right now. (Shame, because I've been hoping to use it as a kind of simple messaging service like Windows' "net send" — making a Growl notification with my message pop up on my mom's Mac using Terminal, or maybe a simple AppleScript Studio app.)

July 08 2011 at 1:37 PM Report abuse rate up rate down Reply
1 reply to MPercentTwentyM's comment
Christopher Forsythe

We're replacing it with a more robust solution.

Chris

July 08 2011 at 2:42 PM Report abuse rate up rate down Reply
Buy an ad here

Tweets

© 2012 AOL Inc. All Rights Reserved.