FrontlineSMS introduced to youth group in Kenya

The FrontlineSMS team is always keen to engage with those using FrontlineSMS for social change projects across the world. It is really valuable for us to hear user’s stories, and find out the advantages and challenges of using our software in action. This summer, Tufts University student and FrontlineSMS intern Emily Wyner visited Nairobi, with support from Groupshot and the Institute for Global Leadership, to find out more about FrontlineSMS users in this buzzing city. Here she shares her experiences of helping a youth project get started using FrontlineSMS software.

Throughout my time with FrontlineSMS, one thing has become very clear: effective program design is crucial to successfully integrating mobile software into social change initiatives. I was delighted when given the opportunity to help Plan Kenya (part of Plan International) in piloting their use of FrontlineSMS to help support their local partners.  This was my chance to observe and assist the process of getting started with FrontlineSMS from initial thoughts, plans, and assumptions to final implementation. I have discovered some interesting things along the way, and it’s great to be able to share the beginning of this journey.

My initial visit with Plan Kenya was really exciting. I first spoke with Aggrey and Irumu, members of the Plan team, to give them a thorough run-down of what FrontlineSMS software is and does. They asked some brilliant questions about cost and requirements, and were keen to lay the groundwork for a sustainable project. We brainstormed smart ways to pilot the software on a small scale, such as using it for internal office communication and management or setting up one Nairobi-based youth group with FrontlineSMS to determine if it improves relations with their members.  Soon enough, I was sent onward to meet with Purity and Bernard,  Plan Kenya’s ICT experts. They too were very enthusiastic about the software, and promised to be in touch regarding some of the pilot prospects.

Following this they arranged for me to meet with some representatives from Jipange, an umbrella organization of 16 youth groups in the Embakasi area, and one of the organizations Plan Kenya supports. I went to meet with Jipange accompanied by Purity and Aggrey, as well as Adam from Groupshot and Jordan from TechChange, too. Plan Kenya had set up the meeting in order to discuss and arrange for Jipange to pilot FrontlineSMS in their programming.

Jordan, Adam and I began by giving the members of Jipange an overview of FrontlineSMS.  Along the way, there were certain reactions that really stood out and some really insightful  questions. I particularly remember a young woman named Wanjiru, founder of The Change Initiative, asking whether or not FrontlineSMS would allow her to send text messages to certain groups of people at a time, such as all the leaders of the 16 groups or all the members of one particular group. This led us to explain the suitability of the FrontlineSMS contact groups function for this project. This is the kind of question that is great to hear when introducing a new technology tool.  It asks if FrontlineSMS has the capacity to do what Jipange already does (or needs to do) in a cleaner, faster, and easier way.

This is key;  when a preexisting organization adopts the use of FrontlineSMS, the software should not necessarily fundamentally alter their programming; rather, it is a tool by which the programming can be made more efficient and effective.  For all new users of FrontlineSMS it is necessary to know your target audience, why you are going to reach them, and how you intend on presenting yourself as a reliable, trustworthy communicator.

One eye on technology and the other on program design, the discussion with Jipange continued on with both eyes focused.  More and more Jipange members joined in with questions and comments. People were chiming in with ideas about how FrontlineSMS could be used in good governance initiatives or the formation of a Jipange-run business. It became clear that everyone was set on starting to use the software.

Going forward, Jipange members (and the Plan Kenya staff who work with them) will now be in control of when and how they begin to use FrontlineSMS. They know the basics, there is support from FrontlineSMS if needed,  yet most importantly they have a clear vision of how they intend on using FrontlineSMS for fundamental communication that is essential to their programming.

It will be great to keep in touch with Jipange and their progress with integrating FrontlineSMS into their daily activities. The members I met were enthusiastic and innovative, and it will be exciting to hear about the ways they go on to use FrontlineSMS in future.

Good luck, Jipange and all new FrontlineSMS users out there!  Don’t forget to keep in touch.  One of the best resources we have is each others’ stories.

- - -

If you're interested in using FrontlineSMS for your work:

You can download FrontlineSMS for free here on our website.

You can connect with other FrontlineSMS users and the team by joining our community forum here.

Find out how others are using the software by reading user guest posts on our blog here.

Announcing the "Mobile Message"

Over the past year or so, it's become increasingly clear to us that we need to take the "mobile message" out of its technology silo and make it more available - and accessible - to a wider audience. This was the thinking behind our regular series on PC World, and is the thinking behind a new series we're launching today in collaboration with National Geographic.

The "Mobile Message" is aimed at a broad audience, but most importantly people who would never likely visit a mobile-specific site. Recent talks at Communicate - aimed at conservationists - and Nat Geo Live! - aimed at the general public - have convinced us even more that we need to stop just talking among ourselves and take the message out to more mainstream, broader audiences.

According to the first "Mobile Message" posted today:

"Over the next few months we will delve into the human stories behind the growth of mobile technology in the developing world. We'll take a closer look at the background and thinking behind FrontlineSMS, and hear from a number of users applying it to very real social and environmental problems in their communities. We will also hear thoughts and insights from other key mobile innovators in the field, from anthropologists to technologists to local innovators."

You can read the rest of the introductory post on the National Geographic website here.

SMS inspiration: A view from the Central Independent States

