post

The Evolution of Mashup Development – From Hacking to Assembling

Standard

The current trends are more that business users gets more abilities to solve their own problems and for programmers to give the business users the tools to do so. There are some tools like this already that are very popular (see Explaining Enterprise Mashups), but we have only seen the start of this development. These trends will change the roles for both programmers and business users in fundamental ways and it is interesting to see how that could play out. This is one likely scenario of what will happen during the next couple of years.

Yesterday
Programmers were building applications and integrations by programming. There were very little finished modules to reuse and combine, so a lot of logic had to be written from scratch (most talk about code reuse is nothing but talk). This was not only Mainframes and Cobol, but also a lot of Java, C++ on Windows and Solaris etc.

Now
Programmers building applications using ready made modules. These modules might be full applications, libraries or, in some cases, widgets. This means that less logic needs to be written from scratch (Apache Jakarta projects have changed the lifes of most Java programmers for example).

In 1-3 years (early adopter geeks today)
Programmers and early adopter business users are assembling solutions using ready made components. These solutions are called mashups today, but are probably not going to have that name in a few years, instead the “mashup style” of solution development are going to have become mainstream and be a natural part of applications (just see how mashups are built with Facebook Applications today). The components are widgets that have been developed by programmers to function as building blocks in bigger solutions.

In 3+ years
Business users are assembling solutions, programmers are building widgets.

From Hacking to Assembling
Of course there will always be programmers that are programming low level solutions like kernels and compilers (at least those are low level to me) and business users that just want their problems solved without them having to deal with any technology. But overall the focus for programmers will go from building the solution to building the building blocks (aka widgets). For business users the focus will go from waiting for a program that solves their problem to be developed to being able to assemble a solution (aka mashup) that will address their problem. Overall the focus will move from hacking to assembling.

Great Tools for Business Users Needed
This means that business users need to be more aware of what building blocks are available. Currently there are a few early attempts to develop systems to handle this – IBM’s Mashup Hub is a good example. Furthermore there is a need for easy to use systems for business users to combine all those widgets. This is probably the hottest area in mashups right now, with everyone wanting to be in on this – BEA Pages, IBM QEDWiki, PageFlakes and iGoogle to just mention a few. But so far it has been with very limited success and just a little more than proofs of concepts or cool AJAX playgrounds. Let’s see what will happen in 2008, I for one if looking forward to seeing new cool innovative solutions to these problems.

Paranoia around Google Knol

Standard

The blogosphere and the twittersphere (is that a real word yet?) are going crazy around Google Knol, mostly it is FOG (= Fear Of Google) and paranoia. I do not see much difference between what Google have been doing for years and what they will be doing with Knol.

What is Google Knol?
Google Knol will allow you to write an article about a specific subject. Google will host the article and hightlight it when somebody search for releated keywords in their search engine. If there are several related Knol’s then the users will help rank them and in that way provide quality assurance. The writers of a Knol have the option to get a share (50% is the speculation) on all advertising revenue Google makes from the article.

Read more about Google Knol in the Official Google Blog, Read/Write Web or TechCrunch.

Why the Paranoia?
The paranoia around Knol is that Google will kill Squidoo (whatever) and Wikipedia (yeah, right) by rolling over them with their user base and Mr. Burns-like piles of cash. The irony is that by doing all the complaining about Knol the blogosphere are once again giving Google lot’s of free publicity. I agree that it is a bit sad that Google can kill off complete ecosystems of startups just by releasing a semi-done project to their gigantic user base, but sorry to say that is the name of the game. Microsoft did the same for years, and before that it was IBM. Even Saint Jobs at Apple does this. It is nothing specific to the internet industry either. The key is that in the Web 2.0 world it is possible for startups to move and innovate smarter and quicker than the big boys, so if Squidoo and Wikipedia do not adapt and join the deadpool because of that then all I can say is R.I.P.

Another big reason for all the writing about Knol is of course that posts about Google gets a lot of attention and traffic, and thus make more money to the writer via Google AdSense.

Knol is just an extension to what Google is doing already
Google is already based on user generated content. Even their revolutionary Page Rank algorithm is based on user generated content. Think about it – every time you make a hyperlink to a page you tell Google that this page is a little bit more important than before and that it probably has something to do with the page you link from. If you make money from your page it is very likely that you do that via Google AdSense, so Google is already paying you for your content.

For Knol Google will host the content themselves, and that is basically the only difference. The content is still user generated and you can still make money on the content via Google. The only thing you really need to be aware of when adding content to Knol is that Google and not you will own that content, but other than that I see no reason for the paranoia.

First mover advantage
While the still unreleased Knol gets hyped I suggest that you start writing some Knol articles about your area of expertise to be ready to add them to Knol ASAP when it launches. Of course you need to give the article an angle that promotes you and your site. Since you will be one of the first Knol’s out there you might use this to get more traffic. Another good SEO tool.

Update: Read this very interesting article from TechCrunch analyzing Google Knol

Facebook as a Mashup Container

Standard

