Klick_Ass is playing on words: a combination of the Ace of Spades playing card with a mouse pointer

Home of the "19 inch talk" & other nerd stuff

The first Open Device Lab Admin Meetup

Let's mingle!
Let’s mingle!

Open Device Labs (ODL) across the globe usually communicate via a special Google Group, in digested form via LabUp!‘s infrequent newsletters, or direct, e.g. via Twitter. On October 26, 2013, for the very first time a number of ODL managers physically met in the lovely city of Nuremberg. To exchange knowledge on how to run and maintain an ODL, present best practices in legal, PR and marketing, and discuss, how the communication of the Open Device Lab idea and the common goals could be pushed forward with joint efforts.

Attendees and a heads-up

Speaking about joint efforts, and to set the scene for some of the following work results, it is quite important to realize who actually participated in this meeting. A portion of the topics discussed and best practices expressed definetely do not apply to other areas of the world (outside Germany or Europe), as in nearly all legal- and tax- and also clearly some cultural issues brought to the table.

Here’s the list of representatives present that day. All global ODLs have been invited but of course not everybody could make the travel (hope to see you guys next time!):

  • Joschi Kuphal (ODL Nuremberg)
  • Ingo Kasch (ODL Nuremberg)
  • Marc Thiele (ODL Dusseldorf)
  • Tom Arnold (ODL Frankfurt am Main)
  • Oliver Beckenhaub (ODL Frankfurt am Main)
  • Martin Klein (ODL Cologne)
  • Dirk Döring (ODL Munich)
  • Anselm Hannemann (LabUp!)
  • Andre Jay Meissner (LabUp!)

The agenda was packed. So, after a short welcome by Joschi Kuphal, and all attendees quickly introducing to each other (we also met large parts of Joschi’s agency Tollwerk and even their families that morning! :)), Tim Schikora jumped right onto the first item on the agenda and introduced the attendees to the “Business Model Canvas” (BMC).

Getting on one page

Tim briefly talked about the interesting concepts behind the Business Model Canvas; and we all agreed it is not possible to fully accomplish that method within the given time. But this has not been our goal, nor to define a “business case” or to match the BMC and it’s verbiage (“Customer”, “Revenue”) to a -generalized- definition of an Open Device Lab. We simply attempted to sort out and define the typical gears and levers of the Open Device Labs present on site. To get “on one page”, and sync our perceptions and brains, before we attacked the more in-depth topics ahead. And this worked too well!

We used canvanizer.com to rapidly brainstorm and then sort, assign and refine our joint definition of an ODL. Some really interesting discussions started when attendees discussed their different perception of certain aspects. Clearly not everybody had the same opinion and priorities on various topics. People said, and I agree, this discussion alone proved valuable inspiration and a great validation for each ODLs own understanding.

The secret attendee
If you can laugh about this picture, you’ve attended the 1st ever ODL Admin Meetup! :)

Unexpected results

Some of the unexpected insights (to only name a few):

  • ODL users are not only developers. We should also target our services (and thinking) on designers and conceptionists, but do not forget scientists, students, and the customers of our direct “customers” (aka the developers clients)! Is your ODL’s communication and verbiage ready for that?
  • The benefit of “guided” testing, provided by ODL people taking their visitors by the hand, is by far not communicated enough by ODLs. Nobody else will (can?) provide such a value. Think about that!
  • Also, again on the partner side of the BMC, schools and universities raised inspired eyebrows: what a great potential for cooperation! Who could be a better partner to raise awareness within the future generation?

You can see the results of our brainstorming at http://canvanizer.com/canvas/51eM4BJjdOI (if by any reason this link goes away or the canvas becomes corrupted, here are backup versions as PNG and (a comparably ugly) PDF).

Note: It is important to mention that this is not meant as a “blueprint” for ODLs or necessarily applies (definitely not in all of it’s details) to other ODLs (that have not been on the table that day). Anyway, it might contain useful inspiration for others. You’ll sort it out.

To-Do: Centralized pool for press materials

All attendees agreed that a central pool for – creative commons licensed – press facing material, as in imagery and text copy, is needed. Attendees felt LabUp! to be the place to gather and list such material. Jay confirmed to take this on his agenda on behalf of LabUp! and follow up with a solution as soon as possible (Authors note: Speaking in the third person about myself scares me, man! Switching to first person.).

Totally running over!

The lively discussion also explains why we totally broke the agenda already with this first slot of the day, running the discussion far into overtime; even into the lunch break. Which was then held at Nuremberg’s famous sausage palace “Wurstdurst” (translates best to “Thirst for Wurst”).

