Results tagged “readability”

Readability, Instapaper, the Network and the Price we Pay

April 1, 2012

This is a long-ass post. In summary: Readability and Instapaper are two awesome reading tools that actually aren't in competition since Readability is mostly a network and Instapaper is mostly an app. But, foolish fanboy enthusiasm on both sides has got people choosing "sides" between the apps and turning legitimate feature debates into some sort of moral judgment of the people building the tools. Based on what I learned during a similar stage in the evolution of the blogging market, I fear these petty squabbles will hurt both tools and leave the market open only to the biggest, best-funded, most soulless competitors and that both these cool, innovative tools will lose.

It's an interesting time for those of us who care about reading on the web. My friends at Readability have launched an awesome API that marks the maturation of a really powerful network for synching the things you read across a ton of great apps and devices. It's pretty exciting.

And also, it's a time for the nascent space of reading improvement tools, as pioneered by Instapaper, Read It Later, Readability and others, to reach that inevitable point in a young tech space's development where things develop into a shitshow flamewar that nobody comes out of unscathed. Or, maybe this time, we just don't have to go through all of that again.

Where We're At

First, I should loudly and clearly disclaim: I'm theoretically conflicted all over this. I am an enthusiastic and proud advisor to the good people at Readability and consider them friends. I am a long-time fan of Marco Arment's from even before Instapaper was created, and whenever we've seen each other socially, I've been really impressed by his thoughtfulness. I still have some equity in Say Media (the successor to Six Apart), which theoretically benefits from publishing sites that run ads which these apps hide. And I'm sure there's more little details you could suss out if you were already convinced that I'm acting in bad faith or don't mean the words that I say here. Rest assured, after a dozen years of blogging here, I write what I write here because I mean it, and I know it to be true, and I hope that's enough to explain my motivations.

Until a few weeks ago, Instapaper was the inarguable mindshare leader in this space, pretty much synonymous with the concept of saving articles on the web for later reading, even though the other apps in the space have also been very popular for some time. Meanwhile, Readability has been pursuing a network strategy, building its reading functionality first into an API that's been adopted by a bunch of apps, then launching iOS and Android versions of reading apps under its own name. These were very well-received, and for the first time, another reading application got as much attention and praise from the tech elite as Instapaper's been getting.

That's when things got complicated.

You see, Readability's original plan was to work with Marco to license a version of Instapaper as the flagship Readability client. Marco describes much of this in great detail on a recent episode of his Build and Analyze podcast, which I think is generally very fair, but you can get a brief description of the story from the posts that both Readability and Marco wrote about the end of their partnership. It was amicable, well-handled and resolved as happily as could be, given the circumstances.

In fact, the only thing I disagree with Marco about in his assessment is the most direct cause of the business partnership between the two companies being unsuccessful. Simply put, Readability and Instapaper weren't able to work together because Apple changed the rules of the market. The deal they had made would probably have been something that could work, if Apple hadn't changed the rules about in-app subscriptions at literally the moment when the joint app was submitted for consideration in the app store. That is, of course, Apple's right to do, but it means that whatever schism happened didn't occur because of malice or ill intent or duplicity by either party; It happened because sometimes shit happens.

This matters because, since the success of the recent Readability app on iOS, things have gotten tense, not between the creators of the two apps, but between supporters, fans and enthusiasts in the community for both apps. And, since I've been through this kind of stupid fanboy battle before and know exactly what it costs, I want to explain what I think is at stake and why we're headed down a dangerous road.

Legitimate Debate

There are a few points of inarguable agreement and a few points of legitimate debate which it's important to dispense with if we can have a useful conversation about the future of reading tools online. Here are the premises from which I'd start:

  • Most content sites on the web are unpleasant to read, and conventional advertising is a big part of the reason why.
  • The behavior of sending content from the web or apps into other services and synchronizing between those apps is only going to become more common, and hopefully will become mainstream.
  • People like the creators of Readability, Instapaper, and the other early tools in this space are real web people, who are both able to, and interested in, hacking on the web because they care about it. This hasn't yet attracted the folks who just have dollar signs in their eyes but don't care about it.
  • Sites which publish original content can't survive indefinitely if a substantial percentage of their readers either block ads or read their content in apps which don't display those ads, unless there is some other way for them to generate revenue.
  • Advertisers will not be so dumb as to continue buying ads on sites at current rates when a significant, or particularly valuable, segment of the audience starts viewing the content through reading apps.
  • Nobody's solved this problem yet, and it's still very early days.

