The Social Mobile Long Tail 2.0

A few months ago I finally got round to diagramming what I thought mobile applications development in the not-for-profit space looked like. I came up with this, and called it “Social Mobile’s Long Tail“. It was based on the original Long Tail concept, first talked about by Chris Anderson in a Wired Magazine article, when he used it to describe consumer demographics in business (something quite different).

(A larger image is available via the kiwanja.net site here)

My thinking was this. Looking at the mobile applications space today we have a number of high-cost, well-publicised, large-scale mobile-related projects which tend to cover national (and sometimes international) needs. These “large” systems play a crucial role in helping larger bodies, sometimes as big as government departments, provide mobile services to their target audiences. They are generally aimed at the higher-end of the market, where only the larger or resource-rich NGOs reside. Way out there on price, complex to develop (assuming you wanted to) and near-on impossible to replicate, they’re almost completely out-of-reach of your average grassroots NGO. These applications and platforms sit in the red part of the Tail.

In the orange section we move into the more mid-range systems – solutions developed by individual NGOs for a specific need, campaign or project. These are generally less complex, which makes their chances of replicability slighter better, but still difficult for many grassroots non-profits with few technical resources or hardware at their disposal.

Finally, in the green section – the truly long part of the long tail – we have the low-end, simple, appropriate mobile technology solutions which are easy to obtain, require as little technical expertise as possible, and are easy to copy and replicate. From my own experiences the number of NGOs present in this space is by far the greatest, making it the area to focus on if we want to create the highest amount of mobile-enabled social change. Add up all the value here, and it easily outweighs the rest along the higher (more lucrative) parts of the tail.

I use this diagram in many of my conference talks and presentations, and it seems to go down very well. It was interesting to see some of the staff at Nokia Research, where I spoke last month while I was in Palo Alto, grabbing their camera phones to snap a picture of it. I’m always thinking about ways I can refine it though, and Jim Witkin – a colleague – suggested adding an extra axis. This is now the one on the right, representing the number of NGOs in each of the Long Tail segments.

There are probably better ways of depicting this, but for now I’m happy with this. Suggestions, however, are always welcome.

Three years on, but still some way to go…

I’m writing this from seat 7D at exactly 38,000 feet somewhere between Forssa and Cambridge. Normally seat 7D would be in first- or business-class, but unfortunately for me I’m on a Ryanair (low cost airline) flight. Nothing fancy here. I’m returning from a short combined work and pleasure trip to Finland, where exactly three years ago I was knee-deep writing the first version of FrontlineSMS.

It was ‘seat of the pants’ stuff back then. I remember giving a very early interview about the software to Charity Times, even though it was only a third complete and it wasn’t totally clear what it was or wasn’t going to do. If that wasn’t enough, I was also asked for a URL so people could go online for more information. “Of course”, I said. With no website yet in place, programming was quickly put on hold for an afternoon while one was hastily deployed. In the absence of an obvious graphic to use for the main banner, and no logo to speak of, I took the liberty of taking a photo of the forest outside (the same forest I used to stare into while trying to decipher numerous unfriendly VB.NET error messages). My forest banner – which did resemble something of a ‘frontline’, I guess – held firm for two-and-a-half years until it was finally replaced when the new website – properly planned and commissioned, I hasten to add – went live in May.

A lot has changed in three years, and we’re not just talking website banners. The initial launch, back in late 2005, went largely unnoticed. I remember spending my evenings trying to identify people who might be interested in writing about it, but it was new, was written by somebody nobody had heard of, had no users, nobody knew if it worked (not even me, to be honest) and nobody knew if anyone would want it. Talk about an uphill struggle. Mike Grenville at 160Characters was the first to see some potential in it, and his post got the ball rolling. A few other sites followed suit, most liking the thinking behind the program more than the program itself. Things slowly began to move, and a few enquiries came in from here and there. One was from Kubatana, who have the great honour of being the first organisation to take a punt on FrontlineSMS (they still use it to this day). Significantly, another email was from the MacArthur Foundation. The huge significance of that mid-November telephone conversation with Jerry wasn’t to become apparent for another year-and-a-half or so.

