The Interledger Community 🌱

Andrey Torres de Lima for PipeWebMonetization

Posted on

PipeWebMonetization — Grant Report #1

PipeWebMonetization's background image

Project Update

The project is on schedule, as detailed below. In summary, we’ve got a functional WordPress plug-in and we’re currently working on our Analytics platform and further research.

Progress on objectives

The objectives of the project are:

  1. Create a WordPress plug-in to facilitate the insertion of payment pointers in order to monetize a WordPress site and make revenue sharing automatically;
  2. Add the ability to hide and show unique content from a WordPress site, only for people who contribute;
  3. Create an analytics system to show data about received payments from a WordPress site.

WordPress Plugin

As for the first objective, the WordPress Plug-in is already functional. The user is now able to add multiple payment pointers to a website. Our plug-in will handle probabilistic revenue share, and will automatically insert the pointers metatags.

All the code can be found here: Code
Our mockups can be found here (there are multiple pages, use the top-left icon to switch between them): Figma

Besides inserting the pointers, the plug-in will also send data from the payments events to the Analytics tool. We are currently working on this integration, writing down the APIs to connect the plugin to our database.

Here are some screenshots of the working plugin:

Plugin image 1

Plugin image 2

Plugin image 3

Plugin image 4

Unique Content Display

We decided to work on the second objective later on, and focus our efforts on the analytics platform now. We’ve done prototypes, but there’s currently no coding progress on the unique content feature.

Analytics Platform

As shown below in Key Activities, all the interface prototypes were done. After that, we moved to development. The Dashboard and Login interfaces were developed using Next.js. We also implemented a passwordless login system with next-auth. This reduces the need for password recovery systems and improves the overall user experience.

Key activities

WordPress Plugin

A local prototype of this plug-in was developed, and the user can add the payment pointers and their probabilities, but so far it is not possible to hide or show specific content.
One difficulty encountered was the simulation of payment events, which was necessary for reading them in our plugin, to send the payment data to the web system displaying them. However, we were able to simulate the events and obtain and treat the data from the micropayments.

Market Research and Strategic Marketing Planning

Our goal was to better understand our public, and get the answers to our essential questions, like 'who would use our technology?', 'what needs of our audience would we meet?', and 'How can we effectively use the web monetization technology to meet these needs. The main method we used to get the answers was in-depth interviews with our target audience: WordPress website managers. The interviews were focused on discovering their routines, goals, and necessities related to monetization.

Here are some of our conclusions:

A large part of WordPress sites do not monetize the content

There are many websites on the WordPress platform that do not monetize their content and do not aim to monetize. Most are made up of landing pages and institutional sites focused on marketing goals. Therefore, it is important, at first, to focus our efforts on attracting an audience that effectively generates relevant content and wants to monetize its content.

Use of metrics and how our Analytics tool can be used

Analytics tools like Google Analytics and Hotjar are used for managers to get metrics like CAC and LTV. Tools are often used at the same time to complement the information and have more than one source of truth. Therefore, insights such as monetization performance may be useful for managers.

The adoption of wallets by users would be a great challenge

As web monetization is not yet a widely used practice by users who consume website content in general, it will be necessary to think of interfaces that take this into account and that are instructive and intuitive enough to introduce the technology for the first time to any type of user.

"It would be helpful to make larger transactions"

It was something recurrent that was heard throughout the interviews. Even though it is not the current focus of the project, we will take into account the development of technology and the future possibility of new features for the product roadmap.
From the survey results, we will be able to more effectively target the product roadmap, meeting the needs of users and also marketing strategies.

Branding

The objective was to have consistent and flexible elements, both for marketing actions and for the construction of interfaces, in order to strengthen the "Pipe Web Monetization" brand. Already foreseeing the use of modular and accessible interfaces, basic elements to be followed were defined; such as colors, logo, and typography.

Branding image

Interface

Following the principles of atomic design, basic components were created whose purpose in the future is to compose an accessible and responsive design system, both for the plugin menu, within the WordPress platform, and for the monitoring dashboard.

Interface's Design image 1

Plugin Menu Interface

Interface's Design image 2

Interface's Design image 3

Interface's Design image 4

Dashboard Interface

Dashboard's interface image 1

Dashboard's interface image 2

Analytics Platform

Front-end

We developed the front-end using Next.js, a React framework. The authentication flow was made using next-auth to provide a passwordless (magic link) login. The dashboard uses react-chart-js-2 to provide responsive and animated charts to show the data.

Back-end

Most of our time in the Analytics Platform was spent with the back-end. The main challenge was the data modeling to allow frictionless scalability and performance, no matter the number of users.
To accomplish this, we chose the serverless approach with a single-table architecture NoSQL database.

Infrastructure image

This way, we’re developing APIs within Amazon API Gateway to allow both WordPress Plugin and Analytics Tool to communicate with the database in AWS DynamoDB through Lambda Functions.
The writing function (POST method) is already functional, and we’re now working on writing statistics as well (e.g revenue per day, day of week, month, and year).

Communications and marketing

Our next step is to, based on all the research mentioned in Market Research and Strategic Marketing Planning section, attract an audience that effectively generates relevant content and wants to monetize its content, engage the users who consume website content in general, to get used with wallets, understanding why are they so doubtful with them, and also engage the web monetization community with Community Calls, explaining about the WordPress researches made and the PipeWebMonetization project.

What’s next?

Here’s what we’re doing next:

  • Develop the feature to control exclusive contents in the plug-in
  • Develop reading capabilities in our API
  • Connect the Dashboard with the Database
  • Implement security tokens to connect de Analytics Tool to the Plugin
  • Elaborate on our marketing plan to reach potential customers
  • Write the documentation for the project
  • Share all our discoveries and research about the WordPress community's interaction with the web monetization technology doing a community call.

What community support would benefit your project?

We’re excited to make connections across the GFTW community because we believe that there is a lot of knowledge to be acquired and a lot of friend projects to support.

Top comments (8)

Collapse
 
gfam profile image
gFam

This all looks super awesome! I currently run the Coil Wordpress plugin which seems to work quite well but I'd be happy to test your Wordpress plugin when you need a tester.

Collapse
 
andreytorres profile image
Andrey Torres de Lima

Hahaha, thanks!
So you will be the first one to test it 😀.

Is support@gfam.live the best way to contact you?

Collapse
 
gfam profile image
gFam

Haha, great!

That email goes to the developers, that would forward to me... but the email I look after is info@gfam.live so feel free to hit me up there.

Collapse
 
chrislarry profile image
Chris Lawrence

@divydovy You might be interested in this.

Collapse
 
chrislarry profile image
Chris Lawrence

@andreytorres David (@divydovy) has also worked on WM WP plugins and user guides. I wonder if his charity payment pointer work could be useful here?

Collapse
 
andreytorres profile image
Andrey Torres de Lima

Thank you very much, Chris!

Collapse
 
divydovy profile image
David Lockie

Nice! I'd definitely recommend you to have a look at the Coil WordPress plugin which already supports using different monetisation by post type, tag and category. I seem to recall it also supports per-author payment pointers.

I know they've just released an updated version but I haven't had a chance to review the changes yet so apologies if anything here is out of date now: wordpress.org/plugins/coil-web-mon...

The analytics and reporting side looks like it could be a great add-on.

Collapse
 
andreytorres profile image
Andrey Torres de Lima

Thank you very much, David!
I will read it now 🚀