Saturday 18th August, 2012
Week 1871 was split pretty evenly between our client work and our internal projects. I’ll try to pick out some interested moments from each.
Sitting comfortably? Yes?
Then I’ll begin.
Roosmarks and the IndieWeb movement
Chris has been doing a bit more work on his self-hosted bookmark/research tool currently known as “Roosmarks”. Aside from scratching his own itch, he’s also very interested in the idea of self-hosted web applications. These are applications that you, the user, host for yourself, as opposed to applications like Twitter or Facebook or Flickr, which runs on a central shared server2. It turns our there’s a movement – called IndieWeb – all about this kind of approach.
There are plenty of reasons why you might want to host your own content, normally centred around ensuring that you control its use and can always retrieve it. The most obvious reason you might choose a centralised service instead is that you have to care about keeping the application running.
Earlier this week we spent some time talking about whether or not we could work towards our company goal using a self-hosted product. It’s clear that the market for a self-hosted application is much smaller than that for a “regular” app, but is that because people don’t care about their data, or because they don’t have the skills or interest to run an application themselves? Or something else? Or all of the above?
Can you imagine self-hosting an application? If so, what kind? If not, is it because of the hassle, or because you think the advantages of a hosted service outweigh data freedom concerns?
Decoupling Harmonia from Rails
The original version of Harmonia is barely an application, let alone a Rails app, but the next version is slightly more ambitious, and will require a web interface of some kind (although that may not be the only kind…).
As I mentioned last week, I’ve been working on some of the core domain logic, but without any framework or interface. This week, Chris and I started to investigate how to bring persistence (via ActiveRecord) to the objects I’ve built, but without introducing coupling between the framework and the clean objects we already have.
After a few hours of head-scratching and a few false starts, I think we’ve found a simple approach that I’m happy with. I’d love to go into a bit more detail, but I think I’m going to wait until the choices we’ve made have a chance to prove themselves (not to mention the valuable input of Tom and James M).
All I’ll say for now is that the key is extracting value objects and adaptors. More on this later I hope.
At GFR we’ve been printing with some of our friends since April, but if you have been waiting for a packaged product, your time has come. This week, BERG opened up pre-orders for Little Printer. Welcome to the party!
Obviously I have a few thoughts.
The Price Is… Right.
If you happened to be sampling the twitters, you’ll be aware that some of the discussion was focused on the £199/$259 price tag. I wasn’t surprised by this reaction to the price; to be honest, it was more than I had hoped too. But I understand why it costs what it does.
If the components to our own far-simpler printer cost around £90, then even considering bulk discounts, it can’t be surprising that in order to build a well-designed and beautifully-manufactured wireless device, and produce & support the polished software to support it, that a company hoping to make a profit would need to charge a little more? I’m sure BERG would love to be able to sell the product for less, and perhaps as they make progress with their longer-term plans3 they’ll be able to start benefiting from the cost savings of manufacturing at scale.
There’s a Kickstarter project called mPrinter which claims to be able to build a wifi device for $100, and without investing tens of thousands of dollars into tooling. Based on my own experience and observations of Little Printer’s journey along with others trying to make physical things, I’ll be very surprised if they can. But, of course, I could be wrong. If there is a way to make these devices at that sort of price, I hope they’ll explain how.
Next, a common misunderstanding about what these things actually are.
Ceci n’est pas une Printer4
Having spent more than a year pottering around with this stuff, one of the most common misunderstandings I encounter is that these devices are printers. I know, it’s confusing; they all say printer in the name after all.
A few people have asked about using them to print documents, or whether or not what we (or indeed BERG) have built is similar to Google’s Cloud Print, which also lets you send content to printers over the internet. Thinking about these things as printers – or at least as printers in any way similar to the thing in your office – is, unfortunately, missing the point.
Maybe it’s only when you’ve actually held some of the diminutive content in your hand, played with it, that you really understand what the point is:
That they are printers is not interesting. It’s what they produce that is interesting. Small bits of personalised content that you can easily hold in one hand, or fold into a pocket or wallet or notebook.
“Reverend” Dan Catt makes the same point. Yes, you could access all of this on your smartphone, but to assume that any other medium is therefore pointless is to ignore how context affects the way we relate and interact with information.
It’s all about the format and the content.
As I’ve tried to emphasise in our own project, what is going to be really interesting is exploring the range of content that could be useful or interesting or delightful in this novel format. A significant amount of BERG’s energy has clearly gone into developing and refining their own ideas about what works in this format, but there is doubtless much more that could be done.
And what of our Printer?
One side effect of the buzz around BERG’s announcement – positive or otherwise – is that our own project got a bit of a boost. Here’s some analytics information reflecting the number of visitors to this site recently:
We haven’t really decided what we’re going to do with Printer yet5, but for the moment it still makes a great open-source alternative. I have plenty more that I’d like to do with it; it’s just a case of finding the time.
Until next time,
– James A.
Printer is only one of the projects that we are working on internally, and it’s not clear at the moment how it might be able to address our company goal – in part because of exactly the amount of effort BERG have had to put into Little Printer to get this far. Shipping atoms is hard! ↩