Even post lunch we still took some time to finish sorting and discussing the canvas, only with Peter Neuberger and Veit Reichert joining in this first topic of the day was dropped to the favor of… even more definitions! Hey, we’re in Germany, we like to be precise! :)

One of the slides used at the meetup.
See the slide. The image says it all! :P (The german caption “Regelungsbereiche” translates best to “Scope”.)

Legal aspects of Open Device Labs [in Germany]

At this point Tom Arnold and Oliver Beckenhaub from the ODL Frankfurt am Main took over and briefly explained, how they came to developing their need for written terms and conditions. Most ODLs run on a “fuck it let’s do it” mentality and begin to care about problems when they arise. Which definitely guarantees for a kickstart at relatively low risk. (Authors note: with 80+ ODLs across 23+ countries by the time of writing I have not heard about anything really bad happening anywhere, to date. One total loss through theft, though. Unfortunately, burglary happens elsewhere as well. But, if that helps, I strongly believe bastards stealing a device library that is in place for the greater good will get a very special place in hell… maybe tied to the front of a WAP browser or so. I am open for your comments here).

But, well, there are risks, so let’s face them.

As Tom and Oliver explained these can easily be more than just obvious concerns, such as damage or theft. Housing the Frankfurt ODL in a small digital agency, they did not have the instant okay of all non-involved co-workers in their location, to “open doors to total strangers”. Discussing their ODL plans with their workmates they found there were indeed some rules needed – to define the “what if”, as far as really needed, and as short as ever possible.

Tom and Oliver came up with only two half-pagers. Only! Really nothing that should scare off anybody, by having to comb through pages of legal wastelands before just quickly testing an app or web service. Two documents, because they boiled it down to one document for actual users of the ODL, and one only needed for people donating to the ODL. What fascinated me, having worked for years for my own software company together with professionals on legal documents: they accomplished this together with a lawyer, who has been keen enough to drop some of the typical theoretical concerns these guys have and simply shoot it straight. Respect! And we met that guy, that very same day:

Veit Reichert, Tom’s and Oliver’s lawyer for trading, corporation and IT law, took over. He summed up the path and discussions the three went down in defining the legal boundaries (and consequently built the documents) of the ODL Frankfurt am Main. As said, in favor of the brevity of their documents they boiled their concerns down to take care of the following aspects, which Veit explained to all attendees like that:

  • Define the parties. Basics for every contract: who is part of the game? This also means:
  • Definition of corporation. Are you a company? An association? A club? Will you be tax legit? Do you run in danger of becoming a telecommunications provider, with all the associated risks and duties (make sure you don’t!)? Stuff like that. Realize the gears and levers simply to be able to act consciously – without getting scared.
  • Define the state of devices. Physically (e.g. when it comes to damage), but also virtually (e.g. when somebody is running unwanted irreversible software updates).
  • Define “usage”. Besides defining the scope of what you allow people (not) to do, seriously take the possible abuse of your devices and/or internet uplink into account. At least in the EU the liability for what users do over a device and/or internet uplink is with the owner of that device/uplink.

At this point, Martin Klein of the ODL Cologne contributed that they have the practice to keep a record of which device in which time window has been used by which user. By using a physically separate uplink they separate their own company’s internet activity from the ODL network usage. Combined, they’ve done already a lot to fence themselves off any possible abuse through ODL users.

  • Data. Are we responsible for any data left on devices? No, we are actually absolutely allowed to delete it! But we also request that the user deletes it, leaving devices in the state where these have been found.
  • Liability. (device-, data-, personal-) In the Frankfurt case, ODL users should not have the highest possible liability over devices let as it is defined by the (German) law when nothing else is defined. ODL_FFM decided to limit the liability to the really anticipated amount. They just did not want to scare off everybody by default. You could decide differently, but if you don’t, be aware of what that means in your geo.
  • Termination. Frankfurt wanted to have the right to terminate the contract at their free will, at any time. Just a general precaution so nobody can control the duration and extent of the contract. Pro-Tip: ask a lawyer for deeper explanations on that. :)
  • Define ownership (donator document only). A very interesting idea for ODLs to not even need to think about tax and other legal implications can be to just don’t own. As long as you define that everything that came in has been lent, you don’t own anything. Not owning means having no taxable body. Think about it. Veit pointed out that, depending on your local law, it might be wise to just use imprecise verbiage in your communication (e.g. the origin column many ODLs use on the device lists of their websites). As examples, better use “contributor” when you specify the origin of a device, as compared naming it “sponsored by” or “donated by” – this way you simply did not define the owner (publicly), or a transfer of ownership, at all. Clever lawyer? Yes? :)

