blog

Archive for June 2009

Gruden selected for NSW State Government ICT Services Panel (2020)

June 30th, 2009 by Philippa

ict-20201Gruden is pleased to announce our appointment to the NSW Government’s ICT Services Approved Supplier Panel (Contract 2020), which is the culmination of a rigorous 10 month tender process. The panel is an initiative of the NSW Department of Commerce and seeks to manage over $90 million per year of NSW Government spend in ICT services.

This ground-breaking new arrangement which runs until 2012, aims at increasing transparency and competition by giving government buyers the ability to view information on approved suppliers’ capabilities, performance and experience. It also makes it easier for government agencies to engage approved suppliers such as Gruden to provide a wide range of services including:

  • bespoke software development and support,
  • project management, strategy and planning services,
  • provision and installation of COTS software and
  • interface design, user experience and digital creative work.

Gruden’s inclusion in this contract is a reflection of the quality and value Gruden has consistently delivered to our clients. Over the past 5 years Gruden has steadily increased the work carried out for government agencies across Australia and this appointment will see us extend our reach into other NSW departments.

“Being one of the few digital agencies to be selected, solidifies our position as a market leader and a trusted & respected supplier to Government. Over the years we’ve successfully delivered & maintained large Government applications and this appointment reaffirms the value we have provided NSW Government agencies.”

- Todd Trevillion, Gruden’s CEO.

Gruden’s current contracts within government include; The NSW Department of Commerce, The Department of Finance and Deregulation, The Department of Environment and Climate Change NSW and The NSW Department of Premier and Cabinet.

Google Wave API Day Sydney

June 29th, 2009 by Mark

On the 19th June Google held a whole-day developer event at their Pyrmont office to showcase their new Google Wave technology and Gruden were lucky enough to be invited along.

Google Wave API Day

The Day

As interesting as the technology – was the format used to showcase it.

The day started with a couple of short talks introducing the Google Waves system, the various pieces that make up the whole and Google’s vision for the technology. The 80 odd developers were then broken into small groups, each accompanied by a couple of Googlers and taken off to various corners of Google’s amazing Sydney offices for a lunch and informal Q&A.

The second half of the day was dominated by the hackathon – the idea here was for the developers to work together or alone on some wave related development of their choosing. During this extended period it seemed that the entire Wave team were on hand for discussion, brain storming, feedback and assistance. The documentation guy was there to hear how documentation could be improved, the Python API girl was immediately on hand to answer my App Engine questions, the UX guy was closely observing how people interacted with Wave and where they had troubles, the Java team were recompiling the API server to include additional dependencies. This level of interaction seemed to be a great way for the Wave team to learn how people are going to approach their product and a great way to help the developers who turned up to get up and running quickly. It was also great to see the level of talent we have locally – Google maps was developed in Sydney and it’s this same team that are behind Wave.

The hackathon culminated in people demonstrating their days’ work live in front of the group over traditional geek fare of beer & pizza. There were nearly 30 demos ranging from GPS hacks to games of connect 4 and hangman to bots that could define terms and tell you what is next on TV. The winner on the night was a shared white-boarding app implemented in Flash.

Lunch time!

What is Google Wave?

There is no simple way to explain it. The most succinct explanation is possibly phrased as a question – if email was to be re-invented today, from the ground up, what would it look like? And by “from the ground up” we’re talking client, server, protocol, the lot.

At a fundamental level, Wave is an open protocol specification. The idea is that, as with email, a variety of companies will develop competing clients (eg. Outlook, Hotmail, Mail.app, Thunderbird) and servers (eg. Exchange, Postfix, Courier) based on the Wave specification.

On a more practical level Wave is email, real-time chat and collaborative content editing & versioning rolled into one. It allows for multiple people to communicate in real time using text and rich content, while retaining the full history of the conversation and the ability to browse backwards and forwards through this history.

Wave also incorporates a framework for developers to create gadgets (client side mini-apps that run within a wave) and robots (server side applications that interact with waves in various ways).

In Google’s own words:

Google Wave is a product that helps users communicate and collaborate on the web. A “wave” is equal parts conversation and document, where users can almost instantly communicate and work together with richly formatted text, photos, videos, maps, and more. Google Wave is also a platform with a rich set of open APIs that allow developers to embed waves in other web services and to build extensions that work inside waves.

- http://code.google.com/apis/wave/

If you want to know more about Google Wave there is a fairly lengthy video of it’s unveiling during the keynote of the Google IO conference a few weeks back. This video contains a number of interesting demonstrations.

There are also a number of online resources depending on whether you are interested in the back story, the big picture, the APIs or the protocol.

Demo time

Will Google Wave change the world?

