...
Android
Java/Kotlin
PWA
SMS / USSD …
Technology | Requirement | Supported interaction | Applicable?
| Use case | Priority
| Notes | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
SMS | Basic phone, 2G, Literacy. Shortcode to ensure free SMS | Basic interactions, Notifications. No limit on number of steps for dialogue, but gets cumbersome above 5-10 steps. |
|
| SMS costs are quite high. Implementers/Users need to be aware | |||||||||||||||||||||||||||||||||||||
IVR | Basic phone, 2G, Phone familiarity. Shortcode to ensure free calls. | Very basic interaction but doesn’t require literacy (except “Press 5”). Can record messages and allows transfer to a real agent in urgent cases or as fallback. |
|
| ||||||||||||||||||||||||||||||||||||||
USSD | Basic phone, 2G Literacy. Aggregator. | Basic interactions. Can support longer interactions Potential timeouts (USSD is like a call). | ||||||||||||||||||||||||||||||||||||||||
Mobile Web | Smartphone, 3G/4G, Smartphone familiarity. Web server/ domain required | Complex interactions. Limited offline capabilities are available. Progressive web apps can be installed on a home screen and receive notifications, thus mirroring a lot of native functionality. However, progressive web apps have longer initial load times - though much faster in subsequent loads - and require the development of an app according to specific technologies. | ||||||||||||||||||||||||||||||||||||||||
Mobile App | Smartphone, 2G or 3G/4G, Smartphone familiarity Web server / domain required. | Complex interactions. Offline-mode is available with syncing data upon the availability of network connection. |
Priorities for new development
Mobile-first? (for some functionality? eg. enrolment - most of the usage now and in future will be done through the mobile interface - does it make sense in the re-design to have UI/functionality that serves the mobile interface better if a choice has to be made between mobile/browser?)
Improve exiting functionality? Which ones?
Develop new functionality? (eg. client portal)
Strategic orientation
Develop openIMIS specific apps?
Build ‘modules’ in existing global goods - eg. ODK?
Integrate other global goods with similar functionality? (eg. Meso-health - now open source at: github.com/meso-health )?
...