waffle

Waffle is a weblog.
The author of Waffle, some guy in Sweden, also occasionally writes stmts.net.

Who is NetNewsWire 4?

NetNewsWire 4.0, the Mac RSS reader, was released just the other day. As someone who was on the NetNewsWire 2.0–3.2 beta team and who has spent at least half an hour and more likely at least one and a half hour in NetNewsWire every day since 2004, I am interested in this. Here is the problem with what’s been going on.

NetNewsWire was originally made and maintained solely by Brent Simmons, although he was able to make it work only by relying on his wife Sheila handling support duties – they both make up Ranchero Software. NetNewsWire was huge both in terms of the app’s capability, feature roster and user base, and Brent on several occasions made large upgrades entirely free.

With Brent at the helm, features were added, considered, reconsidered, reimplemented, cut and wildly discussed. None of it happened in isolation. Brent may not have agreed with all of us on the beta list all the time, but he at least picked our brains. More than once, someone had a huge database which made a redesign of some corner of the app necessary. More than once, ideas were conceived, kicked around and implemented. (Brent and NNW was for a time in the hands of NewsGator, but it didn’t change how the software was developed beyond supporting their sync service such as it for a period existed. This tells me it’s more about the individual.)

NetNewsWire 4 started in Brent’s hands as NetNewsWire Lite. It’s not surprising, considering the organic way things grew in comparison with big advancements coming into being with every OS X version closer to the platform’s birth (and mostly free from the focus to have to poorly reimplement iPad features or metaphors), that the foundation of NNW or the interplay between so many features would eventually gunk up and could use a rethinking. NetNewsWire 3 was one, and this was to be the next. As NNW Lite was mostly finished, NNW was bought by Black Pixel in 2011.

After a long period of silence, they brought out the NetNewsWire 4.0 beta, which was a mildly souped up version of NetNewsWire Lite. After a bit of culture shock seeing so many features I depended on cut outright, I decided to brave it out and see where they’d take it. The place they’d take it was a bunch more betas. One beta was literally released to just extend an expiration timer.

And now, with the final release, they fixed a bunch of bugs that had been shockingly prevalent (like how the article view would stop redrawing except for during scrolling, or how changing from an article to a tab would sometimes not redraw, or how it would just stop reacting much to mouse click events at all) and added Sync. I empathize with them because they’d been working on a sync solution with iCloud Core Data which they just couldn’t get to work well enough and then switched to trying to do Google Reader sync before that product was mothballed to the Internet’s unilateral and universal uproar. Reimplementing sync was, I dare say, 40-60% of all the work Brent ever spent on NetNewsWire. It is time-consuming, hard to get right and has tons of error cases. And it probably requires a good long beta period to settle in.

So what’s my point? Is my point that Black Pixel has been mishandling NetNewsWire? A little bit. Have they been rude to me personally? No, of course not. Their support has been kind and service-oriented. I know I can’t expect the NetNewsWire beta discussion list to be continued by osmosis. NetNewsWire has to be produced by Black Pixel in the process they use and the way they work. Of course they had an internal beta for NNW Sync. But it is nuts to have a public beta process, let it languish terribly for months on end and then not even use it to test out the sync feature but just ship it directly into production. And I don’t expect to be treated like a sage old man just because I was part of a mailing list once. But now I feel like the grumpy man yelling at the TV. I feel like the curmudgeon whining about how things were better in the old days. I don’t want to be that guy, or feel like him.

But I also don’t want one of the five most important apps in my life to fade into something dumbed down. One interpretation of this post’s title is of course “who is NetNewsWire 4, who stands behind NetNewsWire?”. It used to be Brent and Sheila. It now is Black Pixel. Black Pixel has a more Apple-like approach and it’s not the way they work to think aloud, to eagerly solicit feedback, to herd cats and cat-like ideas of what should be for dinner tonight. I can deal with all of this. But I have to see progress.

