DevArt

DevArt was a project by Google in partnership with the Barbican London which aimed to foster and celebrate creative technology forming art.

DevArt was part competition - Google and the Barbican were going to commission the winning artist to create their piece for the Revolution exhibition - and part fostering of the creative digital arts. Developers were encouraged to explore Google's products and technologies and to create something new, documenting their process throughout via linking with their gitHub account.

I was involved with the initial stages of the project working on design concepts and helping to develop some of the logic around how to visualise a project before there is content for the developers to show. My concepts focused around creating an ever evolving piece of art that was formed by the processes of the developers as they created their own artworks. Art created by the creation of Art.

Using 'slices of time' - visualisations of coding languages, intensity and time - you could explore and track the development of any project, seeing the spikes and drops in activity. You could drill down and expand to see every line written, every block deleted, to watch the structures of a digital artwork taking shape over the days and weeks of the competition.

— The DevArt homepage, an ever evolving live visualisation of all developers activity. Previous commits can be seen falling into the background.

— A wall of pulsing, ever updating projects, all changing in colour and size. Projects could be re-ordered and explored, rolling over expands the commits and gives developers info.

— Visualising the activity of the developers project through their code commits and the languages they use. A development blog presents visuals and interactive demos.

Users could further explore the entire timeline of the projects development or even fork on gitHub and work their own variation

— Visualising the rapid build up of code and project updates in the main feed/gallery.

Projects could be sorted a number of filters; language, technologies, theme etc.

— Languages were identified by the colour taken from gitHub labeling. Different breakdowns of code commits throughout the day. 12 hours worth of activity showing the major coding trends.

— We explored adding dimension into the interfaces, showing the code as being physically behind the imagery.

Visualising experiments, updates are broken up into general commits (squares) and full releases (lines). The log would constantly be updating showing the living nature of the DevArt project.

— Another concept explored for DevArt was that of the 'codelines'. An ever updating log of all the code commits made by the developers.

— Each line would echo a slice of time, the rises and falls in height representing the activity through that update.

Users could rapidly explore the entire history of all updates via the quick nav on the right. Clicking the codeline would expand that update and project.