Again, these can only be indicators for running down your very own laundry list of defining the legal boundaries of your ODL, in your country, in your very own universe. Veit, just as every lawyer, of course did not leave the room without claiming the respective disclaimers :) – and I won’t, as well. Nevertheless, both the Frankfurt and the Cologne ODL are making their documents accessible as public domain. You can grab their stuff for free – just make (the fuck) sure to consciously adopt them to your scenario!

  • The Frankfurt ODL wrote a blogpost that also links to their documents. (Blogpost in German, so are the documents.)
  • The Cologne ODL links to their document on the imprint on their website (both in German as well.)

[As a side note, there are English “Terms and Conditions for a Device Lab” based on the US law made available publicly by Phil Weiss, for over 10 months already. These definitions do not follow any of the aspects or the route discussed above, nor do they apply to Open Device Labs (since they rely on a monetary return value for using the lab). I just thought I’d mention there are some English materials, in case you want to start working on your own documents with invoking a proper law consultant. Again, do not simply copy any of this stuff. K?]

It got late, dood!

At this point of the day, where the sun has already been down and all previous ideas of having an agenda were long outdated, we decided to drop the plan and try to go through the most important remaining items that have been suggested by the attendees on the Google group used to plan the meeting. We decided to drop the discussion about the possible need of an “ODL certification concept / procedure” in favor of the two other remaining sessions: “How to increase ODL visibility & visitor frequency” and “Involving donators, supporters & hardware vendors”. Which had initially been set with a total of 2.5 hours, but now needed to go down in less than an hour. Fun! :)

Focussing on the best practices

Having boiled down the sessions to a fraction of the time I decided to simply run down the inspiration and examples I collected on general ODL PR best practices, including quite some tips to become more attractive to sponsors. Here’s what I talked about (please note that for nearly every example shown there are others at least as good as the “chosen ones”. I clearly do not intend to over-/underrepresent one or the other ODL with this. ):

PR inspiration: If there are local events important to your target audience, and you cannot make it over there to run a conference ODL or present your ODL via a (short lightning) talk yourself on the event, at least get into the events timeline:

  • Just send a tweet with the appropriate hashtag and greetings and invite over attendees to test at your ODL!
  • Follow tweets of event attendees and find those where your ODL makes sense to be suggested as solution to problems discussed at the event.

Simple stuff like this can easily reach hundreds of people. Examples shown:

Antistatique ODL conference ODL and tweet

Inspiration to maximize reach: If your premises allow, invite local (not only tech-!) meetups to run their events at your ODL. Present your ODL as a side gig.

Inspiration to gain traction: Why not organize an info event at the ODL, e.g. to a specific audience, such as digital publishers, and show them the ups/downsides of their industries work on your testbed. It is easy and fun and can be very rewarding to leave your usual dev-trails that way!

Leverage opendevicelab.com ratings/comments to demonstrate the vibrant community that is using your ODL to sponsors. Make sure to add a backlink to your profile and to actively ask your users to rate/comment!

Ask your users (and their customers!) to mention you and/or leave opendevicelab.com comments/ratings, to gain traction in new circles. Also, make sure your ODL is a cute foto model (see the following tips)!

Ask your users to inspire their customers to spice up their press releases with that interesting testing story (and make sure to shoot/deliver some jawdropping pictures!). Really easy to reach a whole new audience that way!

A creative decoration of your ODL does not need to be expensive and holds a lot of potential for visually engaging social posts. Use that potential!

Leverage your decorative visual highlights on your own and create and post some unusual pictures that leverage viral potential by “wowing” people!

Be creative in contacting sponsors! Example:

Honor your sponsors, also via social media. Two examples:

A video says more than 1000 words. Think of producing a quick and short video explaining your ODL and offering. It is easier than you think, and there are inspiring examples out there already! Here is a great one, made by the Rio de Janeiro deviceLab: https://vimeo.com/56758941

Leverage your video to pitch your ODL in a (~5 minutes) “lightning talk” at the rather unusual events, e.g. at a local SEO, Marketeer or Startup Meetup. By using a video and just saying some intro words and inviting people to support and visit the lab and ODLs, you really don’t have to have speaking talent and still will reach a bunch of new people at the price of a bus ticket and a burrito + beer. :)

Marc Thiele of the Dusseldorf ODL added, that he contacted all local official departments to explain what his ODL is exactly doing for the community. He received very interesting feedback from quite some unexpected areas, such as being put in touch with the local representatives of Mobile Monday to connect and present his ODL to their members. A nice idea and disruptive path to go down, IMHO!