I'm hoping those baseline assertions can be agreed upon; If anything there is really objectionable to you, I can't help you, because you're crazy. So, where are the things we can disagree about? Right here!

  • Most reading apps have a way for users to pay for the app itself, either as a one-time purchase or a subscription. Many publishers find this objectionable, as the publishers get no revenue from these applications and readers who use them do not consume ads except (usually) when adding the content to their reading app.
  • Apps like Instapaper make the argument that publishers will be able to get the same CPM advertising rates for people who save articles into their apps because the regular web page is displayed before being reformatted into a cleaner format. Some publishers object to this model on the ground that advertisers are becoming aware of this trend and will start paying lower rates as a result.
  • Apps like Readability offer a system where a subscription payment holds the majority of its revenues (in their case, 70%) for publishers, but requires the publisher to register with the app in order to receive their payment. Some people consider this objectionable because it's opt-out instead of opt-in for the publishers, and because it's not clear enough what happens to unclaimed payments.
  • A few people object to reading apps because they want a site's publishers and designers to have final authority over how their content is displayed to users. Most of us consider this untenable because it's in tension with the design of the web.

People may quibble with the wording or emphasis I've placed on various points above, but I think these capture the major discussions going around, and I think reasonable people can fall on various sides of these issues, or may fall on both sides of these issues at various times. Here's the thing that I think is most clear: Reading apps give people a better experience on the web, but do so in a way that's in tension with current publishing business models, and it will take painful, disruptive changes to resolve this tension.

Now, with the reasonable overview out of the way, we can talk about how we people who love the web continually fuck ourselves up.

Crabs In A Bucket

I've known John Gruber and Merlin Mann a long time. Though it's mostly been online, I try to have dinner with them once in a while when we're in the same cities, and if we were proximate, I'm sure our kids would hang out. They're good guys, and I appreciate that they're caustic and funny and am happy for their success.

When Readability first came out for iOS, a lot of people targeted their enthusiasm for the app as criticisms of the dominant player, Instapaper. Marco understandably shared a bit of his hurt at this development on his Twitter account, stoking the expected sympathy but also stoking a bit of rage as people sought to show their loyalty to Marco by "fighting back" at Readability. Marco had used the word "copycat" in a tweet, and that was the early criticism, that Readability was too similar in concept to Instapaper and that this was a dishonest enterprise. Obviously, given that none of these people had leveled this charge at Read It Later or the many other apps that were in the space, this was a reaction to the unexpected popularity of a challenger that they weren't ready to recognize as a member of the in-group.

The second wave of the defense mechanism that had been triggered focused on our tech community's signifiers of authenticity. I saw a number of critical posts which (falsely) described Readability as "VC-backed" or as a "big company" swooping in on the little guy. Again, these folks never criticize Apple or Microsoft's mistakes as being due to their being "VC-backed", and Readability's team is a handful of folks, so certainly bigger than Instapaper, but a tiny company by any measure. The issue isn't whether both of these apps are bootstrapped — they are — but rather whether enough small distinctions could be found to say why one is "good" and the other "bad".

This is where things were a few weekends ago, when I was even trolled into some stupid tweets that made it look like I was picking sides, when really I was just annoyed knowing I'd have to write the post you're reading now.

But with most disinterested bystanders finding these angles of attack ineffective, critics honed in on what they saw as the biggest area of objection with Readability, one which obviously could be legitimately disagreed about, but which would be especially useful as a wedge between the two apps if it could be painted as evil. This was the system that Readability had devised for handling publisher payments. John used this point to characterize the Readability team as "scumbags", Merlin chimed in with a tweet on the topic, and Readability responded with an explanation of what the company is about.

Now, I should be clear: The Readability folks aren't scumbags, and John's being a bully by using his platform to say that. That's his right, of course, but my long-time impression of John has been that his intent is to speak truth to power, and while I am all for his name-calling when it comes to giant institutions and powerful industry titans, I think it's inappropriate and beneath him to do so for individuals who are working in good enough faith to carry on a discussion at a personal level. Put another way, if you can email somebody and find out their side of the story, you don't need to publicly insult them, which is good because public insults aren't particularly effective anyway.

