On Tuesday, 25 January 2011 we will be deploying a major update to the Analytics section. The Analytics section provides access to raw data, reports and export functionality for all your data collected using Mobile Researcher.

To facilitate integration with custom built applications Mobenzi Researcher supports a rich application programming interface (API). The API is implemented using REST which provides flexible data services that are naturally integrated with the web. This means that the API may be accessed from virtually any platform or programming language. Most custom built applications use the API to [...]

As part of the 13.02.2010 release, 3 interface enhancements were deployed to improve navigation and assist in quickly determining your current context. These included the introduction of a Breadcrumb, the rework of the Quick-switch panel and the introduction of a Ribbon to complement the navigation tabs.

By enabling airtime monitoring for a fieldworker’s SIM card, you are able to automatically specify recharges consisting of airtime, data, SMS bundles or a combination. Configured recharges take place without your intervention and only if a fieldworker’s credit drops below a predefined threshold.

Notification triggers allow your applications to receive alerts when survey responses are received. We’ve updated the protocol to guarantee notification delivery and also added notification when a submission is modified in your research console. This update will be launched on the 27 August 2009.

To improve security, from 27 August 2009 access to the research console will be moved from HTTP to HTTPS. This will require a minor change to applications accessing the API via HTTP.

Mobile Researcher maintains a full audit history of any changes made to a field.

An update to our billing model makes using Mobile Researcher even more affordable. Blank responses and instructions will no longer be billed for.

We’ve added the ability to duplicate existing surveys with a single click.

With this new feature, you may optionally elect to use a short naming convention whereby each option in a multi-select question response is identified by QUESTION-NAME_OPTION-VALUE instead of QUESTION-NAME_OPTION-LABEL. This results in significantly shorter, but still unique column headings.