The recent ODLC launch activities – and their successes so far

As many ODLs ask themselves how to promote their lab better, Martin Klein from the ODL Cologne apparently did a very extensive job in doing so for his newly opened ODLC with pretty good success (check out the services and activities described on their website for yourself – again, German, sorry, learn German :) or use a translator please!). He agreed to quickly present details on his launch activities. I can only list his explanations briefly here:

  • ODLC launched in July 2013 by putting the website and opendevicelab.com announcement out. For 6 weeks basically nothing happened.
  • Around September traffic picked up.
  • Today, in November, they receive 3-5 inquiries a week.
  • There are 2-5 appointments made per week.
  • Last Wednesday ODLC had 3 users on one single day.

Here is what Martin did:

  • 2 professional press releases distributed via a paid PR agency (cost: €250).
  • This returned 300-400 unique website visitors per release.
  • Martin promotes the service locally via http://www.plista.com/.
  • Had a pool of banner ads created and run a paid search campaign.
  • Ran a professional photoshooting (short and efficient, cost: €150).
  • Produced small comics “out of the ODL life”, and uses those to post and generate buzz via their Facebook page (which works exceptionally well across non-experts).
  • Invited two times already on a meet & greet in the ODL, served fingerfood.

Closing the day like a greek

With that, we closed the very first ODL admin meetup with a handful of attendees wrapping up the day at one of the best greek restaurants I’ve ever been to (outside of Greece). Everybody agreed that this should just be a start of a series of networking events between ODL managers. Even after nine hours of exhausting work (yeah!), we clearly felt there is still a lot potential to be discussed and improved.

Thank you!

Special thanks to Tim Schikora, Veit Reichert and Peter Neuberger for their very valuable help. Thanks to Ingo Kasch for brewing some bad ass (insider joke! :)) coffees. And of course thanks a lot to Marc Thiele and Joschi Kuphal for all the spirit and work in organizing this event. Finally huge thanks to all attendees of this first ever physical ODL Admin Meetup for all their contributions. Last and totally not least: to you, dear reader, for your interest in Open Device Labs – and for reading this far.

How we built the Open Device Lab at beyond tellerrand

A conference Open Device Lab
The ODL at beyond tellerrand 2012

An Open Device Lab (ODL) is basically a broad variety of internet connected devices to test apps and websites by designers and developers.

A conference is basically a broad variety of internet connected designers and developers to discuss and inspire around web and app development.

So what makes more sense than establishing an Open Device Lab directly on a conference?

For many of us ODLs are the only possibility to access the needed variety of real devices necessary for serious testing. And on conferences like beyond tellerrand some hundred potential ODL users are present. Define “synergy” – There you go!

No sooner said than done and the first dedicated Open Device Lab on a web conference in history has been created. In peak times we had more than 50 devices present in the lab. Numerous projects have been tested directly on the devices or per Edge Inspect, problems isolated, displays measured. Best practices exchanged, 19-inch-talks held. People have also simply been staggered at the fact that it needs much more than the personal smartphone to do serious quality assurance these days.

How did we put the ODL together?

Finding volunteers as well as the support of the conference itself turned out to be the easy part. And together with that a starter pack of devices to put on display felt out of the bag. Anyway, the job is *not* done at this point! The idea of Open Device Labs is not only to just gather a bunch of devices. This is much more about individual contribution of every user of an ODL – e.g. per donating devices to grow the lab! We definetely wanted to emphasize on this important concept also with the ODL at #btconf.

Of course we also wanted to create the biggest possible lab. So we asked conference attendants to “temporary donate” a device to the ODL – but also accepted permanent donations together with the promise to route these to ODLs. @derPepo‘s Donation now is sitting at the growing Düsseldorf ODL, which has been initiated by conference organizer Marc in beyond tellerran-ddorf™ right after the conference.

The idea of Open Device Labs arrived in the minds of around 400 web workers. The ODL Frankfurt/Main has been present on site sharing their experiences, and we frequently heard people reflect “what a cool idea, let’s start something like this!”. Mission accomplished for LabUp! on these two days! And I am really looking forward which other effects result from the ODL at beyond tellerrand 2012 in the future.

As mentioned building the lab proved to be tricky. Since I want to support others to establish similar on conferences I tried to collect our experiences with this blog post. Call it the recipe for a conference ODL. And please, season to taste! ;)=

Checklist for a Conference ODL

1. Exhibition space, suggested furniture
2. Power supply
3. WiFi
4. Devices – the starter package
5. Trustworthy check-in/-out-process, security
6. Communication & the “what-if?”
7. People