[Update: A few people have asked why I say John's being a "bully" here. There are a few aspects, mostly related to his unique place in the Apple/iOS media realm. First, because he routes so much attention through his links, lesser blogs will compete to restate his opinions (such as criticizing Readability) ever more pointedly, in hopes of earning a link. This is already taking a place. More broadly, instead of conceding that he merely has one of the possible positions on Readability's publisher program, he encourages his Twitter followers to believe that Jeffrey Zeldman and I are motivated by a greed we're attempting to hide from people rather than that we come about our opinions honestly. As stated above, I have a lot more shares of an advertising company (Say Media) than I do of Readability, so if we want to grant the premise that I have no character and am sneaky and desperate enough to mortgage more than a decade's worth of reputation that I've earned for some short-term possible return, certainly I'd be betting on the side of publishers making money with more banner ads, rather than on them getting paid through some evolution of a consumer payment system. Similarly, you'd have to believe that the Readability team's nefarious planning deduced that the easiest way to profit from publishers' work was not by making pirated Kindle books or spam blogs, but by creating an incredibly powerful realtime content normalization and synchronization service, getting it integrated into many of the best apps in the industry, creating cutting-edge apps with what's among the best design and typography ever done in an app, and then hoping nobody would notice what they were up to. By the same logic, John must secretly be advocating his position in order to undermine all but the smallest, most vulnerable reading apps so that people are forced to read his site in its original format, where it displays the ads that pay his bills. I don't believe that's true, though. I think John thinks he's more likely to get people in our corner of the tech media world echoing either his criticisms of me and Jeffrey or of Readability if he makes them more pointed (which generally does work), and then will publish and promote the recitations of those same attacks as "evidence" of correctness. Assembling a mob where membership is earned through repeating a slur instead of adding facts to a discussion, and then rewarding those members with attention and amplification is, put simply, bullying. I point this out not because I bear some ill will against John — I sincerely don't — but because I know how this dynamic works in tech media because I used to exploit this kind of thing myself until I thought better of it.]

As I started to get dragged into a discussion with John on Twitter tonight about how "we can legitimately disagree about the mechanics of this payment method and suggest ways to improve it", I realized: We're doing it again. We're fucking ourselves. We're crabs in a barrel, all pulling each other down, and the whole web is going to lose as a result.

How We Screw This Up

I learned a lot of lessons from the stupid blogging tools war of the mid-2000s. I haven't shared a lot of them because, well, I've been busy and not that many people care. Suffice to say, there was a time when many of the same people who have Very Strong Feelings about the current wave of reading apps had strong feelings about WordPress vs. Movable Type, or Tumblr vs. WordPress, and I was delighted to troll them into either agreeing with me or battling me, either way. By the end, I was doing it with the awareness of how silly it all was, but when it began, I didn't realize the cost it would exact.

For example, fairly early on in WordPress' ascendance to dominance amongst more robust blogging tools, Matt Mullenweg made a stupid mistake and put some spammy links on the WordPress website. This was early on, before Automattic was even a company, I think, and it was immediately fixed. Matt learned some lessons from it, went on to make a great product, and made a strong company and has made the web better overall.

But at the time? I took it as proof that we were right, that we must be the good guys, and that he was wrong and probably bad. That there was something about our competition that I thought had to exist on a moral level. And even though I never explicitly egged them on to do it, our community picked up that baton and ran with it. We'd always prided ourselves on how we never asked people to switch from (the then constantly-failing) Blogger to Movable Type, but Matt was regularly asking people to switch to WordPress. The nerve! Asking people to use his product! Dave Winer used to get similarly hurt that we "let" Movable Type users attack his Userland tools, but we'd never known how to appease his frustrations because we hadn't ever encouraged them to attack. In hindsight, though, it's clear we could have set a tone of disapproval of those kinds of criticisms if we'd have understood what he meant.

That's the nature of how our insular tech communities are when they're in their early stages. I got a sense of the shoe being on the other foot when one of the first times I mentioned Tumblr in a marketing page I made for TypePad, I got an angry response from Marco. I hadn't said anything negative about Tumblr, but had clearly struck a raw nerve with my offhanded mention, and I realized that Tumblr was then still young enough that Marco saw any mention by a competitor as existing in that moral ground of the competitors having to be motivated by some nefarious goal. We settled things amicably right after, but it was striking for me to see how easily I could offend someone whose work I admire.

