Download the accompanying report at the end of this post to discover more about co-designing education services with teachers.

Collaboratively designing with end-users is core to the way we create new products and services at Made by Many.

We’ve taken a particular interest in the education space for a few years now - partly because we have been lucky enough to work on amazing client projects like Skype in the Classroom and School in the Cloud, but also because the shifts in education - and learning - are so dramatic and far-reaching. Education is long-overdue the kind of big disruption we see happening today. It’s basically been the same since the Enlightenment, and arguably the invention of the printing press. Today, there are a host of market needs to be addressed, real business problems to be solved and opportunities and new experiences to be unlocked by bringing tech and product design together.


Position closed: What the hell’s an embedded storyteller and why are we hiring one?

Medium screen shot 2015 08 13 at 12.38.21
Embedded Storyteller
London, UK

Made by Many is trying to hire an ‘in-house journalist’. The inverted commas are my apology for the horrible term, but job titles are hard. Why are we hiring such a person? The crude answer is to better market ourselves by more deliberately getting opinion pieces and news circulated. But the longer answer is more interesting and I suspect it’s a trend that is picking up across the industry.


Getting started with Swift and WatchKit

Medium onwristnoannotation

In the second of my blogs on Swift I will look at WatchKit for the newly released Apple Watch. This will involve adding Watch functionality to an existing project, the Hackaball prototype app. Hopefully some of the solutions to problems found on the way will be of use. Version 6.3.1 of Xcode is used.

For an excellent overview of technologies in the Watch, check out the blog by my colleague Alex Barlow.


Replacing Rails: Part 2 - Amazing Tooling

Medium gopher

I come from a compiled language background (C, Objective-C) and I've been thinking for some time now that Rails isn't always the best tool for the job. Memory usage, performance, deployment and too much "magic" are an example of some of Rails' weak points, points I find to be of great importance in the larger scale apps I've had to write or maintain.

I remember reading the initial release of Go and being excited! A statically typed language with garbage collection, a compiled language where concurrency is a first class citizen and a standard library which has everything you could ever need, 90% of what you need is already there.

Here's the workflow and tooling I've been using recently with Go.