Revenue Sharing on Facebook

I believe Facebook will become the no 1 social network before the end of 2007, but there are some things I still miss and I hope they will sort out. If they sort them out, they will please me, grow in signup numbers and earn more cash.

Revenue Sharing on the Facebook Network

One feature that I think will make the number of sign ups and use of Applications explode is the possibility to share revenues within the network. Take the the iLike application for example: The author/programmer of the application is an affiliate for iTunes and makes a small profit each time a Facebook user buys a song from another Facebook user iLike-list. If a User B buys a media item from a list provided by User A, User A should earn a small amount of the profit the application author gets.

Possible solutions on revenue sharing on Facebook

  1. Facebook Applications with affiliation and/or subaffiliation between developer and users
  2. Get part of ad-earnings from Facebook when visitor to user content clicks an ad if ad presentation is based on content context.
  3. Let a user get a smaller amount for adding new active users to their network and earn even more if his/her active users add even more active users.

I believe that this will happen somewhere, users give the social networks a lot of information that the companies can use in order to earn a lot of money, sooner or later the companies must start to share in order to get new customers and good content.

Competitive Analysis Before Redesign

Dan Brown writes a good and informative article about how to make a competitive analysis from an Information Architetural / Design point-of-view. A must read for those interested in business analysis and the more theoretical area of work for people working with front-end related issues. I liked it.

Every industry has its own version of the competitive analysis and its function is clear: to line up your product with other products and show where yours falls short and where yours is superior.

I am a ….. Front-End Architect

I read Garrett Dimons posts The Time is Now for Front-End Architects, The Latest on Front-End Architecture, Front-End Architecture at Web Visions 2006, Front-End Architecture: Markup is the Technical Foundation, Front-End Architecture: Browsers, Front-End Architecture: AJAX & DOM Scripting and realised that Front-End Architect fills the gap for all of the different titles I have had the last 5 years.

If you tell someone that you work with front-end related issues on the web, people tend to say that they also know HTML and you can see in their eyes that they wonder how it comes you suck so hard not getting a better job after almost 10 years in the business. The front-end is a huge and ever growing area of potential problems and a variety of solutions to these problems.

After the vacations and paternity leave I will step into the big boss room and discuss a smaller title change. Maybe I find this one more suitable to whatever I actually do for a living.

Iterative redesign of major websites

An interesting article by Jared M. Spool at www.uie.com about how to manage design and structure whenever the web is outdated and needs larger changes in function, architecture, structure and design.

This is an interesting approach when the technical platform do not have to change. It is difficult to take the iterative approach when moving to a new technical environment and maybe even restructured data.

But the big problem with a re-design (iterative or all-in-one) is, and will always be: How do we please the customers we already got, make it more effective for new customers AND make the site easier to work with for people who earns their salaries by working with the site each day. Read the full article at www.uie.com : The Quiet Death of the Major Re-Launch