1. Exhibition space, suggested furniture

I suggest to place the ODL in a comparable far corner of the exhibition, or even in a separate (lockable) room. Get some sturdy tables providing a space as deep and wide as possible. You don’t want anybody to accidentially tear down a device or spill a drink over the hardware. And since you expect more than one person to work in the ODL at a time, plus spectators, plenty of space makes total sense!

Depending on the location and the audience of the conference you might want to look into differents options to make people stay away a minimum distance from the tables. With deep tables people already need to stretch out to reach the devices, so this is something we found to be sufficient to keep an overview. This is a wide field, ranging from a colored duct tape bar on the floor to barrier tape or securities – it’s totally up to you how to deal with your local event.

In Dusseldorf we built a table area approximately 4.5 meters wide and 2 meters deep covered with black cloth, and we placed the devices in the back of that table. In the resulting free area of about 1.5 metres we placed friendly signs asking to first contact ODL staff before reaching out for a device. We also had a cocktail table hosting a laptop (running Edge Inspect to remote control and debug the devices) and placed a couple of separate cocktail tables for the ODL staff and individual meetings and chats around the ODL.

Running a Conference ODL
The Open Device Lab at beyond tellerrand

It makes sense to acquire appropriate stands used to put mobile devices on display. In the meantime a number of funny and/or useful ideas for device stands have popped up, and not all of them have to be complicated to build or expensive. In our case, we decided on spending 35 euro in the local hardware store and to pop together some super-simple L/U-formed wooden shapes (see pics). To be precise, we built 9x 1 meters of that.

Pretty sufficient for a maximum of approximately 80 mobile devices and, in total, a very comfortable and secure work environment.

2. Power supply

Looking through the eyes of conference attendants the ODL is also a charging station for devices. Temporary donations happened purely out of this fact, so emphasize on that! ;)= And now you know: you will need proper power supply for a pile of devices!

On one hand, we brought the chargers that came with the devices we supplied. Added to that, the super-friendly guys from Cambrionix roped in two awesome 16-port USB chargers to support our ODL (free of charge – which reads a bit odd in this context, haha). If you build your own ODL make sure to reach out to Cambrionix, e.g. via Twitter, and say hi from us at LabUp!

Obviously you will need extension cords and enough multi-connectors. We brought ten 5-port multi-connectors with each 2.5 metres extension, and thought this is far too much. Actually we ended up using them all.

Cambrionix 16-Port Charger currently powering physical CSS Unit measurements
One of the two awesome Cambrionix 16-Port chargers in action, currently powering physical CSS Unit measurements

3. WiFi

The rise and fall of the whole show. I hope I do not need to elaborate on why you should never, under no circumstance, rely on a conference-provided WiFi. Only the absolute minority of conferences will leave you with a stable and reliable WiFi plus approproate IT guys on site that are both competent and capable of acting to provide you with the needed separate subnet. Why I suggest a separate subnet, ideally on separate hardware? OK, so if you want to do synched browsing and remote debugging it will be much more comfortable to do so with having all devices on the same network. How many devices can you hook up in an IPv4 subnet? 254. Which WiFi is capable to manage 254 active wireless devices? None (at least none of the affordable ones). So what? Bring your own WiFi and make sure you make all necessary arrangements on a powerful Internet-uplink with the local IT people well ahead of the event!

We cobbled together a motley crew of SoHo accesspoints: a D-Link DIR-635, the good old Linksys WRT54GL running dd-wrt, plus an Apple Airport Extreme. The Extreme has been used to switch the copper uplinks to the other two routers – we did not “Bridge”, we brought up three separate SSIDs. DHCP and NAT has been provided by the infrastructure of the venue, which actually served us with an excellent IT support in preparations and execution of the conference ODL. As said, and spoken from the perspective of a frequent speaker at conferences, this will stay the exception of the rule – and even here we still needed two long telephone calls to make sure the local crew understands what we are planning to do and what it means when 50-100 devices in synced browsing synchronously fire their sets of requests and suck on the venues bandwidth… ;D=

