Earning money on Google Wave applications

I was talking to Kenneth Joni Jørgensen from Greenclickmedia.dk about how Pay per click options in Google Wave. Kenneth is an expert in creating media campaigns for customers. I talked to Kenneth on how to make money on creating ads in pages.

When I’m going to develop applications to Google Wave, they will probably be supported with a Freemium model. Freemium products have two features a basis and a premium. The basis products purpose is to get people hooked on the service. It will be limited in some features and maybe supported by ads. The paying model will be ad free and have some other extra functions that will appeal to the users like more space or better security. This is the same model Google is using for Apps for my domain, where you can get the service free. With the free version you get ads on your mail. You can also select the paid version, which costs $50 a year. For this amount you get some extra functionalities regarding single singon and no ads.

We where first looking at the wave screen. With the current layout it does not look like there is space for ads like on their search or gmail pages. Google will probably find a place to put the ads, in a way so it will blend into the design.

If you develop an application, which you would like to have some money for you can insert advertisings. A way would be on insert AdSense into the pages. It could be possible to insert AdSense into gadgets like showed in the blog Gadget and Robots interaction. AdSense is just a Javascript, which should be inserted on a page and then it will show the ads. This integration should be fairly simple.

One issue with AdSense is if you are allowed to put the ads on Waves. I’m not sure how own the content, when it is hosted on Google’s servers. Is it Google or the participants in the Wave. I cann’t find any information if you are allowed to set ads on other pages than your own.

AdSense has currently products for Mobile or video, it will make sense also to make a Wave version. This way Google will still make money, and the developer can make money. If the developers can make money on their apps, they will develop more applications.

Bookmark and Share

Workflow applications in Google Wave

One interesting aspect of Google Wave is the way that users can make semi structured workflows. In the workflows everyone can interact with each other in a simple flow manner. The workflow can be created just by adding other people to the conversation, and ask them questions or guide the process. This type of workflow can

But for some workflow instances you want to have the user to follow certain guidelines. You want another person for approve or sign the document, so what there is an agreement for the document. Something like this can also be performed by using voting Gadget. With the help of robots is it possible to make the workflow more structured. I have created a sample workflow application. The application emulates a bank loan submission form.

The process is as following:

  • The customer creates a Wave and writes a reason for getting the loan.
  • Then he adds the Bank robot. He thereby gets a form to fill in some fields, in a structured manner.
  • He submits the form. The robot sends the form to a bank employee. In this case the users “test” user for approval. The customer can’t approve the form, because of access limitations.
  • When the bank employee approves the application, the form data can be sent to the backend system.

This workflow is showed in the following video.

This is a proff of concept solution and demonstrates that it is possible to build workflows in Wave.

Using wave for frontend for a workflow engine, will allow the users to interact more with each other. It will give the participants a much better idea of the whole conversation and change the content in the mean time. I believe that this semi structured way for handling workflows is the easiest way to handle many of the tasks in today’s organizations. You don’t have to follow the rules completely, but can work the most natural way.

One problem with Wave workflows is that you don’t know which workflows you need to take action on. You just have a list of all the Waves, which has changed since you where on the page last time. This could maybe be solved using tags, which each user could search for.

For some workflows you need very strict or concrete results, like invoice approval. When you need to approve an invoice you need to assign the right cost elements to the different lines, get approval from manager and pay the vendor. This might be an area where the information given is too much structured data, so it is better to handle this in the ERP system.

Bookmark and Share