Lessons Learned from Developing
      Mobile Phone Tools
        for Field Projects

          Can Ozturk Ph.D.
     http://developmatics.com
Typical Mobile Phone Application

            Web access




                         Short Code
                         Aggregator
Challenges in Developing and Operating
         Mobile Tools in Developing World

•   Platform reliability
•   Carrier/Aggregator reliability
•   Operational costs (SMS, IVR, Smart Phone Apps)
•   Application performance over constrained infrastructure
•   System administration and maintenance requirements
•   User support and training
•   Local participation and ownership
     – Technology
     – Sustainability
Engaging Local Actors to Own the Technology

•   Demonstration of mobile capabilities
•   Identify key users and roles who will drive the system
•   Manage scope and expectations
•   Participatory System Analysis and Design
        Report/Analysis of Current Situation
        Proposed/Revised Use Cases and logical steps
        Review of blueprint document (Wireframes, message text etc.)
        Approval and sign-off
        Design
        User Acceptance Testing
        Launch
        User workshops to share experiences
Engaging Local Actors to Use Technology Efficiently

   •   Recruiting and training local resources
   •   In-country support for administrators
   •   User feedback on improvements
   •   End-user scenarios must be simple
Achieving Sustainable Mobile Tools

•   Customizable platforms
•   Integration with other systems
•   Systems development in phases
•   Government support and stakeholder feedback
Lessons Learned - I

•   Usage level and system performance
•   Complex use cases
•   Unanticipated uses or constraints
•   Scope definition
•   Solution Model
     – M&E or service delivery
     – Piloting incentives for high adoption
Lessons Learned - II

• Survey Options – concatenated vs. ping pong
• Testing applications
• Sharing phones, low literacy rates, cost
• Time sensitive tasks can be streamlined using SMS
  reminders
• Controlling access to data
Example Cases

• Agricultural Market Price Collection System
• Drug Logistics Management System
MARKET PRICE COLLECTION SYSTEM


Smart Phone/GPS         IVR                                      WEB

          Submit Market Prices
                                                             Publish Reports
                                                            Non-response follow-up



                                                                                 MARKET
MARKET                                                                         COORDINATOR
                              IVR      SMS       WEB
AGENT

                               Request Price Information



  Timeliness Notifications                              SMS to Agents
                                    AGRI-USER/ PUBLIC
Complex Reports via SMS
       • Requires flash-cards
       • May support conditional
         formatting and subforms
       • Difficult to enforce controls
         for data validity via SMS

Mobile lessons

  • 1.
    Lessons Learned fromDeveloping Mobile Phone Tools for Field Projects Can Ozturk Ph.D. http://developmatics.com
  • 2.
    Typical Mobile PhoneApplication Web access Short Code Aggregator
  • 3.
    Challenges in Developingand Operating Mobile Tools in Developing World • Platform reliability • Carrier/Aggregator reliability • Operational costs (SMS, IVR, Smart Phone Apps) • Application performance over constrained infrastructure • System administration and maintenance requirements • User support and training • Local participation and ownership – Technology – Sustainability
  • 4.
    Engaging Local Actorsto Own the Technology • Demonstration of mobile capabilities • Identify key users and roles who will drive the system • Manage scope and expectations • Participatory System Analysis and Design  Report/Analysis of Current Situation  Proposed/Revised Use Cases and logical steps  Review of blueprint document (Wireframes, message text etc.)  Approval and sign-off  Design  User Acceptance Testing  Launch  User workshops to share experiences
  • 5.
    Engaging Local Actorsto Use Technology Efficiently • Recruiting and training local resources • In-country support for administrators • User feedback on improvements • End-user scenarios must be simple
  • 6.
    Achieving Sustainable MobileTools • Customizable platforms • Integration with other systems • Systems development in phases • Government support and stakeholder feedback
  • 7.
    Lessons Learned -I • Usage level and system performance • Complex use cases • Unanticipated uses or constraints • Scope definition • Solution Model – M&E or service delivery – Piloting incentives for high adoption
  • 8.
    Lessons Learned -II • Survey Options – concatenated vs. ping pong • Testing applications • Sharing phones, low literacy rates, cost • Time sensitive tasks can be streamlined using SMS reminders • Controlling access to data
  • 9.
    Example Cases • AgriculturalMarket Price Collection System • Drug Logistics Management System
  • 11.
    MARKET PRICE COLLECTIONSYSTEM Smart Phone/GPS IVR WEB Submit Market Prices Publish Reports Non-response follow-up MARKET MARKET COORDINATOR IVR SMS WEB AGENT Request Price Information Timeliness Notifications SMS to Agents AGRI-USER/ PUBLIC
  • 12.
    Complex Reports viaSMS • Requires flash-cards • May support conditional formatting and subforms • Difficult to enforce controls for data validity via SMS