I'm beginning this week in the small landlocked eastern European country of Moldova, talking to representatives of IREX-supported organisations running telecentres and internet access points across the region. We just had a short session on FrontlineSMS, explaining how it works, and starting to come up with ideas for how to use it. Even though we talk every day about how users innovate way beyond our wildest dreams, I somehow still wasn't prepared for the deluge of brilliant ideas coming from the floor! Here are just a few, which the group have generously allowed me to share as inspiration for others thinking about how to incorporate SMS into their work:

• In a wide geographic area, liaising with partner NGOs, colleagues, and even the authorities - even if it's just to SMS and point out an important email you sent that day. Where the Internet hasn't yet really taken hold, people often don't check their email accounts every day.
• To let people know about trainings and workshops, or ask them to get involved in campaigns and actions
• To create a feeling of community between schools and kindergartens across a wide area
• To let students know when their scholarship money is ready for collection
• To send information to newly arrived migrants in Kazakhstan, where migration is a high-profile issue; informing  them of the law on registration, the contact details of their embassies in-country, and how to get a visa, a work permit, or citizenship
• In a big country, the potential as a research tool and information-sharing tool is huge
• Updating parents about their child's academic performance and behaviour at school.

Participants were also very realistic about the obstacles to using SMS. In countries where SMS bundles aren't common, costs can quickly mount up. In some countries, people often have multiple SIM cards to use across multiple networks as a cost-saving measure - subscription-based services can be a challenge here. And users realised quickly that they had to plan for the service they are considering offering to really take off, so that they would have to resource administrative support for it - but some, such as those proposing parent information services for schools, also saw that they could generate an income to cover this from a small subscription fee for the service.

A final note of caution from me was that in some of these countries, SMS are routinely monitored for political activity not favourable to the government. Where this is the case, organisations need to be aware that mobile services - or even the mobile network - can be quickly shut down, or bulk messaging heavily regulated and the SMS themselves can put both the service provider and the people they are interacting with at risk.

Over the next couple of days I'll be working with individual users on their operational and practical challenges - including types of network, operating costs and staff time - and I'll post further reflections here when I can.

CityCampLondon: thoughts on SMS and appropriate tech

This weekend has been spent at CityCampLondon, in a fog of coffee and beer, on Brick Lane and at the Kings Cross Hub, thinking and talking about using tech to make London better. I wanted to post a slightly more coherent version of my thoughts here.

At the Mobile in the City panel, I reflected on the UK's digital divide, which I've posted about here before, but took it further to suggest that the same factors preventing people from getting online might militate against them having a smart phone. As of January 2010, there were 11.1 million smart phones in the UK, 22.6% of active mobile contracts. Over three quarters of us still use 'dumb' phones. And while 31% of us browse the internet on our phones, 18% access social media and 13.7% access the news, 90.3% use SMS, or text messaging. Ok, so smartphone adoption is growing by an amazing 70% year on year, but I would argue that it's likely that the most marginalised and most vulnerable in society will be the last to see the benefits. Put simply, there's still an excellent case for using SMS to interact and communicate with people we struggle to reach using other technologies.

An example of this would be people who are rough sleeping, or homeless. A friend told me that when she volunteered in a soup kitchen, the most common request was for her to charge the batteries of people's pay-as-you-go phones behind the counter. Three soup kitchens, and one soup VAN, have downloaded FrontlineSMS to keep in touch with their regulars by text. Others are running helplines for teens, and domestic violence sufferers, or using SMS as an adjunct to treatment and support programmes for people with depression. People are collecting survey information, even reports of bird sightings. I'm searching right now for someone in the UK to house and maintain a simple FrontlineSMS hub to support activists monitoring evictions of Gypsies and Travellers in Essex (if you can help, let me know - no experience or tech knowhow required! Read more about this here.)

What these ideas have in common is that they aren't dependent on introducing new tech of any kind - just using technologies and communications media that people already have in their pockets, to enable them to do what they were doing before, but reaching further and doing better. The questions I've been asking people as we've gone through the third day here at the Hub Kings Cross are - who are you trying to reach? And what are they already using? Do you understand the social context? How boring I must sound.

Events like CityCamp and OpenTech are great but can be all about the tool. My plea this weekend has been to put the end user first. I'm not saying you shouldn't get excited and make things, but there is a gap between innovation (coming up with a tool) and implementation at scale (widespread use and social impact), and the bit in the middle is the human element. Make things easy, both for end users and for the organisations trying to reach them - keep technology simple and recognisable, keep the need for training to a minimum, keep barriers to access AND to implementation low. This remains a challenge for FrontlineSMS as we head towards our sixth year, but one we're determined to crack.

The corollary to this is that too often these events result in new organisations trying to cover similar ground in a new way. How frustrating that established players are so seldom flexible enough to pick up new ideas and adapt their existing models to take advantage of them. The pitches we're hearing right now (I'm writing this from the shadows as braver and more brilliant people than I pitch NESTA and Unltd for funding to bring their newborn ideas into the world) are strikingly diverse in style and approach, and in the problems they seek to attack. If there's something I'm disappointed about this weekend, it's that more people from the public sector haven't stuck around to understand how simple technologies can transform how they interact with their clients.

Thanks to Dominic Campbell and the FutureGov team for a great event and for bringing together a diverse bunch for three days - and thanks for inviting FrontlineSMS!

Designing for the REAL 95%