Today, news of the latest version is effortlessly working its way around the web and my Inbox is regularly hit with NGO and press enquiries, people wanting to know if they can help in any way, and a stream of messages of support (there are one or two negative individuals, but luckily they remain well in the minority). There are some great, hugely supportive Blog posts out there, including those by Erik Hersman, Mike Grenville, Sanjana Hattotuwa and Clark Boyd, but also some insightful, short and unusual ones. FrontlineSMS is work in progress, and people seem interested enough to want to come along for the ride.

Cellphone 9 described FrontlineSMS as “The NGO Twitter”, while Unthinkingly thought it was “a thoroughly wonderful idea in many ways … If you’re into international rural research with mobile phones. A tool worth watching very closely, it’s what I think is the leading platform of the mobile research ‘industry’ if there is such a thing”. Chromosome LK won the Dramatic Headline competition with their “FrontlineSMS and Sri Lankan Gays” (referring to its use in Sri Lanka by a gay rights group), while Aydin Design decided that one of the really exciting things about FrontlineSMS was “the speed of development – with low resources, putting it in the hands of people now – so they can do things to improve their lives – now”, which is exactly what it is trying to do. Isis-Inc – who’s strap line is “Technically, it’s about sex” (?) – concluded their coverage with “Yay FrontlineSMS!! Access meets elegance!!”.

It was Clark Boyd, however, who hit the nail right on the head when he wrote:

Today, FrontlineSMS announced version 2.0. To get a handle on what goes into this, think about it. This platform has to work on hundreds of different handsets and modems, and in languages ranging from Swahili to Cantonese. And it needs to work with Windows, Mac and Linux. Not child’s play, and not something that’s been done with millions of dollars of backing from major funders

Not one to sit on my laurels, I’m already working on ideas for the next version of FrontlineSMS, and a number of exciting related initiatives, with the support of another major US foundation. FrontlineSMS is a major step forward in kiwanja’s efforts to build affordable, appropriate technology solutions for the grassroots NGO community.

But we’re by no means there yet…

FrontlineSMS gets active

FrontlineSMS has so far managed to achieve quite a lot with really very little, but that’s about to change. After two-and-a-half years of promise, it’s finally beginning to look like the software I dreamt of that wet Saturday evening in Cambridge back in early 2005. I’ve spent the past week putting six months of development through its paces, whilst writing the new User Guide, and am as excited as ever about what this thing can do. One of the most exciting new features are things we’ve called “FrontlineSMS actions”. Here’s what they do.

“FrontlineSMS actions” are triggered by keywords which arrive via incoming text messages from patients, farmers, staff, fieldworkers, members of the public or whoever. Once a keyword or phrase is detected, FrontlineSMS can be told to do one of a number of things. These are our “actions”:

Auto Reply
FrontlineSMS will automatically send a pre-determined SMS back to the sender of the message (maybe a “Thank you for your message”, for example, or clinic opening times, or the current price of matoke)

Auto Forward
FrontlineSMS will automatically forward the incoming message to all members of a pre-determined Group. This can be useful for users who want Group members to be able to contact each other via SMS with latest news, or with urgent announcements (Auto Forward does a similar thing to Twitter)

Join Group
FrontlineSMS will automatically add the sender of the SMS to a pre-determined Group. Again, this is useful for users running a series of user Groups or clubs, and who want people to be able to join automatically by publicising the keyword without them having to make direct contact. A campaign, for example, could say “To join our Control Arms Campaign, text in the word JOIN to 123456789”

Leave Group
Members of Groups can leave any time they like by sending an SMS with a pre-determined keyword or phrase (for example, LEAVE GROUP)

Survey
Allows the running of competitions, Surveys or the soliciting of opinions from people. Any time a message comes in which starts with the pre-determined Survey keyword, FrontlineSMS will keep track of it and allow all responses to be analysed in the SurveyAnalyst module. Surveys or competitions could ask people, for example, to text in the word OPINION followed by their opinion on a certain topic or subject

Email
Keywords can be used to instruct FrontlineSMS to automatically forward an incoming text message to a pre-determined recipient, by email. This might be useful if a Project Manager, or someone in a different country or office, needs to receive emailed details of incoming Survey or campaign text messages, or if users want their messages to be backed up in an email system such as Outlook or Google Mail, or held somewhere for wider forwarding

