Archive for the 'GooglePlus' Category

Google I/O 2012 Notes: Google+ Hangouts and making your own applications or using widgets instead

As promised some notes on the next session I attended at Google I/O was The Next Generation of Social is in a Hangout. Hopefully you are already familiar with Hangouts in Google+ (a place to video chat with up to 10 other people and/or stream to the masses as a Hangout On Air). As part of Hangouts there are collaborative applications you can use. Initially these have been focused around shared activities like watch YouTube clips with other people, or working on a Google Doc. What you might not know is for the last couple of months developers have had access to the Hangouts API which allows anyone to make their own custom Hangout applications. For example, using this API Google have been able to develop the Art Project Hangout (video embedded below), which lets you collaboratively explore works of fine art with other people.

So with a couple of lines of code (included below) I can embed an Etherpad shared notepad in a Google Hangout (without publishing a live version you’ll have to trust me that this works by watching this demo ;).

Etherpad embedded into Google+ Hangout

The code

<?xml version="1.0" encoding="UTF-8" ?>
  <Module>
    <ModulePrefs title="Etherpad Extension Example">
      <Require feature="rpc" /> 
    </ModulePrefs> 
       <Content type="html"><![CDATA[
        <html>
          <body> 
             <script src="https://hangoutsapi.talkgadget.google.com/hangouts/api/hangout.js?v=1.0" ></script>
             <p><iframe frameborder="no" scrolling="yes" src="http://beta.etherpad.org/p/mhawksey?showControls=true&showChat=true&showLineNumbers=true&useMonospaceFont=false" style="width:100%; height: 100%;"></iframe></p>
           </body>
         </html>
      ]]>
      </Content>
  </Module>

Notes on making this

Here are some things I noted when making this example.

  • A good starting point is Writing Gadget XML Apps. Including the hangout API script in your gadget is essential (and get the write one).

NOTE: For developer sandbox, use this instead of the above script:
<script src="//hangoutsapi.talkgadget.google.com/hangouts/_/api/hangout.js?v=1.1"></script>

It’s a gadget, but not a gadget

The example above is very rudimentary and doesn’t use any of the Hangout API for getting/setting data, detecting participants etc. and in this example all the collaborative gubbings is being handled by Etherpad. You might recognise the XML syntax being used in this example because it’s based on the Google Gadget framework with influences* from the OpenSocial specification.

*a Googler was asked in the session if existing OpenSocial gadgets could be used in Hangouts and the answer was no with the explanation along the lines of ‘Google iterate solutions so they took the best of OpenSocial and came up with something new, but they do hope to bridge the gap in the future’

Before you get carried away

It’s quite interesting that you can wrap almost any existing application (even existing widgets) and run them in a Hangout. For the education sector the huge limitation that I can see is that Hangouts are limited to 10 participants, which will work on small tutorial groups but nothing larger. Apparently, as picked up by Sharif Salah in the fireside chat after the session, this isn’t a technical constraint but Google don’t think you can socially manage a hangout with more than 10 people. So any aspirations of creating a Blackboard Collaborate/Adobe Connect/Big Blue Button style webinar system for larger classes will have to go on hold for now, maybe it’ll be something Google include when they get serious about Google+ for Enterprise.

There are a couple of alternatives if this sort of hackery interests you. For example as part of the JISC Distributed VLE (DVLE) Programme a number of projects looked at how widgets could be used to rapidly and efficiently incorporate more functionality into learning and information systems. You can read more about this in the Extending the learning environment briefing paper. It’s still work in progress but eventually you might be able to wonder over to EDUKAPP (a pilot web app store for the UK Higher Education sector – more background), grab some relevant widgets and make your own hangout. And if you want video you could use something like the Tokbox Open Tok API to get streaming video in a couple of minutes.

Scanning the horizon it is interesting to see the open source webinar platform Big Blue Button include an internal API on their roadmap which would make it easier to extend the functionality of the platform.

In summary, with a bit of XML you can easily make a Hangout app but be aware of the limitations with group size. Also there are other similar gadget/widget based solutions you might want to try. So can you see a place for custom Hangout apps in education?

Update: When I shared this post on Google+ it occurred to me that collaborative virtual microscopes like www.virtualmicroscope.co.uk/ might be useful as a hangout app. More interestingly it’s been announced that there is now a Cameraman app which lets you hide certain participants from a hangout, but one presumes they can to interact with extensions/apps. To me this looks like the first step to having more than 10 people in one hangout, which might make it more appealing for educators

Google I/O 2012 Notes: Google+ platform basics of +1, share and recommendations

Following the opening keynote the next session I attended at Google I/O was Google+ Platform Basics. This session was a great opportunity to meet Ade Oshineye (Google+ Developer Advocate based in London). From Ade’s profile:

co-author of O’Reilly’s “Apprenticeship Patterns: Guidance for the aspiring software craftsman” and you can find out more about that book here: http://www.oshineye.com/books.html

