OMG!!! Ponies!!!

I'm still rolling :)

(Go see Slashdot while you still can)

First Impression: Google Page Creator

I got the nod to check out Google's new Page Creator, a web-based tool for building web sites and hosting them under your Google account.

It's pretty fool-proof. The interface is basic, which - for the intended audience - is a good thing. The templates they provide are plentiful (if not a bit boring), and the page hints are easy to follow. There are tools to help with things like testing hyperlinks, which is nice. You can edit the HTML code of each section by hand, if desired, but cannot edit the page as a whole.

I created a page that I thought was nice, and took it for a test drive. I was pretty impressed - I had a nice enough looking web page in under 5 minutes.

However, when I ran it through the W3C HTML code validator, it failed miserably. The document states a doctype of XHTML strict, which impressed me, but the code failed with simple things like improper break tags (no closing forward-slash or closing tag) and no "type" declared in the javascript script call. Ambitious move Google is making, going for a "strict" doctype, but I can only hope they fix these simple errors prior to the product coming out of beta.

On the upside, the layouts are all table-less and done with CSS, which gets a thumbs-up from me.

In all, I like where this project is going. It's easy enough for my mom to use, and the end result looks decent. I hope Google fixes the code errors. Google Page Creator isn't going to put my web development company out of business, but it will lower the bar for the skill level required for users to create a basic web presence.

I give it a tentative thumbs up.

Check out Shelly's site on Google Pages.

Transparent Technology

I have to give some kudos to Bloglines.com. Why? I was thinking about something today. I was thinking that the best applications (be them standalone software apps or web applications) are those in which the technology is transparent to the user. By that, I mean that the user is free to focus on the intent of the app, rather than struggle with or jump through hoops with the technology behind it. Bloglines is one such app.

I use bloglines every day to maintain my huge list of RSS subscriptions. However, I don't ever think about bloglines. I go to their web site and spend all of my time reading my new articles - and that's how it should be.

So many applications require much more struggle with the technology. One that comes to mind is Microsoft PowerPoint. It's quite a simple application, really. I gave a workshop to faculty on how to create a ppt presentation last week, and watching them struggle with the terminology, and then fight the menu system to find the right option to do what they wanted to do was almost painful. Yet, creating a basic presentation - in concept - is quite simple. Add slides containing your text and graphics to convey your message. Apply cute transition and sound effects. Save. Done. The user interface, however, is not nearly as intuitive as the concept, and therefore presents challenges for new users. The technology is definitely not transparent in PowerPoint.

I think that all developers should pay some attention to interface design - which is a much different process than designing the logic and functionality of an application. Too many apps separate visual design and design of logic, ignoring that bridging feature of interface design. I don't mean the pretty graphics themselves - that's the visual design. I mean, the design of how users will interact with the application. That's where more attention needs to be paid.

Kudos to Bloglines.com for being a great example of transparent technology in a web application.