A Mashup is according to wikipedia a web app that combines several data sources into one experience. Thinking about it that is exactly what millions of users do everyday on Facebook using the Facebook applications. Basically every application is a widget that is running in the Mashup Container Facebook. Each widget can interact with the world around it. So far there is no direct application-to-application communication that I am aware of, it is all via the Facebook infrastructure. But still each application can have access to your personal data as well as some data about your friends. This probably makes Facebook (one of) the worlds most widely used Mashup Container in existance today.

iGoogle and other widget platforms are not Mashup Containers in my definition until they allow the widgets to interact with the world around it. A widget that just sits there and does it’s little thing (like showing me the weather in my city) without being able to commuicate with the platform or other widgets is much less usefull than a widget that is part of a whole ecosystem. With OpenSocial Google, MySpace, LinkedIn etc are quickly becoming Mashup Containers in the same way as Facebook.

This is all very interesting because it means that millions of people are using Mashups every day, even building Mashups every day, all by using Facebook applications. How many of those people even know what a Mashups is? That means that Mashups are all among us already, but they are still undercover, much like aliens in some low budget sci-fi movies from the 50’s (“Plan 9 from Outer Space” rocks!).

Growing Pains: Mashups for Phising and Spamming

Standard

One thing that was clear from Mashup Camp in Dublin was that Mashups are still not mainstream, even if they are creeping closer and closer. John Herren made an interesting comment in his Introduction to Mashups presentation at the Camp, and that was that we will know that Mashups are about to be really big when the spammers and phishers start to use them. So far the spammers are concentrating on email, wikis and blog comments, but maybe the next step is Mashups. I am not sure how that would look, but I can imagine that the ability to combine services quickly would fit phishers quite well, especially if the internet users in general are not aware of those possibilities.

It will be interesting to see how this will look like and how it will impact the Mashup tool vendors and Mashups in general. Spamming and scamming is part of growing up for all internet technologies (arguably for all communication related technologies) so let’s see how Mashups will handle the growing pains.

Mashup Camp fuled by Guiness

Standard

Mashups are fun, Guiness is good, Dublin is cool – combine them all and get Mashup Camp 5 in Dublin. The highlight of the Camp was too meet a lot of smart people and talk tech. Some of the highlights:

  • Chad Dickerson from Yahoo Developer Network talked about web site performance. According to Yahoo’s experience 80-90% of the performance of a web site is in the frontend and only 10-20% in the backend. I must say that that these are suprising numbers, but as the worlds number 1 web destination Yahoo should know. So improving the front end performance has a huge impact and Yahoo are listing 13 rules to help you do so, as well as the Firefox plugin YSlow to help you analyze a sites frontend performance. YSlow is already a critical part of my web toolkit, too bad that it is very depressing seeing YSlow’s reports on my websites, I have a lot of work to do! Chad also mentioned Yahoos GUI design patterns that can come in handy for anybodyworking with web design. His slides are on http://www.slideshare.net/chaddickerson.
  • Performance was also a subject for a later discussion where John Herren and others talked about improving backend performance. The two things that really stuck in my mind was to use a PHP Accelerator to precompile PHP code (instead of doing that on the fly for every request) and to use cookies as a light weight free client side cache.
  • There was an interesting discussion about how to find Mashups, especially in a near future when there are mashups built on mashups and the users are not developers but normal mortals. The Search Engines today help us answer the question “what is”, but searching for mashups or apps is more a question of “how do I”. The options discussed covered everything from ranking mashups based on popularity and meta data to using introspection to automatically figure out what the mashups are doing. It would be interesting to have a system that could track the interactions between APIs and Mashups in a way that a developer could take a mashup apart to reuse just the parts he is interested in. Programmableweb.com is the start of such a system, but it is still only built on the basis of that the mashup developers gives the right meta data about their mashups. Since John Musser from Programmableweb was part of the discussion I am hoping to see some of this implemented there soon 🙂
  • Speedgeeking was as always a part of Mashup Camp, it is basically like speed dating but for demos. 5 minute intervalls to demo your stuff for a new group, and it went on for an hour this time. I built openkapow robots on request and it went pretty well. Building one REST robot to an unknown site every 5 minutes was a risk, but most of them went very well (search openkapow.com for tag “mashupcamp” to find my creations). My Kapow collegue Benjamin demoed his cool Blackberry-LinkedIn-Xing Mashup (also using openkapow). The winner of speedgeeking was the Mashup Camp veteran John Herren and 2nd place as well as the Winner of IBM’s Business Mashup Challenge was Dennis Deery (congrats to you both). Check out one of the most pointless results of the speedgeeking at LOLCatService – the most pointless web service ever.

David Berlind, one of the organisers, have written a good summary of the camp on ZDNet if you want to read more. If you understand Swedish you can also listen to an interview with me from MashupCamp at WhatsNext.se.

All in all it was a great Camp. Not a great number of participants, but the number is less important than the quality of the people. I learned a lot, met great people and came home with my head swirling with ideas. Next Camp is in Mountain View in March and I hope to see you there, if that is too far for you Mashup Camp is also coming back to Ireland next year.