We distributed the accesspoints evenly under the tables and made sure we had set non-interfering radio channels. Having that said: arrange with of other locally present WiFis, use a scanner for that. And recheck on the day of the conference when all boothes are set up, especially when you have been setting up a day or so ahead! It also makes sense to raise awareness at other boothes and arrange agreements on shared WiFi usage, so people do not behave as usual and wildly throw open MiFis and whatnot, until everything goes down in overload. As usual. ;(=

We then connected our devices well distributed across all three SSIDs and made sure to set every accesspoint and supporting device to the absolute minimum transmitter power. We only wanted to span about a meter or so (from desktop to accesspoint below desk), so why pollute a wide range with our signal? You will have got the point in the meantime. Oh and by limiting range of your WiFi you also prevent any of the geniuses sitting in the conference to switch to the much-more-performant ODL-Wifi (don’t expect password to stay secret due to temporary donations) to do what people usually do at conferences: sync Dropbox, have 100 tabs open, check for app- and system updates, permanently receive push-email with full attachments, watch video… you know, that kinda important stuff. %((=

Let me emphasize on that again: do not underestimate the importancy of the WiFi and have a backup plan! There is nothing more stupid than gathering 100 or more devices only to find out you do not have sufficient connection or bandwidth to fuel them all.

In our case the backup plan sucked: we would have had some MiFis; booo, hiss. What we found out on location was, that a simple 50 meters ethernet cable thrown to the location next door could have saved our asses if the unexpected would have hit us. Lesson learned: a good plan well ahead of time helps. Have such!

Tamagotchi Galore
My “donation”, worth about 3.500 Euro, about to be sent into the forest. I brought another five devices in my handluggage and a total of 11 chargers to the ODL, but at nighttime in the hotel I had an empty phone and no charger at hand… ;o)=

4. Devices – the starter package

An Open Device Lab without devices is an “Open Lab”, at max. So: bring your devices! Don’t forget to acquire devices from people that are not directly involved into organizing the ODL and to tell others about that fact. And do so before the first conference attendant is forced to think about leaving his or her iPad – in front of an empty desk – or better not… By providing a critical mass of devices you clearly send out signals that you mean it. Especially if these are YOUR OWN devices (or those of well known others). ;)=

Since most people do not carry a gaming console or Smart-TV to a conference: evaluate if and which people can add value by adding such devices to your ODL, and organize transportation well ahead of the event.

Same for a central Computer to control the lab, for remote debugging or simply to compare simulators and emulators to the real device! Best if connected to a strong projector or, as we did it, to a monster-LCD that has been luckily available at the venue. In either case, bring a very long video cable – thanks to Erik for ripping his home TV set for our lab!

Another Computer and perhaps a printer can also be very helpful – compare the paragraph on security.

Another aspect to keep in mind: have your devices configured as actual test devices. This either means that all data and accounts sitting on the devices are not worth a dime to you, or that you removed all delicate personal information and accounts (such as to stores and markets) – ideally ahead of the event. Of course you can still restrict devices to be available for ODL use in a “don’t touch”-mode, which is still super-useful if you consider synced browsing and remote action. Again, compare the paragraph on security.

Tag your gear
Tag your gear – it is easier to identify who brought what

Not restricted to, but especially your personal chargers and charging cables you plan to bring to the lab should be clearly marked to be easily distinguishable when disassembling the ODL after the show. You can use self-adhesive colored paper dots for that. Or use any tape and color-dot the tape, as I did. In addition to that each of us spread out all his gear and made pictures of what he brought to the lab, which have been sent to everybody in the team ahead of the event. By doing this it was totally easy to disassemble and route the gear to the right box to have it returned to its owner, and it would have even been supereasy with the respective owner missing at teardown (hey, quite possible!).

In any case just make sure to mark your gear in *any* appropriate way – check the next paragraph for more background on that.

5. Trustworthy check-in/-out-process, security

If you had planned to pop up at the conference exhibition with a sign saying “GIMME YOUR PHONE” …well, don’t expect that to work. To validate your concept simply warp your mind into the perspective of somebody, that has never heard before about what you’re up to do, and that passes your booth at the day of the conference. Now that you are looking through the eyes of your target audience: what would *you* need to find to be convinced that you can totally leave your beloved device(s) for quite some hours, or even over night, to potential complete strangers, to serve the greater good?

Here is what we thought we‘d like to see:

• (a minimum of one, better…) two permanently present as staff
• more precise: Staff that leaves a solid impression of being capable to have an eye on gear worth 25, 30, 40.000 Euro (since you’ll very easily hit a number like that)
• a sophisticated Check-In/Check-Out-process and staff able to explain that process
• easy rules, e.g. what happens in case of damage or loss?
• a proper registration and tagging of any left device, to eliminate the risk of mistake on device pickup
• “privacy level”, a possibility to define to which extend a device can be touched/used by visitors of the ODL (e.g. if only in remote controlled use or free to move from hand to hand to even reset/restore and/or install software)
• a receipt about any devices (temporarily) donated to the lab
• (optional:) a reward!

Button "Device Donator"
We handed out these sweet “Device Donator” buttons to people that helped the ODL at beyond tellerrand forward. Thanks to Jacci Schepers for the design! (I still have buttons on stock. If you plan to run a conference-ODL I am happy to send you some)

In addition to explaining our process to attendants at the event we communicated the whole idea and check-in/out-process well ahead of the event, via an e-mail-newsletter as well as the event microsite (also compare next paragraph on communication). Regarding the on-site-explanations to visitors: make sure to have your staff do dry-runs in explaining the process to each other, as if they were talking to real donators. This is the easiest way to make sure everybody has got it the right way, and clarification can be given easily without disturbing anybody in public. Remember the pricetag of the gear you’re after!

Our Check-in/Check-out Process

Everybody that showed up at the beyond tellerrand ODL to check-in devices has been asked for their personal data (full name, e-mail-address, cellphone number, Twitterhandle etc. to stay in easy reach over the conference). We tracked that data in a written list and issued a unique number for every (temporary) device donation. For each number we made several self-adhesive labels using a thermal transfer label printer, and placed one of those on each item the donator left at the ODL (device, charger, cable etc.). Another identical label has been glued to the conference badge of the donator.

The label contained the donators name, the unique number as well as the “privacy level” (the extent to which the specific device could be used or handed out to others), e.g. the label just said “private” or “public”. Additionally we placed “private” devices in their own corner in the ODL so staff would less likely accidentially run in danger to hand these out.

At check-out people needed to show the label together with the conference badge and name the requested device. Our staff checked this information against our list and the labels on the devices. Donators verified their hardware to be in correct condition and certified receipt by signing our list. It was up to the donators if they either left the label proudly sitting on the devices, or if they chose to remove it free of residues (you want to better test your label materials for that!!).

Donator sticker on device
The sticker tagged the donation itself. It served as an ID and clearly told the personnel to which extent the device could actually be exposed to public testing.

Of course you could even extend the security level, one of our ideas had been to use a webcam to take a picture of the donator together with the donated gear. Depending on which possibilities the make and data of the conference badges provide (barcodes, RFID etc.) you could also leverage other hooks. Anyhow, we decided the above to be OK for our specific event, as you might decide on your local flavor.

As a “thank you” for (temporary) device donations we presented each donator with a pretty unique button to attach to his/her lanyard. Lovely Jacci Schepers designed the buttons for us which have been made for a few bucks ahead of the conference – it’s worth the invest (next time I plan to produce stickers as well). I still have buttons left, so if you want some for your local conference ODL just holler at me and I might send you some.

Keep in mind that the ODL staff will have reason to leave the lab from time to time – if it is only for the most natural reasons you could imagine. Probably these people need to eat, too, so have a plan for that and make sure to have enough spare personnel (such that knows the processes and is able to explain, not only “taking care for a moment”). Plan for sickness and other unexpected stuff as well!

Should you plan to establish your conference ODL for more than one day, make sure you have organized a secure overnight storage for all the gear you and others brought in. And plan staff situation for dismantling the lab – also for the overnight break (when everybody is totally tired, eventually a bit drunk, and just wants to go home…). Again: have a plan and things tend to go well, don’t have one and end up loading boxes into your own hotel room, alone, tired, in the cold, at 2am. Got it? ;)=