What About Our Friends?

The worst part of seeing how these petty scuffles play out was that the insidious desire to recast a competition between a number of really good tools as a battle between the Good Guys and the Bad Guys was encouraged by well-meaning, supportive people. I know exactly how good Marco feels to see John and Merlin go to bat for him because I've been on that side of it; Back in January John and Merlin spent the entire first segment of a podcast together talking about how much they loved Movable Type, and it warmed my heart. They used to do the same when Movable Type was in a category as vibrant as reading tools are today, and when the stakes seemed high enough to be worth tearing a competitor down.

That's not to say that folks like John and Merlin aren't sincere in their reasons for supporting Instapaper and criticizing Readability — I think the points they use to back up their arguments are their honest beliefs. But their motivations? It's their wonderful, horrible personal loyalty. It feels good to pick a team and go to war for it. And the thing is, it can be effective, because it does help the eventual winner.

Which is never either of the players that are engaged in the stupid battle.

Because when I would spend my time flinging zingers at Matt Mullenweg about the merits of Movable Type vs. WordPress, you know who was winning? Mark Fucking Zuckerberg. Facebook won the blogging wars. The web became a more closed place than if either Movable Type or WordPress had evolved into the tool that powered social networking.

How We Lose

I strongly fear we're about to cause the same damage to the reading tools market that we did through our stupid fights in blogging. We've got two great, vibrant reading tools that are innovating in the space. To my mind, they're entirely complementary and should really be working together. As I see it:

  • Readability is a really useful network for encouraging and supporting reading, that syncs up your reading content to apps on any device. Its own apps are just a few good choices among the many that connect to the network.
  • Instapaper is a powerful, best-in-class reading app for serious readers. It has a passionate community that supports it, and focuses on being a great iOS experience.

To me, they're just not competitors. It's only the most short-term thinking that would make them so. But those who are fixated on that short term thinking might want to get their shots in on their less-favorite player. And if they do so, they'll destroy both.

Because if we succeed in vilifying Readability for trying to figure out a publisher payment model, Instapaper is going to go down with it for charging for its app. If we succeed in attacking Instapaper for providing ad-free views of content within its app, Readability is going to go down with it.

And the only survivors will be the competitors with inferior products who don't have nearly as good an experience, as much passion for innovation, or as much love for the web. What those competitors do have, in some cases, is $100 million in venture capital funding. Enough to wait it out while these two tiny little bootstrapped players get torn apart by their own fans.

It doesn't have to be this way. I think fans/supporters/whatevers of both these tools can keep their strong opinions but back down their rhetoric while still saving face. Simply ensuring that critiques of any of the debatable points above are, as they say, insightful and not negative would go a long way. But it's just as important to understand the larger industry trends that are being influenced here, and how they tend to play out. Directing our fierce loyalty to one of a small number of early players in a space usually encourages either an arms race or a war of attrition. And the victors end up being the giant lumbering competitors that don't even get caught up in the battle.

Readability And Intention

November 17, 2011

The latest launch I'm ecstatic to share with you all: My friends at Readability (whom I advise) announced their amazing new platform! Though it's best known as a simple way to clean up the formatting of an article that you're reading on the web, there's an incredible depth to what Readability now offers:

  • A terrific service that integrates with any web browser to make reading more pleasant either now or whenever you have time to read — and now that service is free!
  • A brand new HTML5 web app that lets you read on the go on any platform, soon be joined by a beautiful iOS app that will let you read on your iPhone or iPad
  • A robust and inspiring API that powers the entire Readability platform, which is already starting to upgrade some already-amazing apps like Reeder and TweetMag

But as cool as all that news is, I'm even more excited about what's in store in the future for Readability, and I thought I'd explain why.

Things Can Be Beautiful

Just one small, wonderful detail about the upcoming Readability apps for iOS epitomizes why I can't wait for Apple to approve them: Every time you're reading in the new apps, you're seeing typography by Hoefler & Frere-Jones. I'm certainly no designer, but even from a layman's perspective, I know what a big deal it is to be the first app to have this level of type expertise be applied to the reading experience.