Because the answer to “who is NetNewsWire for?” used to be “people who want to use an RSS reader that’s stable, full featured, regularly updated and fast to use”. And that’s not the case any longer. For example, NetNewsWire 4.1 could just be the reimplementation of the back/forward buttons for article item selection, such that if I went to an item and then went to another item and since the first one now was marked as read, I have to hunt to find my way back to it, I could just press the back button, and I would happily buy two extra licenses just for giving me some of the sophistication back.

With any luck, this is the end of a painful first implementation of a solid platform, and new features and updates will come more swiftly now. I hope so. I know that with the exception of syncing, which I don’t use, this is the point which I thought they’d have to get to before it was really theirs, and I’m willing to start fresh here and see what they’re up to. But if the next four years are like the previous four years, count me out.

Comments

  1. Part of the problem with this space is the “app-ification of RSS” – it used to just be that RSS/Atom was just a collection of text in XML streamed to your client of choice over HTTP. These days we have app updates, news feeds, podcasts, and… I guess “smart feeds” (ala Flipboard) – in a lot of these cases the user isn’t even aware RSS is the data transport format. (NNW was there as Podcast enclosures were taking off but that was always a side-show)

    Given that the market has fragmented this much it is hard to imagine the product manager of NNW doing anything but tearing their hair out.

    By Shawn Medero · 2015.09.04 22:30

  2. I’m not a longtime NNW user, and I wasn’t part of earlier betas, but after seeing the final version 4 pushed I had an oddly similar feel.

    I discovered NNW3 because I read a fair number of independently published online comics, most of which publish an RSS feed, and an RSS reader is a drastically more efficient way of keeping track of what was updated today and which things you follow that you haven’t read than clicking through two dozen links. I wanted to save time, so I went looking, and discovered NNW3.

    I used it, and I liked it–it wasn’t really designed for me, and the UI looked a little old-fashioned, but it did exactly what I wanted to do, and did it well.

    Then the NNW4 betas started. Suddenly, the keyboard shortcuts that had worked perfectly to navigate the way I read before didn’t work anymore, and I was forced to use the mouse for a lot of stuff. And the UI kept hanging when not using the scroll bar. I filed bug reports, but was told it was probably something specific to my user that was causing the UI hangs. Oh well, it was bearable, it was still in beta, and I didn’t know of any better alternative.

    Now, after months of no visible (although obviously plenty of back-end) action, 4.0 suddenly appears. It looks different and better, has a bunch of bugs fixed, has sync back, but sync was never openly beta tested, this version or anything close to it never saw a wide beta despite one existing, and in actual use it still doesn’t do what I want it to do as well as NNW3. And I’m really torn as to whether I want to pay for it.

    Progress is fine. Sometimes I get left behind because I do things “the old way”. Other times the mass market is not me, and I have to live with the fact that what I want isn’t what most people want. But since most people willing to pay money for a dedicated RSS reader in this day and age are probably far more hardcore RSS junkies than I am, I also wonder how many of them aren’t exactly the type that you need the geeky, tweaky features to sell a product to.

    I hope you’re right that this is effectively a new version 1.0, and that NNW5 or NNW6 will work more like I and others want it to.

    By M.W. · 2015.09.04 22:53

  3. As a longtime user of NNW, back to version 1, I gave up a long while ago and moved to FeedWrangler. It’s simple. But it works. I’d love to see something even half as good as the old NNW back but I’m not holding my breath.

    By Luke Bosman · 2015.09.04 23:19

  4. Shawn: I hope that what Black Pixel takes away from this is that there’s still a market for a good feed reader that’s just a feed reader, and there’s definitely one for a feed reader that’s a spectacular feed reader. If we’re lucky, they don’t necessarily want it to be as limited as it is right now, it’s just that they didn’t want to go back to the old code base and that this is indeed the lesser of two evils.

    M.W.: I’m happy to see that I’m not the only one being rattled by this.

    Luke: Fair enough, I wouldn’t either. I have learned to “live” with NNW4, which is sad when you’ve been blazing through stuff with NNW3, but it also means I’m ready to love again if they want to show they’re serious.

    By Jesper · 2015.09.04 23:46

  5. As a longtime user of NNW and Google Reader syncing, I was very disappointed when Google discontinued Reader. Since then, I’ve tried many different options, but ultimately have had very good luck using ReadKit and a Feedbin subscription for syncing. There are some rough edges with ReadKit, but it works reliably and I use it daily on both Mac OS and iOS.

    By John · 2015.09.04 23:46

  6. I arrived on the Mac after Google Reader was already on the scene. I tried out NNW when I started using Macs, but never grew into it because it lacked features I thought should be common sense (e.g., keep unread until manually marked as read). As Google Reader continued to grow that’s what I used.

    I tried Feed Wrangler and Feedbin after GR shutdown, but finally settled on NewsBlur. I’ve used Readkit on the Mac and Unread on iOS before, but…

    Today, I happily use NewsBlur as the backend for my RSS feeds and Reader (on Mac and iOS) to read feeds. I squarely land in the camp that never wants RSS readers to die. I live in Reader.

    I downloaded NNW 4 yesterday and immediately knew it was too basic and lacked too many features I am used to. For me, it would be a step back. It’s nicely designed and I can see the appeal, but I want more commonly used RSS reader features, advanced features, more layout / typography customizations, 3rd-party sync services, etc.

    By Richard · 2015.09.05 00:19

  7. I’m not sure what happened between the development of NetNewsWire 3 and NetNewsWire 4 but 4 is really garbage. Any action within the app brings a rainbow beach ball of death. Almost unusable.

    By Joseph Singer · 2015.09.05 02:44

  8. I used to love NNW, but gave it up for Google Reader until that was killed. Since then I’ve been using Feedly as my feed store, and Reeder as the client. Give them a try. As for NNW4… I tried it today and promptly uninstalled it. It doesn’t hold a candle to Reeder 2, and Reeder 3 is already in beta. If Black Pixel hopes to monetize their investment with NNW, they are going to have to do better.

    By Ted · 2015.09.05 04:14

  9. Just another recommendation to try NewsBlur. On the Mac it’s Web-based, but I had long since ended up switching from NNW 3.x to the Google Reader Web UI just because it gave me a more full-featured browser to use, while continuing to use the NNW app on iOS. It’s full-featured, robust and pretty explicitly modeled on NetNewsWire (with some input from Google Reader) and Samuel Clay’s development process is much like what the old NNW beta list was like, except it’s open source (Web, iOS and Android) so if things aren’t moving fast enough in the direction you want, you can always fix it yourself and submit a pull request. (I have, several times.) You can also use it with third-party apps like Reeder if you want.

    By Nicholas Riley · 2015.09.05 05:52

  10. I have 257 feeds in NetNewsWire 3, a massive amount of items, it works fine. What brings NWN 4 ? Blander interface, and slow as shit performance. Slow as in “beachball every time you click on another feed, no matter how many items” Fuck it. Simmons let it die (and “gracefully” took money for an iapp that never took off), Black Pixel just touched themselves for 4 years, shame on them. No amount of sync excuses what this thing has become.

    At the end of the day what I want is working software I don’t care how much goodwill and software philosophy you waxed on, guys.

    I just pray NWN 3 will keep working for a long time along OS X’s upgrades…

    By Yeahyeah · 2015.09.05 09:31

  11. i’ve ever sent 3 suggestions to app developers and one of them was the one you mention – “back” or “previous read irem” button when clicking “next unread item” … and yes – nnw4 is slow for me too both on mac and iphone … and that sync feature – the reason i bought nnw4 – well, it did import all the feeds from cloud, but read count doesn’t sync for me … zero unread on desktop, 600 unread on iphone :(

    By vera...obmana · 2015.09.05 16:32

  12. Without the missing “Combined view” & “Undo close tab” NNW is unusable to me.

    *A user since 2003/

    By zx · 2015.09.05 18:19

Sorry, the comment form is closed at this time.