Honeycomb is a new set of online tools from the creators of Textease. Essentially it's a personal publishing and collaboration platform for children set in the context of a secure walled garden with various levels of publishing permissions set by the school.
I'm in the process of setting up a Honeycomb project with year 5 and 6 children at Chorlton Park Primary School where I teach part-time. So, I thought it might be worthwhile setting out a few initial experiences with the product as I know it's generating a fair amount of interest in the market.
What can a pupil do?
Each child get's their own account and secure login to the Honeycomb site, and once there they can choose one of two user interfaces to work with (Fizz or Buzz). Users can create web pages, blogs or wikis and they can determine who they are going to collaborate with. Adding content to a page is simplicity itself - click anywhere and type (Textease style), and there are simple text and box controls to determine font style/size/colour etc. External hyperlinks are extremely easy to add and it's also very easy to upload images, videos and audio into the user's own multimedia gallery. The simplicity of using Honeycomb is its real strength and I could quite easily envisage Year 2 children publishing their own web pages using the system.
Here's an image of a page I knocked up in a few minutes to act as an example for children setting up a "hobbies" page.
Widgets
At the moment there are only three widgets available to users: a calendar, a slide show and a neat charting widget. Clearly more will be added as the system develops, so for what it's worth, I'd like to see a table drawing widget, a presentation widget (to upload PowerPoints and Open Office presentations) and a "friends" widget to provide direct links to other Honeycomb users. Obviously, there could be N number of widgets added to the system, and I'm sure Softease have a list as long as my arm of possibilities; perhaps people might care to add their ideas as comments below.
What can't a pupil do?
Honeycomb doesn't support any html, so you can't link to images hosted in Flickr or Photobucket, and it doesn't support embeddable script, so no embedding of Quikmaps, Youtube videos, etc. It doesn't have an internal hyperlink structure as yet, and this is a serious flaw as you can't create a homepage that links to other pages on your site, or reference pages from your own page. Finally, Honeycomb doesn't support RSS feeds at present - again, quite a serious shortcoming from a web 2.0 point of view. I should point out that Honeycomb is at the very start of its development curve and I expect the team to address these issues in future releases.
Managing your school's site
Even though the system doesn't have a bulk pupil upload at present (on its way, I'm told), creating new users is very simple, in fact I've done mine live in the classroom a group at a time as this gives children the opportunity to set their own display name. Once up and running, at present the only way a teacher can see what children are doing is by visiting each of their pages in turn. This is where the lack of support for RSS really falls down as I'd like to see a sitewide RSS feed for my Honeycomb site so that whenever a pupil updated their page, I could see it in my feed reader. I'm manging 180 children's accounts in my project and while visiting each page in turn might not be so bad for an individual class teacher, it could become a real workload issue for project managers and specialist teachers.
Where Honeycomb scores highly is in the ability to set permissions for groups and individuals. Users can publish at the individual, class, school, Honeycomb or internet level, depending upon the permissions applied. This is great for schools nervous about taking their first steps into the world of online collaboration and personal publishing as it gives real control to the school as to who can see material published - really important in an online system where children can log in from school or home. Permissions can be changed for individuals or groups as you go so it's quite easy to set publishing to a class level and subsequently relax permissions a level at a time once you are satisfied that the class or individual are following your expectations.
Who is Honeycomb aimed at?
As a supplier of multi-user Wordpress blogs to schools via Creative Blogs, I was initially concerned that Honeycomb might do me out of a living. However, I don't think that any school that's invested time and effort into class blogs will see Honeycomb as a replacement for that type of approach. Honeycomb's emphasis is much more on the level of personal publishing and I can see it being very successfully used by schools already using Wordpress or Blogger for class blogs to give children their own publishing platform in a way which is much easier to manage and control than a traditional blogsite might be. I also think that it might encourage schools nervous of taking first steps into allowing pupils personal space on the web into taking the plunge. If the reaction from my Year 5 and 6 pupils is anything to go by, motivating them to use the system to create content isn't going to be a problem.
Joined up thinking
I also think that Honeycomb is only a few of steps short of an e-portfolio. If I'd purchased Softease's excellent Podium podcasting software, I'd really like to press a button that sent my audio file to my Honeycomb account, and once I'd done my creative stuff with Textease I'd like to do the same via a document embed widget. In this way, a child could save their showcase projects in Honeycomb and open them up for peer review and discussion.
Just one thought, though: if I've worked my way through primary school creating losts of lovely project pages in Honeycomb, what happens when I leave? How do I retain access to all that stuff that I've created?
Conclusion
I'm really fired up to see what the children at Chorlton Park can do with Honeycomb, and although I might quibble with Softease's description of it as "a set of tools which make use of Web 2.0 technology" (if it ain't got feeds, it ain't web 2.0, in my view), I am really impressed by the ease of use that has been built in to Honeycomb from the start. It's definitely worth a serious look, and I would reiterate my earlier point that it's at the start of its development cycle. I'm sure many of the issues I have highlighted above will be addressed in future releases making it an ideal introduction to web publishing and online collaboration for primary age children.