As occasionally happens, Ken and I find ourselves on opposite sides of the world at conferences this week. Ken is at Mobile Web in Africa 2010, in Johannesburg, and I'm hereby asking him to tell you all about it here when he gets a minute. o/ I'm at Design for Persuasion in Ghent, Belgium, with a room full of people who've never heard of FrontlineSMS - this is only the second time I've done this kind of event, but it's something we're committed to doing because that's how we get the word out to new audiences. As I did after the Digital Indaba in July, I thought I'd post the gist of my talk here. You can also listen to an AudioBoo which I recorded in a far more coherent manner than the actual talk, shortly afterwards.

Sidenote: I showed, as I always do, Ken's favourite diagram of 'social mobile's long tail'. Related but different is the persuasion map we're all developing (read: wrangling over) live at the conference, at BJ Fogg's suggestion. It maps technologies along axes showing prominence versus usefulness. SMS has already moved from unknown to well known, and from useful to not useful, a couple of times. Will be interesting to see where it ends up - or who gives up first...

Since I joined the team back in March I've spent a lot of time emailing our users and begging them for stories and feedback about their experience. You can read a version of this plea here! Many of you have given generously of your time and energy to write and tell me your thoughts on the platform and the challenges of implementing using SMS.

Something that surprised me a bit was the low proportion of users who were utilising more than the most basic functionality in FrontlineSMS. Many, perhaps 90-95%, are using only the functionality up to and including keywords to automatically respond to incoming SMS, or simply organise incoming SMS. But not all are aware of additional plugins like the Reminders module and the enormous potential of Medic's PatientView. Even auto-subscribing people to groups via SMS is a step beyond what many have time to set up.This might be controversial - do people disagree? Am I getting a false picture?

If not, the low take-up of advanced features is probably to do with capacity and time - both for many of the small community-based organisations who are our target user, if we have such a thing, and for larger NGOs and international organisations. Indeed, we know at times people struggle to get basic FrontlineSMS functions working effectively and meshing well with their existing work. We're tremendously excited about the potential of new functionality and technology, and small groups of users will be able to make excellent use of them - but for the majority of users, basic troubleshooting, support and advice are critical.

In the coming weeks we'll be working on our plans for the software in 2011 - stay tuned for more from this from our Lead Developer, Alex. Our role in providing user guides and resources, advice and support, and even training is something we're also looking carefully at. As ever, we'd welcome your thoughts.

Mobile meets health on the margins

The timing of this article could not have been better, given the discussions last week on the merits of mobile-based "cloud computing" and the clarification of our position a couple of days later. Despite advances in mobile devices and data connectivity, the need for mobile tools to also be able to work in less than optimal conditions is still as strong and as relevant as ever, as this use of FrontlineSMS by Telecoms Sans Frontiers in Nicaragua shows us all too well. "TSF - No Bugs In This Software That Fights Disease" (re-printed with the kind permission of SatNews.com) November 5th, 2009

"Since the beginning of October, Nicaragua is facing a huge rise of dengue cases, which has become a major public health concern in the country. The Health Ministry of the Central American nation (Minsa) has a crisis unit (SILAIS) which currently focuses its activities in response to both the dengue and H1N1 plagues. An Internet monitoring system has previously been set up to control the health situation in the country; nevertheless access to computer is often difficult in some regions where only few health centers are equipped.

Due to this serious situation, and the necessity to improve the collection of information, TSF, in collaboration with PATH (an international non-profit organisation that aims at enabling communities worldwide to break longstanding cycle of poor health) is reinforcing SILAIS’ capacities in Information and Communications Technologies.

In order to monitor the spread of the dengue in Managua and to conduct mobile health actions, TSF has been implementing for the first time a very innovative system based on a widespread, cheap and solid technology, GSM.

To set up the program, TSF uses FrontlineSMS software. Developed by a TSF partner NGO, FrontlineSMS is free, open source software that turns a laptop and a mobile phone into a central communications hub. Once installed, the program enables users to send and receive text messages with large groups of people through mobile phones. Thus, GSM technology is used to reach as many geographical zones as possible to control health issues in those areas. The server in SILAIS is connected with the 32 health units in Managua.

Each health unit has been delivered a mobile phone by TSF, so that they can send different kinds of information through SMS to the server. Hospital and health centers fill in predefined forms from their mobile phones and send them by SMS to SILAIS. Designed by PATH and the SILAIS, those forms provide data about the classic and hemorrhagic dengue cases, about the H1N1 2009 ones and the need for medicines when the stock nearly runs out. Once the forms received, the server stores information and puts them in databases in order to facilitate statistical analysis, on Excel format for example.

TSF provides two-way communication to health units enabling SILAIS to receive a daily report and gather messages from the health units and will have an updated situation in each center. At the meanwhile, SILAIS will also be able to communicate important information to them through SMS (such as an alert or a warning about coming meetings for example) or give them automatic answers to predefined questions sent by the health units.

By providing communication links between health structures and the SILAIS, TSF will allow the Health Ministry to have more accurate information about the diseases spread within Managua and quickly survey and assess the needs in affected areas. TSF helps health professionals use advanced methodologies such as smart phones and open-source software. Mobile devices are great tools to track and transmit crucial data in order to detect an epidemic threat at an appropriate time. Through this program, TSF participates in strengthening health systems in Nicaragua.

Following the installation of the system, on October 24th, TSF organized training for all the beneficiaries of the project. The health units and SILAIS staff were trained on the application’s functionalities and available services".

For a related article on FrontlineForms, the FrontlineSMS data collection tool used by TSF for the project, go here.

Our "social mobile" line in the sand

