From the floor of the Enyo Hackathon
More than one hundred developers ranging from novice to experienced gathered today at the HP webOS campus in Sunnyvale to participate in a day-long Enyo Hackathon. The day featured multiple presentations from webOS developers, an introduction to Enyo for those not familiar with the application framework, and several hours of 'hacking' time where HP employees offered assistance and guidance to the attendees. (full disclosure: HP is paying for my flight and hotel for this trip)
The event was mutually beneficial for developers and HP, with the developers getting hands-on experience and instruction in one of the more innovative app frameworks of our time while Enyo as a framework received wider exposure and was improved by contributions from the crowd.
The Enyo Hackathon rolled from the starting line at 9:30 in the morning, with bagels and donuts, plus an iced trough filled with hackathon essentials: bottled water and Red Bull. After half an hour of breakfast and registration, head of webOS Developer Relations Enda McGrath took the stage to officially start the event and quickly turned things over to Gray Norton, head of Enyo development to give an overview of Enyo, including its history and why developers should consider it as their framework of choice.
After Norton finished, webOS developer Ryan Rix took a few minutes on stage to discuss how he's used Enyo for his application development. Impressively, he used Enyo for his slides, having helped build an open source application appropriately named EnyoSlides. The presentation is hosted online and can be remotely controlled and viewed over the internet, as well as accept comments and questions from the audience.
Next up was somebody you wouldn't necessarily expect to see making a presentation at a hackathon, user interface designer Hal Saville, the beauty half of the Superinhuman Industries app house (the brains half being Jeremy Thomas, who joined HP in January 2011). Saville's presentation was on how to make visually well-designed apps. Saville was the visual thinker behind such webOS apps as Tron-tastic unit convertor Radius and beloved Twitter client Bad Kitty. He focused on the importance of stripping down information, keeping things simple, being okay with white space in a design, and using your content as your user interface. He also gave a quick preview of his next app, an app named Way that will save a point via geolocation and give you distance and direction to get back there - a simple app in concept, but with Superinhuman's typical high-end design.
PhoneGap's Herm Wong gave a brief presentation on Adobe's cross-platform application compiler, and then the developers were set off to hacking. While the traditional hackathon format is to start from scratch and see how much of an app you can complete in the time required, the Enyo Hackathon extended that include contributions to Enyo's documentation and even updates to Enyo's code itself. Throughout the day multiple pull requests were approved and added to Enyo, with a ringing of a bell into the main hacking space to signal the event. They're really into improving Enyo through community contributions.
Another developer started creating an Untapped for wine, named Enyology, which he showed off in the browser and with the iPhone emulator. One enterprising developer put hours of work into making a basic app for Windows Phone with Enyo, with the majority of the work dedicated into a freshly-incorporated update to the Bootplate Enyo template to better support Windows Phone.
The most impressive and well-received demo, however, was not an Enyo app at all. Developer Blaine Bublitz put his time into making development easier for all Enyo developers. The Bootplate template is good, but it can require a lot of tedious customization to tailor it to the app in development. So one attendee created a command line tool that generates an Enyo scaffold from scratch with appropriately named files while including and packaging all of the necessary libraries. Bublitz's scaffolder also can handle debugging for Enyo apps and the developer plans to add a package manager to integrate items from the Enyo Community Gallery.
All together, the Enyo Hackathon seems to have been a success for the Enyo team. A few dozen developers got experience with Enyo and some useful contributions to the entire framework were made by attendees. While events like this only have a small direct reach, the developers that came here are the dedicated type that tend to be community evangelists for the things that they like. By and large the attitude about Enyo was positive amongst attendees, but as those who added to Enyo as a platform can attest is in need of improvement going forward. More events like this and the conferences that the Enyo team has been attending will help spread the word and get more developers on board with Enyo.