In the meantime, we started with improving the layer system of pidoco. We know of many people who struggled with the layers and needed some time to understand how pages and layers are related to each other. Another issue was the way too long list of layers that you got when prototyping for a while.

The new implementation solves these issues with just a small change: every page may contain elements itself. You can think of a special layer for each page, that is not shown in the Global Layer Repository. All elements of a page are on top of any layer that is visible on the page, but you still may rearrange the global layers among themselves. To represent this special layer (or better to say, the page) we added a new item on top of the global layer repository, which you can choose to edit the elements just as you would choose a layer:

The big advantage of this system is that if you want to you may ignore the layers completely and just work with pages. And once you are at the point that things get too complex on a page you can add layers to structure things. Without all the layers that just appear on one page the global layer list is a lot less cluttered now. An improvement we only realized while implementing this feature is that our word export now makes a lot more sense having a chapter for pages and one for global layers.

We’d be happy to know what you think about this improvement. Please feel free to chat with us and tell us whether this helps you or is just confusing you.

Today I published the second part of a double blog post on JavaScript testing (first part) and how automated tests can be integrated into a continuous integration server (second part). If you think that such topics could be of interest to you, please feel free to bookmark http://fun.kyco.de or add it to your favorite feed reader. If that is not the case, you won’t be bothered with these things in here anymore.

In our usual development cycle of three weeks we concentrated on many smaller improvements and little features that help you prototype faster. With the next version we want to implement bigger improvements like adding more structure to the repository and editor, allowing for easier reusing of smaller components within your prototypes, or increasing the flexibility regarding the interactions that you can model with pidoco. This will include the suggestions that we received through our uservoice forum or that were mentioned in our support chat.

Making such big steps will be a nice challenge that we are facing. Currently, we are developing a prototype of the final version that is supposed to include all changes we would like to do. After some initial brainstorming a while ago, Tino started to create the prototype. And he surprised me with some very creative elements, like the little boxes with a ‘V’ inside, which are menus with just one top level entry. They act as simple hover menus, very similar to our current context menu.

Having this initial prototype, we invited some few people to remote usability tests. They were asked by Tino to do some simple tasks, mainly navigating through the given dummy prototype. (Now it’s getting recursive…) Since we used our own tool, we did not have to travel to Frankfurt am Main or Hamburg to meet the people for one hour of test. The complete session was recorded, including all mouse and keyboard interaction and the voice of both Tino and the test participant. That enabled me to review the test sessions, making notes, and collecting all the ideas that arose throughout the tests.

With the notes I spent most of this week in modifying the prototype, applying some simple ideas from the tests, and thinking of solutions for issues we realized during the tests. Following will be an internal review with our team and, possibly in the course of the next two weeks, a further round of remote tests. Until now I’m quite happy how everything worked together. Conducting a test with no setup time, handing over the prototype to different people to work on without any hassle, being able to describe many ideas in the prototype without too much work.

Once we think the concept is kind of finished, the real challenge will start. We do not want to lock our doors for two years and implement the next version in one step. We’d rather like to cut the concept down into manageable pieces that we can implement in a short period of time. Usually, we tried to deploy a new version every third week. This time we might have to break with this rule, but my hope is that we can do most things within 6 weeks (two sprints) or at most 9 weeks, which makes a new version at least every second month. That said, let’s see how it will be in reality. I’ll write some updates every now and then…

Now back to my prototype.

Wow!

That is all I can say about the awesome feedback we got after the UXcamp Europe taking place a week ago.

To give you an idea:

• @elreiss: “UXcamp Europe in Berlin was a SMASH success. Thanks to the fab organizers for making this happen. And keep it open and dynamic!”
• http://twitpic.com/1sh7mw: “Ranjeet Kumar came from India to #uxce10 and says it was a best conference he ever attended (other were paid).”
• Hilko Holweg (maczarr.de) “Das Camp zählt zu den besten, die ich bisher besucht habe.” [The Camp is among the best I ever attended.]

During the closing session on Sunday some were suggesting to have the UXcamp take place either twice a year or make it 4 days long. Well, this might be a little too much for us to organize, but maybe there are others out there who want to do a camp themselves. We’d love to support you in that, so please speak up!