6. Communication & the “what-if?”

Definetely make sure to elaborate better too detailed on what you plan well ahead of the event. Explain, why and how all this is meant to happen. Why you think it makes sense to participate and support by (temporarily) donating devices, and why this is cool and safe to do. The conference website is a good place for that, maybe you can even write a small blog post or interview for the conference newsletter about your ODL, or the conference supports by tweeting and posting about the ODL ahead of the event – that is golden stuff. In any case: include a contact address for questions. With this you ensure people can ask questions if in doubt, give feedback or even offer support.

Also make sure to communicate clearly who is the host for the ODL – make sure people can easily see who feels responsible for the whole gig.

Another important point: talk within the team and define what happens if something breaks or gets lost. Who steps in, to which amount, for resulting damage?

We have been totally lucky with that and were able to win the conference host for that. The benefit of having the ODL at beyond tellerrand weighed in for Marc to take over any eventual risk out of damage or loss for all gear on and below the tables. Done deal. And a good one if you ask me – consider offering so to “your” conference host.

The baseline of the last recommendations: speak about eventualities *before* stuff goes south – not *after* that happened. This includes, if that should be your result, to clarify to attendants that participation at the ODL of any kind happens at their own risk (which is not helping to convince them, but it helps you to preserve freedom).

7. People

