On Wednesday night I know where I’ll be — playing keyboard for a few songs at the James Dempsey and the Breakpoints concert benefitting App Camp for Girls.
You should get tickets. It’s a fun time for a great cause.
Bonus: James writes about how this concert is full circle for him. It’s a special night.
Evergreen is a new feed reader for Macs. It’s not actually done yet — in fact, it’s not even alpha yet, much less beta. It’s still in the painful-to-use stage, for sure.
I’ve been working on it (among other things) on nights and weekends for a couple years. For much of the time I planned to make it a for-pay app — the plan was a free Lite version and a for-pay version.
But as time went on I was less and less motivated to make a for-pay app. Doing all that stuff — dealing with licenses, money, a store, support, and everything else that goes along with a commercial app — just didn’t sound like any fun, and it would have taken time away from actually working on the app, which is all I really want to do. I just don’t have time to spare.
So I decided to make it free and open source. (The code is up on GitHub.) This fits with my goals:
- Promoting feed-reading as part of promoting the open web.
- Publishing a bunch of feed-reading code and an example Mac app that other developers can use.
- Giving me something to write about on this blog.
I like developing in public. Publishing the code makes it feel like a performance, a kind of tightwire act. Which suits me.
* * *
The one thing that almost held me back from making it open source was the effect on other developers. There are for-pay Mac feed readers, after all, and I don’t want to take anything away from them.
And I don’t want to send the message that software ought to cost nothing.
I think that making it open source makes it an obvious special case. There is at least one other open source Mac feed reader, and there are other open source Mac apps, and I don’t think that these projects are fueling the race to the bottom with app pricing.
I went over and over this decision for months. It wasn’t easy! But in the end I decided it’s a good thing, and there are always good reasons not to do a good thing.
* * *
The app doesn’t have any icons yet. Brad Ellis, who I’ve worked with before on some versions of my previous feed reader, and who is my favorite designer, is working on icons.
Brad is not only my favorite designer, he’s the favorite designer of people who thought they might be my favorite designer. :)
* * *
I have no plans to make an iOS version (though anything could happen). The plan is to make it a great Mac app. Period. But if it syncs with Feedly and so on, then you could use some other reader on iOS and it would sync with Evergreen.
* * *
There is a road not taken here that’s worth exploring, though probably not by me (for reasons of time).
I would love to see a casual feed reader (as opposed to productivity-style) that just provides a timeline, with new stuff at the top. The idea is to make something like a Twitter client but for feeds. You’d get a list of articles, and when you want to read something you’d click (or whatever) to open the article in your browser.
Such an app wouldn’t have per-article read/unread status — instead it would maintain a high-water mark, the date of the newest item you’ve seen in the timeline.
For a little while I was planning to do both styles of reader, since so much of the code would be shared. But that was overly ambitious, so I dropped the idea.
But you could do it.
* * *
I made a Twitter account: evergreen_mac. Though I have no fondness for Twitter, it seems like app makers need to be accessible that way. Most Evergreen users will probably be on Twitter.
But you don’t have to use it: you can report bugs and make feature requests via GitHub. And that way they’re in the system, which is good.
You can also email me: I’m brent at the domain name that appears in the link that starts the first sentence of this post.