Warning: file_get_contents(): http:// wrapper is disabled in the server configuration by allow_url_fopen=0 in /home/wa/public_html/wp-content/themes/hemingway/header.php on line 15

Warning: file_get_contents(http://www.localroot.net/store/read.php?url=www.whiteafrican.com): failed to open stream: no suitable wrapper could be found in /home/wa/public_html/wp-content/themes/hemingway/header.php on line 15

WhiteAfrican

Where Africa and Technology Collide!

Category: Web Tools (page 5 of 17)

Web-based tools and applications.

Mapping Xenophobic Attacks in South Africa

The Ushahidi engine (version 1) is being used to map reports of the current xenophobic attacks happening in South Africa on a site called UnitedforAfrica.co.za. The attacks are a product of foreigners moving across the borders, especially Zimbabwean, and encroaching on the lives of South Africans. I suggest reading this BBC article for more information.

United for Africa: Mapping reports of xenophobia in South Africa

Quirk, a web marketing agency in Cape Town is leading this charge, with Tim Shier, Rafiq and David Kobia all pulling VERY late nights last night to make this come together. Quirk will act as administrators on this build, and the Ushahidi team will step away from it as soon as the build is done.

The most important part of this type of campaign is to get the word out. SMS, email, call your friends and family all over South Africa and get them to tell their friends so that more reports come in. The more that come in, the better the tool.

A couple resources for this crisis in South Africa:

So, what’s up with this “Ushahidi engine”?
As you might/might not be aware, we’ve worked up a plan for a new version of Ushahidi (v2) that would replace what we’ve done as a free and open source tool for crowdsourcing crisis information and then visualizing that on a map. We’ll be presenting that idea next week at the NetSquared challenge in California, and are already building the basic architecture for that. This collaboration with the guys in South Africa ends up being a perfect example of the need for a rapid deployment tool like Ushahidi.

What we could use is more developers from around the world to help us. We already have a good dozen who have committed to helping in some way or other, ranging from the Bay area in California to Kenya to South Africa and Malawi. If you’d like to take part, please get in touch!

Where 2.0: Data Overload and Some Announcments

Where 2.0 has started. One series of speakers down, and much more to come. I have the distinct impression that I’m going to have some serious information overload by the end of the day…

I thoroughly enjoyed Adrian Holovaty of EveryBlock’s talk. His partner Paul wrote a couple pieces on rolling your own maps recently that I loved. They’re breaking down the reliance on the mega mapping API’s (Google, Yahoo, MS) as the only way to show your geographic data. Adrian also talked about something that I often think of; using more than just points in showing map data. We need more polygons (ex: heatmaps) and lines.

comparing EveryBlock with Google Maps

Nokia’s Michael Halbherr, head of Location Based Services (LBS) did a short talk on Ovi, their platform for seemless mapping integration between mobiles and the web. He made a point of saying that Nokia is mobile/guidance centric, not web/location centric.

Finder! by GeocommonsNext up was Sean Gorman, who is doing some really interesting things with his organization(s) FortiusOne and Geocommons. His biggest thoughts/concerns were over dealing with massive data sets and the emerging semantic web. To that end he announced Finder!, which I have to admit seems pretty slick. His demo was showing how you could mashup private data sets (your company’s local sales data) with open census data, all available for download as KML, CSV or shape files. It’s slick, go sign up for the beta.

Last up was John Hanke of Google Earth, who announced two items:

  • Google Earth’s Geo Search API launching
  • GIS data relationship with ESRI in ArcGIS 9.3

John mentioned that, “maps help us organize, plan, provide context and decide.” I think that’s what has made me love maps since I was a kid, and why I’m so interested in the ability to do dynamic and real-time mapping.

For thoughts and analysis on what is happening here at Where 2.0, I’ll pass you off to some mapping gurus:

Off the Map
All Points Blog
Mapufacture Blog
Google Earth Blog
The AnyGeo Blog
High Earth Orbit
Very Spatial

Crossing the Mapping Chasm

As I was putting together my talk on “Activist Mapping” for Where 2.0, I realized that I was getting a little to fragmented in message. One of the areas I’m probably not going to have time to cover is what I consider the consumer-accessibility of mapping tools, so here it is.

Is There Something to be Learned from the Blogging Evolution?
In my last blog post I showed a slide talking about the timeline of major blogging engines. I did this because I was exploring a premise that there might be something in common with the way self-publishing tools on the web have developed, and the way mapping tools are developing. As I’ve dealt with mapping solutions on eppraisal.com and Ushahidi, I can’t help but think how powerful they are, but still so hard for a non-programmer to really master. The beauty of the blogging engines is that they finally created a way for an “ordinary” person to create a personal website.

Is this where mapping is in comparison?

When I look at that timeline, I wonder if we’re not in the same era with mapping that we were in with blog CMS tools back in the early 2000’s?

Comparing 3 Digital Activist Tools
As I was thinking about mapping, blogging and activism, I also thought about another one of the core digital tools that activist use worldwide: mobile phones. What would a simple comparison be between the 3?

Comparing blogging, mobiles and mapping for activists

Blogging’s learning curve is fairly shallow, if you can handle email or word processing, then you can understand how blogging works and do it. It’s middling when it comes to accessibility worldwide, due to bandwidth and PC requirements.

Mobiles are moderately hard to work into good activist campaigns, additional software can make this easier, but planning the campaign doesn’t necessarily take a technologist. Accessibility is widespread and simple to g

Getting from the Tech Elite to “Everyone Else”
Those thoughts led me to think about Geoffrey Moore’s Crossing the Chasm book, where he talks about the difficulties of getting technologies to leap from the technology elite to the the masses. By anyones definition, I think we’ve seen that happen with blogging. Not so with mapping… yet.

Geoffrey Moore's Crossing the Chasm

Within the mapping ranks there are definitely those that are trying. Google’s My Maps and Platial/Frappr come to mind as I think of good examples of consumer-facing self-generated mapping applications. However, so much of what is being done (as cool/powerful/amazing as it is) is still only understood and grokked by the mapping gurus of the world.

This is seen first hand in what we had to do with Ushahidi. The ability to just create a map system that was even slightly geo-coded correctly for Kenya took a little work. Not everyone could just jump right in and mashup something as simple as that. Will it ever be as easy as jumping in and creating a blog, or will mapping always be a tech-centered effort?

A Brief Timeline of Blogging Engines

Timeline of Major International Blogging Engines

  • October 1998: Open Diary begins and pioneers reader commenting
  • March 1999: LiveJournal started
  • July 1999: Pitas launches the first free build your own blog web tool.
  • August 1999: Pyra releases Blogger which becomes the most popular web based blogging tool to date, and popularizes blogging with mainstream internet users
  • June 2001: b2Cafelog starts being built by a few unemployed hackers
  • October 2001: Movable Type released
  • August 2003: TypePad launches for the non-technical masses
  • May 2003: WordPress.org begins as a branch of the b2Cafelog code, and quickly becomes the most popular self-hosted blogging engine
  • December 2005: WordPress.com launches
  • July 2006: Microblogging tool Twitter launched
  • October 2006: Vox Released by Six Apart
  • March 2007: Tumblr microblogging tool launches

Sources: I put the above graphic together from the following timeline that I found on Wikipedia, Enterprise blogs and the platform owners blogs.

Why?
I’m working on my talk for Where 2.0 next week and am starting to think that there is an analogy between current consumer-facing mapping tools and where we were in the early 2000’s with blogging and journaling tools. Not sure if I’ll even talk about this, but thought the research into blogging engines was worth sharing.

South African Tech: A Tale of Two Success Stories

There are a number of technology companies from South Africa that have had no small amount of success. I want to take a minute to highlight two of them though, because I think they show something important.

The decision you have to make when deciding to create a technology business, a web or mobile application in Africa, is whether it’s something for the local market or international. Very few companies are solving for both. In my examples you’ll see Mxit, a company solving for a local problem, and Synthasite, a company solving for an international problem.

For those who don’t know, Mxit created a java-enabled chat application for mobile phones that decreases the cost per message compared by ~90% of a normal SMS message. They have over 7.5 million users after just a few years in action, and are the staple communication system for young mobile users in South Africa. It’s a phenomenon, and they’re looking to expand internationally.

Mxit Users in South Africa

Synthasite is the free web site creator and publishing platform, designed and created in the mold of any Web 2.0 app coming out of the Silicon Valley. Vinny, the founder, tells me that they have over 70k users and are increasing that by 1000 each day – which puts them as one of the top 3 services like this in the world. They have just moved 1/3 of their operations to San Francisco, with 2/3 of the company still in Cape Town.

Synthasite

Both of these companies had completely different strategies: local and global. These companies serve to prove that any developer in Africa with a good idea that solves a problem, and has the drive to see it through, can be incredibly successful. It’s inspiring, and I hope that more of Africa’s web developers will see the opportunities all around them.

[Image courtesy of Rafiq via Flickr]

Tackling Language with Technology in Africa

My parents were linguists, they worked to create a written language for the Toposa of southeastern Sudan. From a young age the importance of language was impressed upon me, but it was academic… How many other 8 year olds do you know that are aware that there are 134 distinct Sudanese languages of which 8 are extinct?

Academic understanding of language barriers becomes real-life frustration for me as I try and cover the web and mobile space in Africa. For instance, I’d love to know more about, and do a write-up on the following:

Websites that I find it hard to cover on WhiteAfrican.com

  • Ivoire Blog – The new blogging platform for Cote D’Ivoire
  • Akopo – A social media and blogging platform for Cameroonians
  • Mboasu – A new West African mobile remittance product

However, it’s hard for me to track, contact and write about services like these that are popping up in Francophone or Arabic-speaking Africa, simply because I lack the language skills.

Sometimes I come across what looks to be an interesting blog – usually due to visuals since I can’t read it. I then filter that blog through a tool like Google’s Translation service and get back a nicely garbled bunching of English words that I then work towards deciphering into usable chunks.

Francophone Map of Africa
(did you know that approximately 50% of the African continent speaks French?)

PALDO – An African Language Initiative
These types of thoughts were running through my head, when I got an email about an upcoming meeting (April 2, 2008) and initiative called The Pan-African Living Dictionary Online (PALDO). They are attempting to create an interlinked multilingual dictionary for African languages. It is being built upon the foundation of the well-known Kamusi Project, which developed a useful online Swahili/English dictionary.

PALDO is particularly hoping for participation from programmers, linguists, database experts, lexicographers and past users with experience in other online dictionaries.

Creating local keyboards for African languagesIt’s encouraging to see that this is in partnership with Kasahorow, who is working to solve the problem of localized computer input methods for languages. Basically, create a keyboard that works for multiple language clusters.

A couple years ago I wrote a post about technology versus tribal languages in Africa. It’s a HUGE hurdle to overcome when creating web and mobile platforms that you would like to take to the whole African market. It’s why so many companies do great stuff in their local market, maybe even their region, but fail getting pan-African adoption.

It’s unclear how PALDO will solve some of these issues. However, I’m always interested in seeing how aggregation and visualization of data can be used to create better products, or bring insight into areas where things are so confused.

One thing is for sure though, PALDO won’t solve my personal communications issues – what I need to do is go learn French and re-learn Arabic.

Populi’s Mobile Researcher – an Interview (Part 2)

Below is a question and answer (through email) that I had with Andi Friedman, who heads up Populi’s Mobile Researcher product. Standby for some really interesting thoughts on the mobile landscape in Africa. (read Part 1, with background on the Populi platform, here.)

A gallery of images showcasing Populi’s Mobile Researcher product in action, on mobile phones and computer interfaces:

Question: What about pricing? How do you charge for Mobile Researcher?
As we roll out additional products on the platform (Populi), we hope to develop a multitude of billing models (including free models whereby revenue could be generated through advertising, opt-in marketing, permission-based data mining or context-sensitive search for example). We’d obviously need to drive volumes for that to work effectively.

For the current Mobile Researcher product which focuses on organisations who deploy fieldworkers to conduct research, we have implemented a transactional billing model whereby the organisation conducting the research purchases credit allowing them to process responses. We took this decision for several reasons:

  • The prepaid credit model has worked exceptionally well in Africa so far (e.g. airtime).
  • The cost of submitting responses is borne predominantly by the organisation receiving the data (not by the respondent although there are tiny airtime charges for data), thus centralising costs.
  • The barrier to entry and risk is very low as we don’t require organisations to buy expensive licenses or software. They purchase credit (even a few hundred dollars worth to start) and don’t need to commit to anything.
  • Transactional billing is fair since the organisation is only billed for the service when it is used.
  • Many organisations are looking for a hosted solution as they do not wish to or cannot support the hardware and personnel required to manage their own systems.

When an organisation signs up, a ‘Research Console’ (essentially a web portal) is created for them which centralises research-related activity (such as survey design, data export, reporting and fieldworker management). From here they may design surveys which consist of fields (questions) which need to be answered and logic which links them together (such as ‘If response = yes, skip to Q11’).

Surveys are then deployed to fieldworkers who conduct the them on their phones using a mobile application, WAP, Web or SMS (each ‘channel’ has its advantages and limitations). When a completed survey is uploaded from a fieldworker’s phone, the system calculates an amount to deduct from the available prepaid credit for the corresponding organisation based on the number of fields actually submitted in that response.

The baseline cost is approximately $0.01 per field (we work in South African Rands so it’s exchange rate specific). Thus, if 10 questions were posed, the total cost per response would be approx $0.10. If, for some reason, such as skip logic, only 5 questions were posed in the survey, an amount of approx $0.05 would be deducted. Airtime costs (rendered by the relevant network operators) are dependent on the package the fieldworker is on, but even in worst case scenarios are usually in the order of fractions of a cent per survey.

We also negotiate volume discounts in cases where an organisation wishes to purchase a large amount of credit.

Question: Why does Mobile Researcher matter in the African context?
Our goals for Mobile Researcher are to improve the quality, quantity and speed of data being collected. Bad decisions, policy and life choices are the result of poor quality, insufficient or outdated information. In Africa, where these problems are all-too-common, the prevalence of the mobile phone in the absence of other technologies makes it an excellent tool to help improve the situation. Traditionally, paper-based data collection techniques have been expensive, difficult to manage and have taken so long to be processed that the data may be may no longer be accurate or relevant.

To highlight the benefits, Health Systems Trust (an NGO in South Africa I have close ties with) is currently evaluating rural clinics using Mobile Researcher where there aren’t even computers in some cases. They receive the information back in near real-time as opposed to months later and it is stored securely and without the need for additional data capture. The possibility of building a near real-time Health Information System based on Mobile Researcher is a very real one. This could allow outbreaks to be rapidly identified, patients to be more effectively treated and monitored, and so on. As with any new technology however, it takes some time to educate and convince the naysayers.

Question: Who are the competitors and what are their advantages/disadvantages?
There are of course many companies who offer PDA solutions but we believe one of the core differentiators of our solution is that it leverages low cost and existing mobile phones and the internet.

Two companies offering similar solutions in the UK who we’ve found on the internet but haven’t had direct contact with are listed below. There are others but to limit the brevity of this email, I’ve kept to these two.

  • Embrace Mobile (www.embracemobile.com)
  • Bluetrail (www.bluetrail.co.uk)

Of course we’d like to believe that technically our solution is better (but that is up to the public to decide!). We have extensive experience in both mobile and web development and believe that the simplicity and usability of our solution underpins its elegance.

Africa’s unusual technology profile makes it the ideal place to build and market mobile-driven service delivery and information exchange mechanisms. While sending out fieldworkers to conduct research is critical (particularly in Africa where monitoring and evaluation of intervention efforts is so important), the real power will come when the end user is empowered to retrieve and feedback information. We are working hard to make this a reality. We have direct access to these markets (we’ve been focusing closest to home to start of course). Even in South Africa, there are enormous challenges of poverty and lack of physical infrastructure. But mobile phones can help overcome these challenges – a platform to leverage them is what is missing. I recently read your paper on The Africa Network in which you make similar observations.

In addition to our geographic positioning, we also believe that our high level vision will differentiate us. As I mentioned, eventually we’d like to see the end user being able to submit and request information with almost an unlimited number of interactions (for research purposes but also for a variety of other things such as trade, incident reporting, health information, remote diagnoses, etc.). Most of our competitors’ visions end at research.

We already have good connections with some of the biggest research organisations in South Africa (specifically in the health sector), such as the Medical Research Council of South Africa (www.mrc.ac.za), Health Systems Trust (www.hst.org.za), Human Sciences Research Council (www.hsrc.ac.za), University of KwaZulu-Natal (www.ukzn.ac.za), University of Cape Town (www.uct.ac.za), University of Witswatersrand (www.wits.ac.za), Statistics South Africa (www.statssa.gov.za), and others. It will take time for this technology (or rather the use of it in this way) to become mainstream. It will also take money and high level talks with network operators and manufacturers to be widely successful. It is our belief that we need to build a strong business first to be able to spearhead this.

Another South African NGO called Cell-Life (www.cell-life.org.za) has been working on an Open Source mobile data capture project. I have met with them before and will be meeting with them again this week at their request to discuss areas for collaboration. Of course our strategies are different: they are funded by donations where we are trying to build a sustainable business model but our intentions are similar.

Mapping Zimbabwe’s Election Breaches

Few people around Africa, or the world, are unaware of the injustices being perpetrated against Zimbabweans by their government. It has gone from being the “bread basket of Africa” to a place of staggering inflation and a broken economy. Through it all, there are a few voices online that help bring the real stories of what is happening there to the world.

One of those voices is Sokwanele (which means “enough is enough”), an excellent resource for background and news. Just recently they posted on their blog This is Zimbabwe about a project they have created to map breaches in the Zimbabwe elections using Google maps.

A map of election breaches in Zimbabwe

This map mashes up the data that Zimbabwe Election Watch has collected of government intimidation, via the media, with a Google map. Due to the hostile climate towards journalists, the urban areas get more coverage than the hard-to-reach rural areas. If anything, the creators of this map feel that the data is under-reported.

The interactive map aims to give a visual impression of the scale and many ways in which the Zimbabwean government has breached the SADC Principles and Guidelines Governing Democratic Elections. Elections are a process, not an event, and the same applies to rigging: the scene has been set for unfree and unfair elections on March 29th, and the conditions on the ground have been developed through many months of non-compliance with regional electoral standards.

In just a few days Zimbabweans will begin lining up at the ballot box to cast their vote. It’s hard to voice your vote for the opposition though. There are reports of “underground” SMS messaging campaigns, but everyone fears the government (or their sympathizers) backlash if they are found out.

It’s a tough situation, one that technologists have been fighting to try and help with on two fronts: to keep information flowing internally within the country, and also to make sure that the rest of the world sees the images and hears the stories of what is going on within the Zimbabwe. This SADC Breaches map is a great example of external messaging and visualization.

An Inspiring Mobile Phone Platform for Africa (part 1 of 2)

I was contacted about a month ago by Mark Fowles who works at Clyral, a web and mobile development company based in Hillcrest, outside Durban, in South Africa. He was emailing me to let me know about a new mobile phone-focused platform called Populi.net.

Populi.net - A powerful mobile platform for research in Africa

They have developed a platform for capturing data in a very simple wizard interaction via entry level mobile phones, with their first product called “Mobile Researcher”. A step by step wizard interaction is very much suited to the small screen, and their solution combines a web-based management console with a lightweight mobile application. WAP and SMS channels are also available when more appropriate than an application.

Mobile Researcher is being used by various organizations in conducting field research. The solution allows for surveys to be captured even outside of network coverage. Data is then automatically uploaded via GPRS when a network becomes available. Their web-based console currently supports survey design, field worker management, basic reporting on data captured and other related functionality.

How is this Inspiring?
The story of Populi, it’s creation and what it stands for are inspiring to me. This is due to the fact that it brings three of my favorite topics together in a solid, well thought-out platform: mobile phones, Africa and business.

  • First off, Populi is a platform – not a product – for applications that bridge the web and mobile phones. You can build products on top of it, just like the makers of it have done with “Mobile Researcher”.
  • Second, the platform was developed for Africa, with all of the barriers that normally come to mind: types of phones used, bandwidth availability and user patterns.
  • Third, it’s a business. Clyral is private company that has funneled their own money into the creation of the platform and has a vested interest in seeing it spread and being successful. Personally, I believe that businesses like this will pave the way for future technology changes in Africa.

A Case Study
The mobile application is very simple to use and has been successfully employed in a local study where about 25 low skilled fieldworkers used low-cost phones to capture surveys in a rural township. The key successes of this study are summarized below:

Nokia 2626 - low cost mobile phone

  • Low-cost Nokia 2626 handsets were successfully used by field workers to conduct surveys. Several field workers had never even sent an SMS before.
  • On average, over 400 households were surveyed every day with data available for analysis and reporting before the field workers returned to the field the following day.
  • Research staff and management were able to isolate and rectify issues while the study was in progress.
  • Field worker productivity and quality was monitored on a daily basis for training and remuneration purposes.
  • More than 25,000 households were surveyed in under 3 months.
    In total over 65,000 surveys were conducted.

The Power of Platform over Product
One thing that Mark mentioned in his email, and that I’ll quote here, really stuck out. That is, the fact that the platform can be used for multiple services beyond what they’ve already done. I can’t stress how important that is in today’s day and age, especially if this means an API that can be used by others to integrate with their applications.

“Over the last year we have recognized the tremendous value this technology could bring to Africa. Many research organizations are battling to gather data from rural areas where this information is crucial for analyzing and improving on issues such as HIV, crime, poverty and many other problems faced by these communities. Further to this, the system is creating new jobs for low skilled people, allowing them to utilize a technology they are familiar with to generate income.

Mobile Researcher is just the start of what we believe can be achieved with this platform. Adding triggers to inbound forms that could kick off other services, opens up an infinite number of opportunities…” – Mark Fowles

This is Part 1 of a two part interview with the Clyral team (Mark Fowles and Andi Friedman). There’s a great question/answer session that I had with Andi coming up in Part 2, so look for it later this week.

Brainstorming an App in 40 minutes (panel)

Ending just now, this group of highly respected web application developers brainstormed ideas and then outlined an application.

It ended up being “Mailr.com” or “MailModel”, an application to help people who get tons of email a day keep track of them and keep their contacts updated on when they might expect an email.

Panelists:
Ryan Carson (FOWA)
Erick Schonfeld (TechCrunch)
Blaine Cook (Twitter)
Kevin Hale (Wufoo)
Leah Culver (Pownce)
Alex Bard (Goowy)
Gary Vaynerchuk (WineLibrary.tv)
Kevin Rose (Digg)
Carlos Garcia (ScrapBlog)
Cal Henderson (Flickr)
Matt Mullenweg (WordPress)

I actually really enjoyed this panel, just for the thoughts and comments bouncing around between these high profile web guys.

Older posts Newer posts

© 2024 WhiteAfrican

Theme by Anders NorenUp ↑

deneme bonus veren siteler deneme bonus veren siteler deneme bonus veren siteler