Maybe the most important part with such a project is the people involved. This first conference ODL would not have been possible without Daniel Connerth, who built the device stands, codesigned the buttons, helped to install the ODL at the venue and staffed it for full two days. Timm Jansen contributed just as passionately to the planning, the installation on a sunday as well as staffing and upkeep of WiFi and setup of the ODL for full two days. Just as Erik Sixt, who also brought in valuable private gear, but foremost a lot of passion, excitement and spare time into the project.

Sven Wolfermann, in a keen act of fearless trust, sent the majority of his device collection and chargers into a forest near the german town Krefeld (and so did I), where conference host Marc Thiele added a laptop, printer and some own devices and brought them to the venue. Marc is also the guy that gave the ODL exhibition space and all other needed local support for free. *And* he is the guy that I call ahead of every event he is organising, to brainstorm and to make sure we use available and nonavailable budgets in a way that generates the most valuable takeaway for the community.

Without playing our own trumpets too much, I feel we did not do too bad this time establishing the conference ODL @btconf. Thank you guys – you are the best! Let’s repeat this!

Jay (@klick_ass) and Sven (@maddesigns) at the @btconf-ODL
Sven (to the right) and Jay at the beyond tellerrand Open Device Lab


The ODL at beyond tellerrand has been a ton of work, but foremost it has been a ton of fun. The idea of Open Device Labs and the necessity of testing on *real* devices has been communicated in the best possible way to about 400 attendants and their personal and social media networks. One and the other bug has been found during testing, which ultimately moved forward the user experience. And that is what this is all about.

What remains is the hope that this wrapup serves as a starting point for other conference ODLs. Please have fun doing so, and please let me know if you do so. If you should decide to even frequently establish a conference ODL (e.g. like our own Berlin Desknots), these labs would be called “Virtual Open Device Lab” and as such, among “resident” and “mobile” ODLs are listed at OpenDeviceLab.com.

Affordable WiFi Access Point capable to support 50-100 clients (wanted)

When you’re running a device lab to test across a variety of internet connected (mobile) devices, a wireless local area network will be your primary way to hook up your gear to the ‘tubes. When you’re taking that device lab rather seriously and you’re testing across, let’s say, more than 30 devices, you will quickly run into a problem: your WiFi.

Don’t believe the tech spec hype

Some manufacturers publish tech specs stating the maximum connections their access points are capable to support. Yes, most don’t even do that (or talk about the “number of people that can share the same internet connection”), and there is a reason for that. These numbers might be true in some ideal scenario (like: all connected devices using the same chipset, behaving in mixed conditions (some idle, some active), all in vital shape), but having tested a number of these SoHo-style devices we all tend to use at home and in small and medium businesses, I can tell these numbers are very optimistic. At least for the use case we’re after, and that, to be fair, might not be the scenario the manufacturers meant when they published their numbers:

The use case is a tough one

Synchronized browsing, used in web development to easily preview and debug code in production across a farm of devices, implicates X devices calling the same URL at more or less the same time, sometimes several times a minute (code, preview, debug, refresh). There are a lot of variables to take into account and a lot basically “depends” as a rule of thumb around this topic ;). For illustration purpose imagine the traffic produced by 50 devices calling a webpage with 30 requests and a 0.5-1 MB pageload, refreshed continuosly – do the math. That is most likely not what the makers of that WiFi-gear had in mind when they were talking about the number of clients.

A number of mobile devices combined to a device lab
How does your WiFi gear like more than 30 devices?

I cannot find gear that is suitable for the above scenario and affordable for individuals or small and medium businesses, that run (non-for-profit open) device labs. The available product documentation is not comparable (enough). I know there is superexpensive gear used for permanent installations or at events, but this is not even close to the budget range of what I am looking for. I am not a wireless networks expert, and most of the people would agree this to be a black box to most of the typical web or app developers. And the experts I asked also only know the superexpensive gear (and actually don’t know talk too precisely about limitations with the above use case).

There seems to be a huge gap between 30-300 Euro-ish SoHo-style devices and 6000+ Euro-ish gear. Is there an affordable solution, somewhere inbetween?

Call to action

I know that a ton of people is looking for a solution, so this blog post is to find out. Please help, point people that could know more than us to this post, and share knowledge via a comment. If you run a device lab and found gear that does the job, please post your experience and suggestions. If you combined a set of APs to a working solution, please post the details here (I’d prefer a single device for a number of reasons, but, anything is better than nothing).

Thank you!

Update (May 29, 2013 – looong overdue looking at the number of feedback I have received via Twitter and E-Mail in the meantime, my apologies!):