One thing we should not forget is that we only set the infrastructure for the weekend, but the participants filled it with live. Therefore, we have to thank for 57 great sessions (Saturday and Sunday). You can find many of the presentations on slideshare, where we even were a featured event! Many people helped us at either serving coffee all the time or taking care of the cloakroom, which we couldn’t have done ourselves. So, a big THANK YOU to all the 400 people who came to Adlershof to share this weekend with us.

About a third, maybe even more people were traveling a long way since they are not living in Germany. Some were even coming from different continents! We are really happy that we were able to welcome you in Berlin. In my opinion it is quite exceptional that so many people traveled that far just for a BarCamp.

When meeting people after the camp a lot are asking me: “You are doing it next year as well, don’t you?” Well, we have not yet talked about that. It is quite time consuming to organize a BarCamp for 400 people. On the other hand, I have the impression that if we won’t do it again, people might get angry with us and stop talking to us. We’ll let you know…

In this blog post I will show you a cool application that I have worked on outside Pidoco. Some of you might be familiar with using modeling tools. For example if you are a software developer, chances are you have to design architecture diagrams from time to time. Or if you are at a big company, you might have seen one of these complicated process models that explain how your business works. If that’s the case and you use this kind of software, the processWave.org Editor might make your work a lot faster and more convenient.

The processWave.org Editor is a fully collaborative modeling application that lets you create technical diagrams with several people at the same time. All changes that you or others make to the diagram are automatically synced between all participants in real-time – just as you know it from the Pidoco Prototype Creator. It is written as an extension to Google Wave, a powerful new collaboration platform from Google, that helps you create all sorts of documents and artifacts with multiple people very quickly. If you did not have the chance to give Wave a try yet, let me explain how it works: You start a new Wave, an artifact which is often described as “equal parts conversation and document”. You then invite the other people to that Wave to let them participate. And with a click on a toolbar button you add our editor to the document, and start modeling. A typical use case is shown in this video. The cool thing is that you can use Wave’s powerful conversation capabilities to discuss the model while you create it.

To try out the editor yourself, visit http://www.processwave.org – it is free and open source. We currently support modeling in different languages from the areas of software and process modeling, such as the Unified Modeling Language, Petri nets, Business Process Modeling Notation or Event-driven process chains. The work was done by my bachelor’s project team at Hasso Plattner Institute, the place where I study when I am not developing server components of pidoco’s Prototype Creator. Google actually liked our work so much that they invited us to demo it in a talk at Google’s biggest developer conference, Google I/O in San Francisco.

It is just two days until our second UXcamp will take off with the warm up party. The badges are already printed and prepared, 11kg of coffee arrived last week, lanyards and t-shirts arrived today. We are just preparing the session grid and after having a look at the session proposals we hopefully have enough rooms for all the sessions. I can’t help it but I have the urgent feeling that we might have forgotten something. But I guess that is a necessary feeling two days before a big event!

Today we also signed the last sponsoring contract. We are very pleased with having so many sponsors supporting the UXcamp. Without them we would not be able to host such an event and make it free to the participants. Oh, and talking about participants: it was a pleasure to read all the countries on the badges where people are coming from. We have several attendees coming from overseas! In addition, we recognized some pidoco users on the participants list. It would be a pleasure to get to know you in person, so please approach us during the camp.

Hm, still thinking that I forgot something… Anyway, see you on Friday at Volksbar or Saturday morning.

It’s no secret that globalization is upon us; and it’s also no secret that diversity adds to the culture, creativity, and competitiveness of globally operating businesses. We are happy to welcome two new members in our growing team who bring with them international experience and lots of fresh ideas: Carmen from the United States and Abba from Uganda have joined Pidoco’s marketing team and will be working together with the rest of the team to create educational and marketing materials. We wish both of them a great start at Pidoco: Welcome to our team!

Pidoco is committed to diversity. With our new team members we are proud to add yet two more countries to our “portfolio”, which by now includes Vietnam, France, Uganda, the U.S., and – you’ve guessed it: Germany. And we hope that we will continue to diversify our growing team in order to infuse our work atmosphere with new perspectives and unique ideas.

