Since we announced Flattr Plus in early May we’ve been working hard to perfect what we believe is the web’s missing (monetization) link. It’s been encouraging, and exciting, developing an easy, automatic solution to fund content. We’re still on track with the closed beta, which will be ready in the early fall (sign up here), and the open beta, too, which is planned to launch late fall or early winter.

For now, we wanted to inform you about the developments on Flattr Plus that have happened since May. Specifically, we wanted to show you how the design is progressing, give you a peek into the data intelligence and development going into the add-on and tell you about the new API on

So we’ve done a lot of conceptualization and engineering to make Flattr Plus run like a well-oiled machine on the inside. But what about on the outside? How does it feel from your perspective as a user? Sure, Flattr Plus will allow you to easily and automatically fund your favorite content, but is it free-flowing and intuitive?

The short answer is yes. This is an interface we created for testing and collecting feedback. Bear in mind, this is just a testing screen we’re using to sharpen the algorithm.

The interface for collecting user feedback for the beta algorithms.

One of the biggest challenges the Flattr Plus project faces is determining what signifies a flattr? What browsing activity, in other words, should trigger a monetary transfer to a particular site? And how do you keep that as private as possible?

It’s sort of the crux of everything: making flattrs automatic is what makes Flattr Plus unique: no one’s ever made a payment system quite like Flattr Plus – even Flattr. One of the first things we did to shine light into this unknown territory was to just gather browsing behavior from our friends, colleagues and family, who volunteered to share all their browsing data. The idea was that by taking the maximum amount of data possible, you find the minimum amount required for the add-on to work. The process is a bit like whittling a stick: you start with a large, unwieldy piece, then carve it down to something small and intricate.

After analyzing all their browsing habits, we developed several ideas for algorithms that would trigger a flattr. Next we implemented a dashboard to show the output various algorithms produced.

Another test screen, the Add-on itself.

And of course we did some good, old-fashioned interviews of our friends/guinea pigs. However, before we could extend the test to real beta testers (you), we needed as privacy-friendly a way as possible to get useful data. This was made possible by the stick-whittling process I refer to above, but beta testers will have to volunteer some information if they want to test (of course we absolutely tell them this in a big, fat disclaimer). The final version available to the general public will be 100 percent privacy-friendly. This is a requirement for us, not a mere priority.

For now though … still whittling that stick, not to mention polishing up the code and freeing it of issues. Finally, deciding what triggers a flattr is relevant to how the add-on will function – but what happens when the add-on sends data to, so that it can disburse money to worthy content creators?

Well, the rollout of Flattr Plus demands a fairly significant number of changes to the existing Flattr system. The most substantial part of this is a rebuilt API and a new approach to how flattrs are handled. Chief among those new approaches is getting rid of “things.” Previously, as existing Flattr users knows, Flattr worked by allowing a number of elements – “things” – to serve as identifiers for what was able to be flattred. For Flattr Plus the sole identifier for what is flattrable will be the URL, i.e., the add-on will send the URL to the Flattr API using a secure connection, and the Flattr API will determine the owner of the URL without knowing the behavior that led to the flattr; so obviously, we had to do away with “things” as identifiers as mentioned in our last post.

We are now also starting to create the all-important onboarding for new users, how Flattr Plus will be integrated into Getting the add-on in the browser, creating an account, the payments flow and the dashboard all have to work perfectly together with Flattr Plus.

Finally, we’ve been speaking to publishers worldwide about opening their sites to receive funds from Flattr Plus users. Thus far those conversations have been very fruitful, and we’re pleased to report that publishers have shown a great deal of enthusiasm to employ Flattr Plus when it rolls out.

3 thoughts on “Flattr Plus update

  1. How will pages on platforms work – will I be able to flattr a Medium poster or Twitter user directly in addition, or will money flattred to Youtube still be shared with the content creator?
    How will flattr work with sites that have extremely long engagement but little ads in comparison (Twitter, Facebook)?
    How will publishers know we’re using flattr plus and not present us a “Please disable your ad blocker!” screen without people using that singal without using flattr plus?

  2. Not sure what you try to say here, but we can not, not know our customer, we have to. It’s known KYC (know your customer) and is by law a demand. It does not matter what we think about this, we have to comply to the legislation.

  3. Hi Adrian. The owner of the account will be the receiver of the Flattr.
    The issue with content of different “types of engagement” are one of the things we are trying to solve.
    Flattr Plus will be a separate extension to begin with, and yes we are going to try make publishers understand that Flattr users are not in their interest to block.

Comments are closed.