The depth and range of discussion generated by my last post on "the cloud" and "appropriate technology" may have come as something of a surprise, but one thing is clear. There's a great deal of misunderstanding around the topic, particularly with people who are either developing or promoting tools based on the very technology I was challenging. The only way to avoid this kind of confusion is to spell out our positions clearly, and I made this point in that very same post. So how do we move on from here? Well, we need to set out our positions clearly as a marker in the sand for future discussion. So, let me go first. To clear up any present and future confusion, here's the official FrontlineSMS / kiwanja.net position on what I consider five key "mobile tools for development" areas - location in the "long tail", scaling, replication and growth, open sourcing and access to "the cloud".

1. Who are your target audience?

Some time ago I butchered Chris Anderson's "long tail" concept and adapted it for mobile. It seemed like the best way of categorising the different focus areas for mobile tools - high-end for larger organisations down to low-end for small grassroots ones. Here's what I came up with.

The basic rationale behind the diagram is this. Tools in the red area are technically and financially out-of-reach of many grassroots NGOs, many of whom sit in the green space. Tools at the higher end of the graph are generally more complex, server-based systems which require a high degree of technical competence, and often the Internet, to set up and use. Tools in the lower end are simple, low-cost, need few technical skills, work on easily available hardware, don't require the Internet, and are easy to install and run. Tools in the green space can be quickly adopted and replicated - within hours - whereas tools at the other end need much more planning, i.e. more people and more lead time, and most likely a degree of training.

Note: There is no right or wrong or good or bad place on the tail. There are just different places

From its early beginnings in South Africa in 2004, FrontlineSMS has been totally focused on grassroots NGOs in the green space, an area which I believed back then was heavily underserved (and to a large degree still is). We're not particularly interested in big users such as international NGOs or government departments. So if our tool isn't considered right for the kinds of big projects they're likely to be running, then that's fine with us.

I wonder where the other social mobile tools would place themselves on the tail?

2. What is your position on scaling?

Believe it or not, not everyone wants to build tools that can grow into large centralised solutions, which is how many people seem to define scale. No one is ever going to run a nationwide election monitoring campaign running into millions of text messages using a single laptop, cable and mobile phone. FrontlineSMS is based on "horizontal scaling", gained by an increase in the numbers of individual users with their own systems. In other words, a hundred systems in a hundred clinics serving 10,000 people each, rather than one system adapted and "scaled up" to serve a million. We're happy and comfortable with this approach, as are our target audience of grassroots NGOs.

3. How does it replicate and grow?

Growth is based on patience, and a "pull" rather than "push" approach, i.e. awareness-raising and then letting NGOs decide if they want to try out the tool or not. Those that do then go and request it from the website. Everything is driven by the end user, who needs to be independently motivated to download and use the tool. There is no need for us to be involved at any stage, so no-one flies anywhere and no-one does any training - note that the approaches of FrontlineSMS:Medic and FrontlineSMS:Credit may be different - and no-one tries to "sell" FrontlineSMS to anyone. The solution is designed to allow users to do everything themselves. No core FrontlineSMS implementations are driven by us, and none are our projects. Use is replicated by users sharing experiences, talking about their use of the tool to others, and growing numbers of champions who are either building their own solutions around FrontlineSMS, or bloggers and researchers who write about its use and impact.

4. What is your position on open sourcing?

Again, from the very beginning we have been unashamedly focused on our end user - NGOs in developing countries seeking easy-to-deploy mobile tools. Our end users are not programmers, coders or technical developers, and few if any of our FrontlineSMS user base would have any idea what to do with source code. We decided that we would focus on the open source community once we believed we had something worth working with, and that time is about now. In between working on everything else, we plan to launch a developer community soon. That all said, there are already a number of developers bolting on new functionality to the core FrontlineSMS platform, and 90% of the code is already available online and accessible through SourceForge.

5. Does access to "the cloud" matter?