I’m also part of the small team behind http://developerexperience.org/ which is an attempt to see if we can successfully apply the techniques of user experience professionals to products and tools for developers. We call it Developer Experience or #devexp for short.

Having followed Joss Winn’s work highlighting developer craftsmanship it was great to have an opportunity to steal a couple of minutes with Ade, in particular, I was keen to make him aware of the work Mahendra Mahey (UKOLN) is doing around DevCSI and Dev8D (Ade appeared keen to come along to the next Dev8D).

Publisher buttons, schema.org and recommendations

Back to the session, Ade and his colleague Julie Farago went through the various publisher options for Google+. These included the share, +1 and badges people can add to their own site to make it easier to get your content into other people’s streams. This was something I’ve previously looked at before, but wasn’t particularly impressed partly because when doing a Google Search for these types on buttons I get directed to Google Webmasters: Add +1 to your pages to help your site stand out, which isn’t great. A better starting point is the Google+ Platform Plugins page, which uses Developer Experience principles for customisation and options [Something I’ve only recently got my head around is why Google have +1 and share buttons given that both also open the same comment box. The answer is share is “for content that users may want to share but not +1 (e.g. news or controversial content)”].

It was interesting to hear Ade mention that the people at Google had noticed a number of people were using a more traditional html/javascript popup instead of the entirely script powered version of the Google+ Share button, so they included the code for this version as well.

A recent development mentioned in the session was Google +1 Recommendations (emphasis mine):

Working on +1, we often hear people say they want to see more of what their friends recommend. Likewise, when we talk to site owners, they ask us to help them show more relevant content to their users. Today, we are rolling out a new feature of the +1 button in platform preview: when users hover over a +1 button, they will see recommendations for other great content on your site. … To keep these recommendations more relevant and on-topic, they will always refer to pages on the same domain or subdomain as the +1 button.

Google+ Recommendation

Because this new feature is limits recommendation to the same domain it’ll be interesting to see if this has any effect on internal site traffic and how relevant the suggestions are. Currently on the small sample I’ve tried it seems to be a mixture of the most popular (page with the most +1s) and the most popular within your circles … but I could be wrong.

The final thing from this session, which I wasn’t expecting, was schema.org and rich snippets got a mention. Phil Barker (JISC CETIS) has written more on Will using schema.org metadata improve my Google rank?. My impression is schema/rich snippets won’t necessarily improve your search rank, but the added information in the search listing and Google+ stream might make it more attractive for someone to click on.

The next session I attended was The Next Generation of Social is in a Hangout which focused on the Hangout API. More details of this and hopefully a practical example to follow.

Some quick notes on Google+ Hangouts On Air

  1. Hangouts On Air are broadcasted live to Google+ and YouTube so anyone can watch even if they don’t have a G+ account
  2. Participants who can join the hangout for On Air are limited to people in your circles. So if you are planning on having guests you need to make sure they are in your circles before you start.
  3. Google+ users can comment on an On Air broadcast whist watching the feed in the Google+ site.
  4. If you are demoing Google products with multiple accounts best to log in on separate browser (first time around I got chucked out of my own hangout when switching accounts).
  5. Resolution of recording is only 480p which probably not high enough if you want people to see text in browser. I’ve experimented with ManyCams (CamTwist is a Mac equivalent) which allows you to stream your desktop as if it was a webcam. ManyCams also allows you to do picture-in-picture so you can have your desktop and talking head. Resolution still isn’t great so you might want to use partial desktop. Here’s an example of switching from a ManyCams source to Hangout shared desktop:

Here’s an extended example of a Hangout I did recently (my first) demoing a new tool I’ working on.

Final thoughts

Hangouts On Air look like a good way to quickly setup a streamed event. If you are doing desktop sharing some juggling is required if you are using standard desktop applications. If you are planning on interacting with the audience some protocols need to be established and separate channels used (you you use the Google+ comment stream, Twitter, something else). Because a Google+ account isn’t required to view when viewing the YouTube feed it opens it up to a wide community. I think I’ll be hanging out more.

Are there any other tips you’ve got?

About

This blog is authored by Martin Hawksey Google+

JISC CETIS Learning Technology Advisor (OER Programme Support)
jisc cetis logo

The MASHezine (tabloid)

It's back! A tabloid edition of the latest posts in PDF format (complete with QR Codes). Click here to view the MASHezine

Preview powered by:
Bluga.net Webthumb

The MASHebook

You can also download this post as:

Subscribe to monthly email digest of posts

Loading...Loading...


Subscribe to per post email updates

Enter your email address:

Delivered by FeedBurner

Copyright License

Creative Commons Licence
This work is licensed under a Creative Commons Attribution 3.0 Unported License. CC-BY mhawksey

Privacy /Cookies

This blog uses Google Analytics (which makes use of 'cookie' technologies) to provide information on usage. Here's an overview of Google Analytics Privacy and how to opt-out (other 3rd party services like Twitter might also be tracking you via this site, but as far as possible I try and prevent this by removing official tweet buttons).

Badges

. . .