ReadWriteWeb

Google Mashup Editor

Written by Lachlan Hardy / August 3, 2007 9:38 AM / 10 Comments

I just got in to the shiny new beta for the Google Mashup Editor and I wanted to share my thoughts on it with you. Like Yahoo! Pipes before it (our review here), the Google Mashup Editor provides a simple interface that enables developers to make basic web applications and mashups quickly. And again, like Yahoo! Pipes, it is very definitely aimed at developers.

The idea behind it is to provide a rapid development framework for mashing feeds into Google services, using common technologies such as XML, JavaScript, CSS and HTML. It also offers a JavaScript API for more advanced behavioral interactions. Google describes the Mashup Editor as "a great tool for grabbing information from feeds and letting users see and manipulate it."

Google Mashups Editor
Google Mashups Editor, showing code for a 'Hello, World' application.

Documentation

For keen developers who haven't yet received access to the beta, there is a strong set of resources you can use to start learning the GME application functionality, structure, code and controls that don't require a login. Ample documentation is available, including a diagram of the application structure and a comprehensive tag reference. Typical of Google, the documentation is the bare necessities, without even a index of the listed tags at the top of the reference page. Also, there is currently a short list of articles & tutorials, a FAQ, the official project blog, and, of course, a Google Group.

Components

The application itself is divided into 3 main parts: the Editor, Feed Browser and Sandbox. A screenshot of each is included in this article.

The Editor is for building projects. Each project can have multiple GML files (I'd guess that stands for Google Markup Language, but it's not documented), and you can also upload resource files such as JavaScript or images. Each GML file can contain a mix of XML, HTML, JS, CSS and the GME tags. The examples don't encourage good coding practices, but at least you have a lot of flexibility with how you code the applications.

The GME Feed Browser
The GME Feed Browser, browsing the Read/WriteWeb feed.

The GME Feed Browser is a convenient tool for checking your source feeds. You can use Google Base, or external feeds that you source yourself. The documentation frequently suggests using Yahoo! Pipes to clean up feeds before bringing them into GME. It offers some simple options for choosing the maximum number of results and pages you want returned.

The Sandbox is the simplest of the GME components. It's a running version of your applications. Just hit 'Test' in the Editor and, after a sluggish pause, you're automatically delivered to the Sandbox where your application begins running. You can test all functionality and see how your app will look. It also offers a simple option for viewing it as a Google Gadget.

The GME Sandbox
The GME Sandbox, displaying a quick basic app I wrote for reading Read/WriteWeb feeds.

Publication

Publishing is as simple as pressing a button and choosing a name for your application. That name becomes the subdomain at googlemashups.com, such as this sample application at http://mapwiki.googlemashups.com/. Google curates a full gallery of other mashups. Getting your mashup live and into that gallery as quickly as possible will result in massive exposure - the balance will be making sure it's good enough to stand out.

Conclusion

The Google Mashup Editor is an incredibly powerful tool for rapid testing and deployment of mashup concepts, particularly those that utilize Google services or products. This opens the space to all those developers who don't have their own servers to play on and gives them a framework to kickstart development. It's simple easy and fun to produce something very quickly, but it will be much harder to produce fantastic products. Nonetheless, the cost-savings in development time are going to make this a popular testbed for all sorts of concepts. Google Mashup Editor is a name you will hear a lot in future.



1 TrackBacks

TrackBack URL for this entry: http://www.readwriteweb.com/cgi-bin/mt/mt-tb.cgi/1503

Comments

Subscribe to comments for this post OR Subscribe to comments for all ReadWriteWeb posts

  1. Google Mashup Editor -versus- Yahoo Pipes: http://www.nilkanth.com/archives/2007/07/06/google-mashup-editor-vs-yahoo-pipes/

    Posted by: layla3 | August 3, 2007 8:55 PM



  2. Google Page Creator is a free online tool that makes it easy for anyone to create ... Google Page Creator is a Google Labs project, and is still in an early
    http://www.letras32.com/letras/manny-charlton/index.php

    Posted by: letras | August 3, 2007 11:00 PM



  3. Looks fantastically lame compared to Microsoft's PopFly...

    Posted by: Chris Pirillo | August 4, 2007 4:21 PM



  4. @Chris Pirillo If you're talking looks then Popfly wins hands down, but so far I prefer GME for actually building something. Popfly is slow, awkward and inflexible. And the fact that each Popfly widget ships with an automatic redirect to install Silverlight for those people who don't have it - and doesn't tell them why or ask permission - completely destroys my interest in using it

    GME, on the other hand, works with the basic staples of the web and allows most of the same flexibility as building an app myself. I don't care how pretty it is when it just works

    Posted by: Lachlan Hardy | August 4, 2007 7:12 PM



  5. There's been much talk about Steve Yegge at Google working on a Javascript on Rails project. The key piece would be the ActiveRecord like API that is of course missing here (and the data storage engine backing it.) Just how long until Rhino on Rails? I can't wait!

    Posted by: Ryan Kuykendall | August 5, 2007 7:32 AM



  6. It seems to be a great App... i will build some APIs with it...

    Posted by: cenourinha | August 5, 2007 10:34 AM



  7. Sounds like very useful tool from Google, i'd never heard of it before reading this but ill certainly be trying it out

    Posted by: beakersoft | August 5, 2007 1:06 PM



  8. Lachlan - I work for the Popfly team and I want to find out why the Popfly site is slow for you. Can you send me an email (sriramk [at] microsoft.com)?


    - If you look at http://on10.net/Blogs/tina/microsoft-popfly/, you'll see what kind of perf you're *supposed* to see. Do you see something similar? If you're not, then I can try and figure out see why you're seeing something different.

    We're always working on performance and I want to see whether this is something we know about.

    - I would also love to hear why you think we're not flexible and what you would like us to fix or change.

    - Regarding the Silverlight redirect issue, you shouldn't see this anymore and do let us know if you do. We did have this problem in the past where the Silverlight detection logic would redirect the entire page instead of just showing an inline image.


    Thanks,
    Sriram

    Posted by: Sriram Krishnan (Popfly) | August 5, 2007 2:01 PM



  9. Veteran international correspondent Kevin Sites travels solo to report on Always Working, Always Moving: Transcript: Play this Video TRANSCRIPT
    http://www.szovegek.com/szovegek/lou-reed/index.php

    Posted by: Sove Adams | August 10, 2007 2:46 AM



  10. It seems like it ought to work, but I don't know enough CSS background image positioning to know how to lay that out. Can someone give me some pointers?
    thanks
    Sam - http://www.szovegek.com/szovegek/john-mellencamp/index.php

    Posted by: Sove Adams | August 10, 2007 2:49 AM



RWW SPONSORS


FOLLOW @RWW ON TWITTER

ReadWriteWeb on Facebook



TEXT LINK ADS