FrontlineSMS only came about four years ago because of a critical lack of tools that allowed for group messaging without the need for the Internet. Building a tool which is able to operate in Internet-free zones has therefore been central to our thinking since the very beginning, and continues to this day. Beyond basic messaging, FrontlineSMS can make use of an Internet connection when and where available - messages can be forwarded via email, or posted to websites, for example (that's the functionality Ushahidi takes advantage of) - but no Internet is not a show stopper for us. And as time moves on and connectivity does improve, we'll be ready. We're adding picture messaging in the next couple of months (for example), and other web-based features are in the pipeline. We are not anti-Internet, but realistic when it comes to its availability and reliability.

So, that's our line in the sand. If anyone else has a mobile tool - or is working on a mobile tool - I'd encourage them to clear up any possible confusion and write a post outlining their thinking in these five areas. The alternative is more confusion, and more false arguments and comparisons.

I know I'd love to know the thinking behind more social mobile tools, and going by the reaction earlier this week, it looks like I'm not the only one. Now is a good-a-time as any to join the conversation.

Read responses and "lines in the sand" from:

FrontlineSMS:Credit FrontlineSMS:Medic

(As of 20th December, no other mobile tools providers have responded, which is a shame. May the confusion and misrepresentation continue...)

The Social Mobile Long Tail explained

What follows is a short extract from the recent "Soul of the New Machine" human rights/technology conference hosted by UC Berkeley, in which I explain my theory of the Social Mobile Long Tail.

This video is also available on the FrontlineSMS Community pages

A full video of the session - PDA's and Phones for Data Collection - which includes presentations from InSTEDD, Ushahidi, DataDyne and Salesforce.com, is available via the FORA.tv website.

A glimpse into social mobile's long tail

Although I've only been writing about the social mobile long tail for a couple of years, the thinking behind it has developed over a fifteen year period where, working on and off in a number of African countries, I've witnessed at first hand the incredible contribution that some of the smallest and under-resourced NGOs make in solving some of the most pressing social and environmental problems. Most of these NGOs are hardly known outside the communities where they operate, and many fail to raise even the smallest amounts of funding in an environment where they compete with some of the biggest and smartest charities on the planet.

Long tail NGOs are generally small, extremely dedicated, run low-cost high-impact interventions, work on local issues with relatively modest numbers of local people, and are staffed by community members who have first-hand experience of the problems they're trying to solve. What they lack in tools, resources and funds they more than make up with a deep understanding of the local landscape - not just geographically, but also the language, culture and daily challenges of the people.

After fifteen years it should come as no surprise to hear that most of my work today is aimed at empowering the long tail, as it has been since kiwanja.net came into being in 2003, followed by FrontlineSMS a little later in 2005. Of course, a single local NGO with a piece of software isn't going to solve a wider national healthcare problem, but how about a hundred of them? Or a thousand? The default position for many people working in ICT4D is to build centralised solutions to local problems - things that 'integrate' and 'scale'. With little local ownership and engagement, many of these top-down approaches fail to appreciate the culture of technology and its users. Technology can be fixed, tweaked, scaled and integrated - building relationships with the users is much harder and takes a lot longer. Trust has to be won. And it takes even longer to get back if it's lost.

My belief is that users don't want access to tools - they want to be given the tools. There's a subtle but significant difference. They want to have their own system, something which works with them to solve their problem. They want to see it, to have it there with them, not in some 'cloud'. This may sound petty - people wanting something of their own - but I believe that this is one way that works.

Here's a video from Lynman Bacolor, a FrontlineSMS user in the Philippines, talking about how he uses the software in his health outreach work. What you see here is a very simple technology doing something which, to him, is significant.

Watch this video on the FrontlineSMS Community pages

In short, Lynman's solution works because it was his problem, not someone elses. And it worked because he solved it. And going by the video he's happy and proud, as he should be. Local ownership? You bet.  o/

Now, just imagine what a thousand Lynman's could achieve with a low cost laptop each, FrontlineSMS and a modest text messaging budget?

The "long tail" revisited

Four years ago was a very lonely time. Not for me personally, understand, but in the social mobile space. The wider non-profit world was just beginning to take a serious interest in what the technology had to offer, and in 2004 I'd just co-authored one of the earlier reports - funded by the Vodafone Group Foundation - on the use of mobile technology for conservation and development. To give some context, these were the days when it was widely believed that "poor people in developing countries" would never be able to afford a phone, and the days when concrete case studies on the application of mobile technology for positive social and environmental change were few and far between. Most evidence was anecdotal. A revised report would look very different today, but with one exception - many of the conclusions would likely still stand. If that's the case, how far have we really come?

Four years ago this week I came up with the concept of a laptop-based group messaging hub. The software I ended up developing is better known today as FrontlineSMS ("ProjectSMS" was the working title for the first few months). When I eventually got the resources together to write the first version in the summer of 2005, there was zero chance of reinventing any wheels. The "social mobile applications" shop was quite literally bare. After extensive research for a project I had been working on with South Africa National Parks (SANParks), there were simply no appropriate technology mobile solutions they could easily pick up and run with. The situation seemed crazy, and I had a hunch that SANParks were not alone in their need for an appropriate, portable, GSM-based communications tool. The rest is history, as they say.

Things are not quite so lonely today and 2008 - for me, at least - goes down as the year things really began to change. For what seemed like an age, FrontlineSMS was one of the few appropriate technology-based mobile tools aimed at - and openly and freely available to - the grassroots non-profit community. For a while it was the only one. It was also likely the first to be developed specifically with the NGO sector in mind - most other solutions were commercial offerings which found their way into the hands of NGOs, quite often the larger international variety with the funds, expertise and resources to use them. The frustration for me was that - until last year, at least - many of the emerging 'non-profit' mobile solutions seemed to be following that same model.

Enter "The Social Mobile Long Tail", my attempt at mapping out the social mobile applications space (you can read the original post, which explains the thinking in detail, here).

The basic rationale behind it was this. The majority of emerging mobile solutions, platforms or tools (call them what you will) were settling in the red area, and as such were technically and financially out-of-reach of many grassroots NGOs, many of whom sit in the green space. Tools at the higher end of the graph are generally more complex, server-based systems aimed a multinational NGOs or government departments. Tools in the lower end are simple, low-cost, appropriate and easily replicable solutions. My experiences working with NGOs in Africa over the past fifteen years has strongly influenced and steered the focus of my work towards the long tail, and I would have it no other way.

But let's just destroy a few myths for a minute. There are many out there. Here's my top three (feel free to add to these in the comments section below).

Firstly, wherever your tool sits on the graph, there is no right or wrong place for it. It's all about the context of the user. There is just as much a need for $1 million server-based, high bandwidth solutions as there are for free, SMS-only tools. In your typical scenario, national governments would likely go for the former, and grassroots NGOs for the latter, but not always. Both are valid, and tools shouldn't ever be described as "being better" than another because of it. This is a big mistake. We need there to be solutions all along the tail so that the users have a healthy applications ecosystem to dip into, whoever and wherever they may be. If you're trying to park a car into a small space, a Mini is much better than a Rolls Royce.

Secondly, let's not get all hooked up on scale. Just because a tool in the long tail might not run an international mobile campaign does not make it irrelevant. Just as a long tail solution might likely never run a higher-end project, expensive and technically complex solutions would likely fail to downscale enough to run a small communications network for farmers from a small NGO office with no mains electricity, for example.

Thirdly, we don't yet have any complete, polished mobile tools. I would argue that everything that we see in the social mobile applications ecosystem today is "work in progress", and it will likely stay that way for a very long time. Speaking with my FrontlineSMS hat on, I'd say we're probably only about 40% there with that solution right now. There is much to do, and the mobile technical landscape never stands still. Our challenge is how we all move with it, how we stay relevant, and how we all work together to share technical resources and know-how. A fragmented mobile landscape is a problem for all of us.

There have been many positive blog posts calling 2009 the "Year of Mobile". I think they could be right. I also think 2009 is going to be the "Year of the Searcher" (see my earlier blog post). As I argued back then, let's never forget it's the users of our tools who we answer to. Social change happens on the ground, often through them, and not online.

For the first time in four years things don't feel quite so lonely. I for one am hugely honoured to be working in a space alongside some of the most dedicated and talented people in the mobile and development fields, all of whom are trying to apply a range of practical solutions - all the way along the "social mobile long tail" - to some of the most pressing problems in the world today. We have a great opportunity in front of us if we stick together, remain focussed, and do not lose sight of the big picture.

After all, we don't want to be reading blog posts in twelve months time calling 2010 the "Year of Mobile", do we?

Pocket messaging?

During the recent Pop!Tech Social Innovation Fellows boot camp in Camden, Maine, I had the pleasure of sharing a cabin with Erik Hersman of White African, AfriGadget and Ushahidi fame. Despite knowing Erik for a couple of years or so, it was the first time we'd managed to sit down over a prolonged period and chat Africa, mobiles, innovation and technology. It was great and, as it turned out, productive.

Most evenings founds us blogging, Tweeting (@whiteafrican and @kiwanja), practicing our 5-minute Pop!Tech pitches, sharing stories and bouncing random ideas around. So it came as no surprise when we stumbled on a pretty cool idea for a hybrid piece of hardware (at least we think it's a pretty cool idea). If it existed, we thought, this thing could unlock the potential of platforms such as Ushahidi and FrontlineSMS yet further, and prove a real breakthrough in our efforts to lower the barrier to entry for organisations seeking to use SMS-based services in their social change work.

Messaging hubs like FrontlineSMS - currently being used by Ushahidi in the DRC to collect and forward local text messages to a remote server - require three things to work. Firstly, a computer with the software installed and configured; secondly, a local SIM card connected to a local mobile operator; and thirdly, a GSM modem or mobile phone to send and receive the messages. The GSM device is essential, as is the SIM card, but the computer is another matter. What if messaging software such as FrontlineSMS could be run 'locally' from a microSD card which slotted into the side of the modem? The software, drivers, configuration files and databases could all be held locally on the same device, and seamlessly connect with the GSM network through the 'built-in' modem. This would mean the user wouldn't need to own a computer to use it, and it would allow them to temporarily turn any machine into a messaging hub by plugging the hybrid device into any computer - running Windows, Mac OSX or Linux - in an internet cafe or elsewhere.

Right now this is only an idea, although we're going to see what we can do with it early next month when Erik and I, along with most of the Ushahidi team, happen to be in Nairobi, Kenya. Using Erik's extensive contacts in the Kenyan innovation space, we'll be looking to see if a prototype device like this can be cobbled together in a workshop somewhere. I'm willing to sacrifice a GSM modem in the name of progress.

If the guys can pull it off then there's a real chance we could get funding for wider trials. Things would then get really interesting not only for our own projects, but also for many others working in the same social mobile space, making rapid prototyping and the dissemination of tools much quicker and easier.

Social mobile: Doing what it says on the tin

About a year ago I was asked to give an interview to the Africa Journal. They were looking at ICT innovators and entrepreneurs in Africa and I agreed, despite being mildly uncomfortable being labelled an ICT innovator or an entrepreneur (and an African one, at that). At the end of the interview, however, they captured a brief moment which beautifully encapsulated what FrontlineSMS is all about. The interview ended:

FrontlineSMS provides the tools necessary for people to create their own projects that make a difference. It empowers innovators and organizers in the developing world to achieve their full potential through their own ingenuity

FrontlineSMS has always been about empowerment. It's never been about telling people how to use mobile phones to monitor elections, to increase market transparency, or help raise awareness around HIV/AIDS issues, even though it's been used for these things and many more. At the end of the day, it's a tool which allows organisations to figure out how to do these things for themselves. Combine that with a connected community and you have the makings of something quite powerful.

The decision to build a platform - and not a specific solution to a specific problem - has turned out to be one of the key strengths of the software. The new functionality we've added to the latest version takes this one step further allowing, for example, St. Gabriel's hospital in Malawi to figure out how to do automatic remote top-ups of their health workers' phones, or CP-Union in the Philippines to share incoming SMS data - human rights reporting in this case - with their own K-Rights Monitoring software. When users start adding contacts, keywords and actions in FrontlineSMS, or integrating it into existing systems, they're essentially creating something new, something from scratch, a communications environment all of their own making.

In ideal circumstances platforms become something of a blank canvas, and the brushstrokes the user-generated 'content' (actionable ideas, in this case). Not only does this encourage a culture of do-it-yourself thinking, it also creates instant engagement and ownership. Combine these with the local knowledge and level of engagement many NGOs already have with their stakeholders, and you're half-way to a positive outcome. Approaches which allow initiatives to grow from the ground up, focussing on technology as the enabler (not the owner) generally have the greatest chance of success. The uses of FrontlineSMS, for example, are bewildering, and they're growing all the time. Few, if any, were anticipated. Lower the barriers to entry and all sorts of things can happen, it seems.

Local ownership, the use of appropriate technology, ease-of-use, high replicability and accessibility, and a low barrier to entry should be among the key ingredients of any grassroots-focussed social mobile tool. If we're to make real, tangible progress then the tools we create don't only need to set out to empower, they need to empower. In other words, they need to do exactly what they say on the tin.

Cometh the hour. Cometh the technology.

For NGOs and developers alike, the ICT4D space can be a tough nut to crack. While NGOs generally struggle to find the tools they need to meet their particular needs, developers face the opposite problem - getting their tools into the hands of those who need them the most. Attempts to connect the NGO and developer communities - physically and virtually - continue to this day with varying degrees of success. There is no magic bullet.

Of course, bringing together the two parties in one place - conference room or chat room - is only a small part of it. Getting them to understand each others needs, often over a technologically-fuelled chasm, can be another. While one side may approach things from a "technology looking for a problem" angle, NGOs often have it completely the other way round. One of the boldest attempts in recent times to join the non-profit/developer dots took place in February 2007 in the boldly titled UN Meets Silicon Valley conference, where the United Nations met up with a bunch of Silicon Valley companies to explore how technology and industry could bolster international development. Lower-profile events take place far more regularly, often in the form of 'user generated conferences'. One such gathering - yesterday's BarCampAfrica - aims to bring "people, institutions and enterprises interested in Africa together in one location to exchange ideas, build connections, re-frame perceptions and catalyse action that leads to positive involvement and mutual benefit between Silicon Valley and the continent of Africa".

Having worked for many years in the non-profit sector, particularly in developing countries, I've seen at first-hand the kind of challenges many face, and their frustration at the lack of appropriate ICT solutions available to them. I've also been on the developer side of the fence, spending the last three years building and promoting the use of my FrontlineSMS messaging platform among the grassroots non-profit community. Unfortunately, despite what you might think, seeing the challenge from both perspectives doesn't necessarily make finding a solution any easier. Getting FrontlineSMS, for example, into the hands of NGOs has become slightly easier over time as more people get to hear about it, but it's been a very reactionary process at a time when I'd much rather be proactive. No magic bullet for me.

Sadly, for every ICT solution that gains traction, many more don't even see the light of day. While some may argue that those who failed probably weren't good enough, this isn't always the case. Take Kiva as a case in point. In the early days Matt and Jessica Flannery were regularly told by 'experts' that their idea wouldn't work, that it wouldn't scale. They didn't give up, and today Kiva is a huge success story, connecting lenders - you and me - to small businesses in developing countries the world over. Since forming in late 2005 they have facilitated the lending of over $14 million to tens of thousands of entrepreneurs in some of the poorest countries in the world.

A key turning point for Kiva was their decision to switch from business plans to 'action' plans, getting out there and building their success from the ground up. Some of us would call this "rapid prototyping", or "failing fast". Whatever you choose to call it, it's an approach I firmly believe in. In places like Silicon Valley getting it wrong isn't seen as a bad thing, and this encourages a "rapid prototyping" culture. Sadly the story is very different in the UK.

Some projects - Kiva and FrontlineSMS among them - are based on experiences gained in the field and the belief that a particular problem can be solved with an appropriate technological intervention. Of course, before any ICT4D solution can succeed there has to be a need. It doesn't matter how good a solution is if people don't see the 'problem' as one that needs fixing. In the case of Kiva, borrowers were clearly in need of funds, yet lenders lacked access to them. With FrontlineSMS, grassroots non-profits were keen to make use of the growing numbers of mobile phones among their stakeholders, but lacked a platform to communicate with them. These two initiatives worked because they were problems that found a solution.

The ICT4D space is exciting and challenging in equal measure, and by its very nature practitioners tend to focus on some of the most pressing problems in the most challenging regions of the world. Whether it's a natural disaster, a stolen election, human-wildlife conflict, a crushed uprising or a health epidemic, elements of the ICT4D community spring into action to either help co-ordinate, fix, or report on events. Interestingly, sometimes it can be the events themselves which raise the profile of a particular ICT solution, or the events themselves which lead to the creation of new tools and resources.

In 2006, Erik Sundelof was one of a dozen Reuters Digital Vision Fellows at Stanford University, a programme I was fortunate enough to attend the following year (thanks, in large part, to Erik himself). Erik was building a web-based tool which allowed citizens to report news and events around them to the wider world through their mobile phones. This, of course, is nothing particularly new today, but back then it was an emerging field. During the final weeks of his Fellowship in July 2006, Israel invaded Lebanon in response to the kidnapping of one of their soldiers. Erik's tool was picked up by Lebanese civilians, who texted in their experiences, hopes and fears through their mobile phones. The international media were quick onto the story, including CNN. Erik's project was propelled into the limelight, resulting in significant funding to develop a new citizen journalism site, allvoices, which he runs today.

In a similar vein, it took a national election to significantly raise the profile of FrontlineSMS when it was used to help monitor the Nigerian Presidential elections in 2007. The story was significant in that it was believed to be the first time civilians had helped monitor an election in an African country. As the BBC reported, "anyone trying to rig or tamper with Saturday's presidential elections in Nigeria could be caught out by a team of volunteers armed with mobile phones". Although FrontlineSMS had already been around for over eighteen months, its use in Nigeria created significant new interest in the software, lead to funding from the MacArthur Foundation and ended with the release of a new version earlier this summer. The project is now going from strength to strength.

One of the most widely talked-about platforms today also emerged from the ashes of another significant event, this time the troubles following Kenya's disputed elections in late 2007. With everyday Kenyans deprived of a voice at the height of the troubles, a team of African developers created a site which allowed citizens to report acts of violence via the web and SMS, incidents which were then aggregated with other reports and displayed on a map. Ushahidi - which means "witness" in Kiswahili - provided an avenue for everyday people to get their news out, and news of its launch was widely hailed in the mainstream press. Putting Ushahidi together is a textbook study in rapid prototyping and collaboration. In the past few months the project has also gone from strength to strength, has been implemented in South Africa to monitor acts of anti-emigrant violence, won the NetSquared Mashup Challenge and was runner-up in the recent Knight-Batten Awards.

The interesting thing about these three projects is that they all proved that they worked - in other words, proved there was a need and developed a track record - before receiving significant funding. Kiva went out and showed that their lending platform worked before major funders stepped in, just as FrontlineSMS did. And Ushahidi put the first version of their crowd sourcing site together in just five days, and have reaped the benefits of having a working prototype ever since. If there is a lesson to learn here then it would have to be this - don't let a lack of funding stop you from getting your ICT4D solution off the ground, even if it does involve "failing fast".

Of course, not everyone should rely on an international emergency to raise the profile of their project, and it wouldn't be wise to bet on something ever happening, either. But when it does, the obvious lack of a solution to an emerging problem often rises to the surface, creating an environment where tools which do exist - whether they are proven or not - are able to prosper for the benefit of everyone.

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.

Bridging the knowledge divide

A common theme in my work, and in many of my conference talks, centres around a very simple message - appropriate technology. It's nothing new, and as a concept has been around since the 1970's with Fritz Schumacher's defining book, "Small is Beautiful: Economics as if People Mattered". During my recent interview with Nokia's "New Horizons" magazine, however, it was interesting that the conversation was entirely appropriate-technology focussed. I was expecting questions about FrontlineSMS, my work on wildlive! and my developing-country technology experience. Instead, the interview was dominated by my focus on "needs-based", "human-centred", "grassroots" and "appropriate" technologies. Believe me, I was more than happy to talk about these things - I don't think enough people do.

It still surprises me - sometimes even saddens me - that we live in an era where there's a general tendency to over-engineer solutions. Not only is this a waste of time in my view, but it's a waste of money and effort. It also raises expectations. Believe me, there's plenty of this going on as we speak (sorry, read). I come across this at conferences where I meet hugely technically-abled people who spend their time trying to find homes for the very latest technical gadgetry. And because of where I work, and the circles where I mix, the home they are looking for is usually in a developing country. This only serves to exaggerate the problem.

Take the recent use of my FrontlineSMS system in the Nigerian elections. FrontlineSMS is not rocket science. It's so simple, in fact, that it slipped under most people's radars. One comment on Slashdot discussing its use highlights this over-engineering view well:

It's too simple. You guys don't know what you are talking about. Doing it all with one computer and an SMS modem? You can't future proof it that way. I want to see some mention of CORBA and SOAP. How can you have a system without middleware? Can you use dot NET? Everybody uses that these days. And what if I want to use it when I am already on the phone. Can't it have a WAP interface as well? I want to sell a thousand copies of this thing and nobody is going to pay a million bucks for something which doesn't use a single cutting edge technology

There is certainly no written rule that everything has to be cutting edge. Very little, in essence, is. Is Google cutting edge? There were plenty of other search engines around before they came along. All they did was see the opportunity, do it better and hit the target. Over the coming weeks I'm going to be spending a lot of time discussing mobile phone use, and web access, in developing countries. I'll soon be presenting a paper - the same one presented at W3C in Bangalore last December - at the 16th International World Wide Web Conference in Banff, and sitting on an expert panel at the same event. And my message will be the same as it has always been.

Although it should come as no surprise that there's a gulf between many developers and the realities of life in developing countries, there have been attempts to bring the two together. Some have worked better than others, but at least there's a realisation that a meeting-of-minds is needed. If you want a simple, effective example as to why, take a look at the handsets being used by the majority of rural people in developing countries (see photo, taken in India this January). Then have a think about how Java, Flash Lite, WAP and smart-phone applications would go down with these users. Okay, one day these technologies will become relevant, but right now I would argue that they're not. SMS is still the killer application, like it or not. And, on the subject of web access on mobile devices, I would also argue that we haven't quite mastered it ourselves yet. Generally-speaking the user experience still leaves a lot to be desired.

I'm not the only person who thinks this way. Far from it. And I'm looking forward to meeting the others, and our technically-minded colleagues, in Canada next month. Time to re-open the debate...