To date, there are many different tools available that support the project manager in handling all this, one of them is plan.io. We at pidoco use plan.io for quite a while right now and are really happy with it. Since we also use pidoco to create wireframes that represent the major part of our specification, it would be nice to have some kind of integration between the two systems. Having the prototype in the plan.io wiki where you can write some explaining texts around, but at the same time being able to click through the prototype to feel the intended interactions, would be great. In addition, when people comment the prototype using our review feature, most of the times it results in new tasks that we have to do in the next iteration.

From now on this becomes reality. We have developed a small plan.io app that integrates pidoco prototypes with the wiki with one click. In addition, there is a list of all discussions to the prototype, where each of the discussions can be transformed into a new task. On top of that we put all the discussions into the plan.io activity stream, which you can grab the RSS feed and get regular updates of new comments to your prototype. In order to try our plan.io app you need to have both a pidoco and a plan.io account, which you can both test for free.

As already mentioned above, there are plenty of tools out there and you are probably using a different one. However, if you let us know which one, it should be easy to integrate pidoco with your tool as well. While developing the plan.io app we also started developing an API, which we plan to publish soon, for those who would like to write their own integration. More on this is coming soon.

Tools Which Facilitate (partially) Synchronous Remote Usability Testing:

Here I will be listing some of the tools which in some way would aid in conducting Synchronous Remote Usability testing. Most of the tools will only fulfill some of the requirements listed previously or only implement partially the methodologies above.

Online Conferencing Systems:
These tools allow screen-sharing and remote control of mouse movements and the keyboard.

• Cisco Systems WebEx
• Microsoft NetMeeting
• Yuuguu

Although those tools allow you to observe and control tests sessions they come with a few flaws:

• Test-users are required to install the client software on their own system
• Firewalls may block the software (5% of test-users experience this problem)
• Real-time amendments of the prototype is not possible
• The moderator can’t use his machine for other tasks whilst conducting a test (making notes is not possible)
• Latency problems
• Test-user can not work on a familiar desktop environment

Screen Capture Software:
These programs allow virtual recording of the test-users screen. Test sessions can be recorded and stored but hardware configurations are often insufficient which leads to lagged test results.

• Camtasia by TechSmith
• Cam Studio
• iQuick Screen Capture

Video Conferencing Tools:
Video conferencing tools (Skype, MSN Messenger etc.) allow the moderator and test-user to communicate via live audio&video feeds. The downside is that the client software needs to be installed on both system. Also specific testing of prototypes is not possible and would require additional software which use-up additional bandwidth and system memory.

Presentation Softwares:
MS PowerPoint is a great tool for static presentations, is however limited in it’s collaboration and sharing features.

Video Editing Tools:
You can also create video snippets of your presentations ( MS MovieMaker, Adobe Premiere etc.) but it is a lot of hassle and will surely put you off quickly.

Online Questionaires:
Online questionnaires created with Google Form or Surveymonkey are great applications for getting quantitative feedback on your product. It is however difficult to organize and match the feedback to the right user and test session.

Since this overview on incomplete tools for Synchronous Remote Usability Testing tools could go on forever, I do not wish to withhold the solution for you guys!
A little self-promotion will follow:

pidoco° Usability Suite:
The pidoco° usability suite is an online, web-based collaborative platform which allows to create, share and test prototypes in an instance. It is a tool which combines rapid prototyping of fully interactive prototypes and has powerful collaboration features:

• Prototype Creator (creates realistic & fully functional prototypes via drag&drop)
• Reviewer (allows asynchronous work-flow and feedback collection)
• Remote Usability Tester (Synchronous Remote Usability Testing with screen-sharing, live audio-feed and mouse-tracking)

Conclusion: 

It is possible to conduct user tests at an early stage. The aim for every company is to deliver their product on time and with the least hassle possible. Every year thousands of agencies spend a fortune on running all sorts of tests and still deliver products with flaws which need later amendments. The problem is that early-on, qualitative feedback is needed yet often not achieved due to budget limitations.

Technology allows us to connect to connect to people around the globe, so why not use this opportunity to run usability test session online. It will save us the cost of travel, give the test-user the comfort of staying in his home or at his workplace and create a greener world for all of us!

For the second new feature we slightly modified the invitation dialog and added a new feature to the invite menu entry. In this new dialog you get three links, one points to a png image, one to the sketched html, and the third to the plain html version of your prototype. You can choose the page they will point to and copy paste the link into your wiki or send these links via chat to your colleagues.