External Command
To provide maximum functionality, keywords can be set up to trigger the running of external commands or programs on the computer (for example, a batch file or a script). Advanced users could write a batch file which finds out how much free disk space is left on the computer, for example. An incoming SMS with, say, the keywords FREE SPACE could then be set to trigger the running of this batch file, with FrontlineSMS texting the result (i.e. the amount of free disk space) back to the message sender. The External Command function can also be used to instruct FrontlineSMS to send incoming messages to remote servers over the internet, which may be useful as a method of backing up data, or for a website with a news ticker which needs to display all incoming messages for a campaign or event

As I speak – or should that be write? – FrontlineSMS is being tested by around twenty-five NGOs. Over seventy requests to use the new version have been submitted via the website in the past three weeks. Right now we’re just ironing out the last few kinks before we make it more widely available to the NGO community. These are exciting times, and going by the feedback we’re receiving, we’re not the only ones getting excited…

FrontlineSMS comes of age

Two-and-a-half years in the making, FrontlineSMS is finally shedding its Beta status and will soon, finally, be launched to the NGO community as a fully-blown product. Although it’s taken much longer than I’d have hoped, at least we’ve had ample time to listen to the users and got the clearest possible indication of what we needed to add, remove, tweak and improve to make it more useful and relevant. The Beta – proof-of-concept as it was – naturally had its problems, but thanks to a great team of developers the new version is on target to exceed even my own expectations.

We’re still in Beta in the new release (but at least it will get out of it this time!) and things are still a little rough in places. Many of the finishing touches are scheduled for later in the development cycle, but the software is already beginning to take shape and neatly builds on the current FrontlineSMS look and feel which we know works well.

Here’s a sneak preview of just a few of the things we’ve been working on.

We’ve built two user interfaces in the new version – a Classic and Advanced view – allowing the user to determine how much functionality they want to be exposed to. Beginners will be happy with the Classic, which looks and feels pretty-much like the current release. We’ve also added right-click menu functionality, making things quicker, easier and more accessible throughout, and ‘handles’ which allow different elements of the screen to be expanded or reduced in size depending on how much the user needs or wants them.

 

A choice of database options are now available, allowing incoming and outgoing message data to be read and shared by other applications. Incoming messages can also be ‘posted’ automatically to web servers, or passed to other running programs which can then deal with them independently. There are also improved data import options allowing, for example, groups of contacts to be easily brought into the database, with generated message data more easily exportable from a number of modules in a number of popular export formats. One of the problems with the current version was that the data, useful as it was, wasn’t easily accessible by anything other than FrontlineSMS. Not quite so useful.

Device installation and configuration is now largely automated in the brand new PhoneManager module, with auto-detect and auto-configure functionality. FrontlineSMS scans the host computer, looks for modems and phones (which can be internal devices, or connected via USB or bluetooth), determines whether they’re any use, and then sets them up if they are. Multiple devices can be used at the same time, and each can be configured exclusively to send messages, or purely to receive, depending on what the user requires. A wide variety of GSM modems and phones will be supported at launch, with simple driver creation possible for new devices as they hit the market. Long gone are the handset headache issues of version 1.0

Additional functionality includes support for SMPP, which will allow messages to be blasted through SMS aggregators such as Clickatell. This will make it possible to send large numbers of messages far more quickly and cheaply than via any attached device, if and when an internet connection is available. The new FrontlineSMS will also be platform independent, so Mac and Linux users no longer need feel left out.

Of course, this is only half of the project. A team at Wieden+Kennedy are working hard to re-brand the software and build a simple, functional, accessible website, work which is also going fantastically well. But that’s the subject of an entirely different blog post altogether…

All of this work – the application itself and the website – will be publicly launched on 8th May at Global Messaging 2008 in Cannes, where I’ve been invited to give a keynote speech – “Mobile messaging as a means of empowerment: How has SMS been harnessed by NGOs around the globe?”.

Two weeks later, 22nd May, sees FrontlineSMS feature as a finalist in the Stockholm Challenge where it’s been selected for its use in monitoring the 2007 Nigerian elections. The project then enters a new phase on 1st June as the MacArthur Foundation funding ends and a new grant from the Open Society Institute (OSI) begins.

I’ve always felt that FrontlineSMS had a huge amount of potential. Thanks to a dedicated team – supporters, users, developers, bloggers and donors among them – we may soon start to see it.