Via Mr Falletti, I notice that the BBC have posted a review of the Facebook check-in project we ran for them at the Radio 1 Big Weekend, including a load of video footage with attendees. As he says, it's very frank and complete:

"Even though we had some initial teething issues, the research from the audience and on site analytics showed that the audience really liked sharing their unique experience with (or bragging to) their friends.

We had large interaction spike from the news story posts from seeing a high number of 'likes' and 'comments' on each of the check ins. This interaction was exactly what we were trying to achieve and it really worked. Interestingly, the stats also showed that more women engaged with the product rather than men - something that needs to be investigated further - does social syndication in this way appeal more to women than men?"

Really enjoyed UXCampEurope. I've attended a couple of the London events, and got a lot out of each one, so was quite happy to have an excuse for a weekend in Berlin... And wasn't disappointed.

From the moment we arrived, it was all very smooth. A great venue on the outskirts of Berlin (slightly awkward to get to by S-Bahn, but not so much that it derailed anything), huge and light; excellent food; and great facilities. A couple of the rooms got quite crowded and could have done with better air-con, but that's probably more a comment on the popularity of those sessions than on the venue.

There was a good selection of talks; a couple of times I was forced to skip one I really wanted to see (like Eva-Lotta's sketching workshops). Maybe one fewer room would have forced us to fill all the available time-slots instead of spreading out and leaving too much choice... Amongst the talks, there was a heavy emphasis on Agile/UX, and also on tool use: lots about Axure, and a couple referencing Balsamiq.

Highlights for me were the two sessions run by Anders Ramsay on user stories (wonderful analogy: software development is a restaurant, with the kitchen being development and front of house, UX) and the design studio workshop. Honorable mentions to Design For The Toilet, an examination of and call for data-driven design to the exclusion of our own instincts, which the speakers ably demonstrated were wrong; and an examination of a recent redesign of Doodle, one of my favourite web services.

Eric Reiss rounded off the first day with a warts-and-all show-and-tell of disastrous experiences running a design agency, and uncomfortable number of which rang bells; and I had a fascinating and intimate chat in the final session, on bringing design to the often code-emphasising world of open source projects.

I wandered up to London last night with Ellen to see War Horse, a rather interesting show based on a World War 1 story, using a variety of life-size puppets. Puppets are Ellen's thing at the moment (she did a couple of shows during Brighton Festival), and I rather enjoyed Flogging a Dead Horse when we caught it last year.

I found the script of War Horse slightly on the mawkish side, and long after having shared a house with an academic who specialised in the subject, I still find World War 1 material challenging in general. But that didn't matter one jot - I was absolutely blown away by the technical mastery of the puppets, the unnervingly lifelike movement ascribed to them, and the playfulness with which they were employed. You haven't lived until you've seen a wheeled mechanical duck get pushed around the stage in a waddling motion, it's eerily articulated neck pecking at the floor.

Over and above the relentless detail of the animal movements, a few moments really hit home: watching a trio of puppeteers slowly withdraw from the corpse of a fallen horse, driving home the finality of its death; one of the cast casually slapping one of the "horses" on the rump during the final applause, to persuade the artificial beast to leave the stage; and the insistent pestering of a young French girl for chocolate. By the end, the animals may as well have been real; their suffering certainly was. And yet they're strange things constructed from wood, wire and leather - not by any means real, they ought to sit snugly in the uncanny valley.

I couldn't help but relate my own empathy with War Horse to some of what I saw Sherry Turkle talk about last week: I *must* hurry up and read the first half of Alone Together, which deals with social robotics.

And Ellen talked about a modern renaissance in puppetry. I idly wondered if something about our relations with software and machines might have trained us, or at least acclimatised us, towards relating better with this particular art form...

We're having an interesting experience at the moment with "operator app stores". We've submitted our Guardian Anywhere app to a couple of them. It's a fairly popular app: 60,000+ downloads, 4.5 star rating, 27,280 active installs and well over 2 million copies of the Guardian delivered through it.

I won't name names. Let's call the operators concerned A and B.

Initial reaction from A when we submitted the app was to reject it, because A can (I quote) "already supply news feeds through its own and third-party services and there is no additional requirement for these type of products".

We've since resubmitted it to A, through their portal which they're using to liaise with folks like ourselves. We submitted it on 30th March, and their site says it should go through in 10 working days. As of the end of May, it wasn't live and the folks at A weren't able to say when it might be (the connection their UK application shop wasn't "live").

Operator B, on the other hand, rejected our submission "due to your app containing ads or links of any sort, which is currently prohibited for applications held within B's app store". I'm still picking pieces of my jaw off my desk.

We have no advertising or other revenue tied to this product - I'm not moaning because we're out of pocket, and my interest in getting this sort of distribution is purely to compare operator app stores to the Android Marketplace.

But it feels like operators are repeating mistakes they should've learned from 5 years ago, and aren't learning from the success of app stores. Launching through them is a cumbersome process with hefty manual reviews and curation. Even a manual review process from Apple doesn't take 3 months, reject your app for containing links, or say "no thanks" because they already have an app in your category.

Update: I've been working on mobile so long that I'm quite bored of operator-bashing. After seeing quite a few folks pick up on this and get busy kicking the operators, I thought I'd try and be a bit more constructive.

I think it all comes down to clear communication: anyone distributing apps should say, clearly and concisely, in a single place, what their standards for accepting and rejecting apps are; what apps they are and aren't interested in; and what their timescales for launch will really be. And then stick to them.

I was feeling a bit twitchy about not having written any code for a while, and I wanted to fiddle with the Songkick API. On discovering that there didn't seem to be any Java libraries for it, I thought I'd write one. Here it is; it's quite limited at the moment (only does Event, Artist and Location searches), but I'm adding to it every now and then and maybe you'll find it useful.