It's not just the font-hipster value of reading a headline set in Gotham or body copy in Whitney; What I'm struck by is the sheer commitment to quality in an app experience down to the finest level of detail. The Readability team teamed up with Teehan + Lax to make what I'm comfortable calling the best-designed, most attractive mobile apps I've ever seen. In a world where every Apple blogger is wringing their hands over skeuomorphism, it's delightful to see a family of apps go the other way into pure, beautiful function.

A Real Platform

The geek in me cares about what's under the hood, though, too. And as no less an authority than Dave Winer noted, Readability's new API is formidable. I frankly didn't get it a few years ago when Dave was always so excited about OPML and reading lists, but these days I understand that a simple, synchronized list of the content that matters to you is something that should almost exist at the operating system level. It should just be baked into everything you do.

The experience of an "it just works" synching system in the cloud is powerful. For files, I get that experience from Dropbox. For notes, I wanted that experience from Evernote, but always got too much other crap. (Note: Evernote's a very nice app, and I know lots of people love it, but I just want things to be clean and simple and not full of all kinds of bells and whistles for tasks as important as reading.) Managing that type of synchronization across all my phones and tablets and laptops and desktops and other systems is a significant task, and it's impressive that Readability is poised to do that for me not just in all the Readability apps, but even across my other apps as well.

That's not to say that the basic "let's clean up this page" capability of apps like Evernote isn't valuable — it's great! But that much is built in to the browser on my phone these days. What I care about is having the information that I want to read be available wherever I am, in the format that's most readable. It's a capability that I firmly believe will be baked in to all of my most commonly-used tools and apps in the years to come. And it's a vision that's much bigger than any one app.

Trust and Values

Of course, as I noted yesterday, I also care a lot about owning and controlling my data. Readability's API makes it very easy for me to manage and maintain a list of what I'm reading without giving up my ownership of that list. I can take my ball and go home, but just as importantly, I can take my list and plug it in to whatever else I'm doing.

That's critical because, as I'd noted at the beginning of this year when I first joined Readability as an advisor, reading is a profound and meaningful experience, and in my opinion is among the most valuable things we can do with our time on the Internet. I need it to be everywhere that I am, and I need to trust that the platform which powers my reading online shares those values. Even for simple things, like not sharing my reading behavior without my express permission.

The best way I can show the character of the team behind Readability and the community around it is by talking about who's not working with Readability's platform — yet. Marco Arment, creator of Instapaper and a former fellow Readability advisor, had a thoughtful and respectful note about the fact that he and the Readability team have gone their separate ways now that their respective apps are slightly more competitive with one another.

I don't mean to tell tales out of school, but I know the Readability team respects Marco as much as he respects them, and the fact that innovative, creative entrepreneurs can work together (or work apart) in such productive ways is why I'd feel safe as a developer building on Readability's platform. And I hope to see Instapaper and the Readability platform (both of which I happily pay for) work together at some point in the future.

But, for that matter, I hope to see Readability baked into Google Chrome and Microsoft Word and iBooks and all the other apps I use every day, too.

Read Later

There's a lot more I can say about Readability because I'm so excited by the platform's potential. But for now, there are a few key points I'd start with if you want to explore more:

  • Readability's API is going to be one of the most meaningful tools that developers can bake into their apps in the months to come. It really does remind me of the early days of Twitter's API, in the feeling that it inspires in me to want to spend a weekend hacking on it.
  • Readability is also one of the key APIs that support this year's NYC BigApps challenge, where you can win your share of $50,000 in prizes as a developer. I think this year's apps are guaranteed to be the best ever in a BigApps contest.
  • You may want to revisit Reading is Fundamental, where I mentioned earlier this year the ideas that made me so passionate about Readability and its potential.
  • CNN has an odd, but sort of charming, look at the new Readability. I preferred Ben Popper's take at Betabeat.
  • And, going back more than four years, To Read is To Be Human, when I first started reflecting on the optimism and idealism that's captured in the simple action that so many of us do every day when we save an article with the intention of reading it in the future.

Reading is Fundamental

February 1, 2011

A few months ago, I wrote about fat pages, the unbearable burden of clutter that often makes reading on the web so much less pleasant than it ought to be. It ended with a sincere wish:

So, if these smart folks are right, and lots of people value a clean experience, and right now publishers are making zero dollars off of readers who prefer uncluttered reading, who is going to be the first to charge for a clean version of their site? And which bloggers are going to choose to eschew all the flashing ads and obnoxious sharing buttons, forgoing a few dollars in revenue in exchange for a better presentation for their ideas?

We already know people will pay for more control over presentation and the ability to skip ads on TV. That same drive has helped satellite radio take off. We see even the Gawkers of the world headed towards designs with fewer ads. And lots of us pay a premium to use computers that aren't pre-loaded with spammy software or covered in advertising stickers. Hell, I've been linking to the (cleaner, less ad-cluttered) print versions of articles on this site for the better part of a decade. Why not simply give the people what they want?

I didn't think it would happen so soon, but today there's an answer. Readability has launched, with a brilliant and simple web experience that gives you the control to make reading on the web as pleasant as it ought to be. It also offers a straightforward value that's not just worth paying for, but rewarding to pay for, because the lion's share of the low cost goes to the original publishers of the content. (You get to choose how much you want to pay each month, starting at five bucks.)

Be warned: This is an unabashed and enthusiastic endorsement of what Readability has accomplished, and what the team strives to do in the future. I've put a Readability button on every post on this site. And I've come on board as an advisor to Readability, and once you see what it can do now, I think you'll immediately understand why I had to jump on board.

What is Readability?

You might already be familiar with Readability's first incarnation: It was a javascript link you could install in your browser that would simplify the page you were reading to make it more comfortable. Tons of people made use of it, and the open source tech behind it was so good that in just a matter of months it got built into Amazon's Kindle, Flipboard's namesake app, and even Apple's Mac OS X itself, where it was bundled into Safari as the "Safari Reader" function. Not too shabby.

But Rich and the team at Arc 90 weren't complacent with all that early success. They kept building on that core reading function and ended up with a rich set of tools for both readers and publishers that's incredibly thoughtful and well-designed. It does a few key things:

  • You can click "Read Now" on any page to get a more readable version of the current story or article. Or you can click "Read Later" to save that article in your account for when you have more time to read. The "Read Now" and "Read Later" buttons can appear on an article because an advertiser adds them there, or because you installed a browser extension or bookmarklet on your computer's browser.
  • You subscribe to Readability for a couple of bucks a month. They take care of making sure 70% of what you've paid goes to the original publishers, ever time you click one of those Read buttons.
  • You can read your articles through the truly beautiful web interface at or by using the iPad/iPhone app (coming soon!) that is powered by Instapaper.
  • If you're a publisher, you can connect Readability to your site just by embedding a simple button, and make more money and get more information about your readers' preferences while making them more happy, too. Plus, not incidentally, you can make some actual revenue from your content that's not from ads.

Readability split

These ideas are particularly exciting if you think back a few weeks ago to "If you didn't blog it, it didn't happen". The Clive Thompson article in Wired that inspired that piece, while touching on the importance of permanence in publishing, concluded with some other key points I found evocative:

Even our reading tools are morphing to accommodate the rise of long takes. The design firm Arc90 released Readability, an app that renders website text as one clean, ad-free column down the center of your screen—perfect for distraction-free long-form reading—and it got so popular that Apple baked it into the current version of Safari. Or consider the iPad: It’s been criticized as “only” a consumption device, but that’s the whole point; it’s superb for consuming long takes. Instapaper, an app created by Marco Arment to time-shift online material for later reading, has racked up nearly a million users with hardly any advertising. “It’s for reading,” Arment says, “when you’re ready to be attentive.”

Reading Between The Lines

In all, Readability has a wonderfully optimistic and ambitious vision, aimed at supporting great writing while making readers more happy. They're a New York City startup (hooray!) and they've assembled a fantastic team of advisors. Marco Arment isn't just providing the power of Instapaper to make Readability's mobile app awesome, he's an advisor. (See his post.) Paul Ford is on board. Jeffrey Zeldman is on board. And there are even more great advisors whose tweets I don't regularly favorite.

More importantly, the team at Arc90 that built Readability is putting their hearts into this thing. It's been extremely gratifying to hear a roomful of coders and entrepreneurs talk passionately and at length about how important it is to them to support great writing, and great journalism. They speak honestly and sincerely about being on a mission, and about building a meaningful business that's thoughtful about the way it does its work and the impact this product has on the web.

So, congratulations to the team on a great first version. And if you haven't already, give Readability a try. I'm sure they'll be listening to your feedback, and I'm sure you'll find inspiration in both the beautifully-readable articles you read, as well as in the compelling app that presents them to you.