Maybe, but not any time soon. The protocols that we all depend on to send and receive email were initially developed in the early 80’s and while things move a lot faster now they still years to mature and get adopted.

Google Wave represents a major paradigm shift for end users to get their heads around which is not helped by the fact that it currently has serious usability issues. It is also very much in early beta – crashes are not uncommon and it needs some serious optimisation to avoid causing browsers to occasionally hang. Most of the time these are friendly and just require browser refreshes, but they are frequent.

But for all this it is an incredible step forward at many levels and it addresses many of the current shortfalls in current modes of digital communication. Google have shown they can address performance and usability issues in their products, so the extent to which Google open up and allow competition will probably be the deciding factor in Wave’s success.

Thanks to Jan Vaughan for the great photos

Government 2.0 initiative launched

June 29th, 2009 by Guy

Last week at the Public Sphere #2 conference in Canberra, the Minister for Finance and Deregulation, Lindsay Tanner, helped launch the new Government 2.0 Taskforce.

The taskforce’s objectives are to:

  • make government information more accessible and usable
  • establish a pro-disclosure culture
  • leverage the views, knowledge and resources of the general community
  • build a culture of online innovation within Government

“Let us imagine a scenario to illustrate the point.

You are thinking of buying a house.

You go online and using mapping data you access the suburb you are thinking of moving into.

With just a few clicks you are able to access information about schools, parks, child care centres and aged care facilities in the area.

You are able to see whether crime is rising or falling in the area, how fast the local public transport services will take you to work, and how congested the roads are at 8am on a weekday morning.

With a few more clicks you are able to join an online forum about the quality of the local schools, and about the pros and cons of living in the area.

Then, after you have moved in, you are able to go online to tell your local councillor, MP or government agency that a nearby road is full of potholes and dangerous to drive on.

This scenario is not far-fetched. We are moving toward it by the day.”

- Lindsay Tanner.

Needless to say, this is an initiative that Gruden fully supports. We have worked closely with government on numerous projects and understand both the challenges and opportunities of putting public sector information online. Having a cross government body responsible for informing and empowering those at the coal face has the potential to really drive openness and interaction and we look forward to doing even more innovative work.

Further information on the taskforce, its scope and aims as well are available at http://gov2.net.au/about/.

Seven Google Analytics tips and tricks

June 17th, 2009 by Guy

Google Analytics is pretty popular for tracking website usage, and we use it here at Gruden on our own sites – including this blog. Here’s our collection of general purpose Google Analytics tips and tricks…

googleanalyticslogo

1. Clever homepage tracking

Need to know which areas of your site’s homepage visitors are clicking on?

Google Analytics’ “Site overlay” functionality works OK for HTML-only sites but it’s fairly useless if your site includes Flash elements. To get around this add Google Analytics tracking parameters to your internal links.

Here’s an example of how you can structure these links to generate some useful stats.

This link is for a “Partners” link in our homepage’s top navigation area:

http://www.gruden.com/index.cfm/p/partners?utm_source=homepage&utm_medium=topnav&utm_campaign=partnerslink

Do this for all links on your homepage and you’ll get a report on all clicks of the “homepage” source, and you’ll be able to break this down by section (e.g. “topnav”) and then by the link (e.g. “partnerslink”).

2. Filter out your own traffic

Traffic stats, especially on smaller sites, can get really skewed if visits from the people running the site aren’t being filtered out.

To fix this, add a new filter using “Exclude all traffic from an IP address”. Add your own IP address, and repeat for any other IPs you don’t want to be included (follow Google’s advice on how to use backslashes before the fullstop characters in the IP address).

Don’t know what your IP address is? Try going here: www.whatismyip.com

3. Get a weekly email report

To get in the habit of checking your site’s stats every week, simply get Google Analytics to email you a scheduled report.

4. See what people are searching for

Don’t forget to set up Site Search reporting on your account. It’s useful when creating content to know what your users are searching for – especially if it’s not something they can currently find.

5. See where people are going

When linking to external sites, track clicks on outbound links and you’ll know which sites you’re sending traffic to.

6. Use Advanced Segments

Google Analytics’ Advanced Segments aren’t really as complicated as they sound. You can use Advanced Segments to group together different types of data and then create a report.

For example, a car manufacturer might want to create a report on visits to its site’s “small cars” content only. To do this include all small car content in a custom segment by creating a series of filters that only include content with particular title text.

7. Know your site’s top-performing times

If you know the times of day when your site performs best you can then time other activity around this – such as only running your online advertising (Google AdWords etc) at these key times.

To do this create a custom report using Time on Site, Pages/Visits, and Bounce Rate metrics and then apply an “Hour of the day” dimension to the report.

Now you know when you’re getting your most serious visitors!