Platform User Manual
[Mzima] User Manual
[Mzima] User Manual
  • [Mzima] Ushahidi Platform User Manual
  • Navigating the Ushahidi Platform User Manual
  • Downloading the User Manual
  • Translating the User Manual
  • About Ushahidi
  • Overview of Ushahidi Platform [Mzima]
    • Technical Specifications
  • 1. Installing Ushahidi Platform
  • 2. Setting up a deployment
  • 3. Configuring your deployment
    • 3.1 Accessing your deployment
    • 3.2 General Settings
    • 3.3 Surveys
    • 3.4 Data Sources
      • 3.4.1 Email
      • 3.4.2 Gmail
      • 3.4.3 Vonage(formerly NextMo)
      • 3.4.4 SMSSync
      • 3.4.5 Twilio
      • 3.4.6 Twitter
      • 3.4.7 Africa's Talking
    • 3.5 Categories
  • 4. Managing People on your deployment
    • 4.1 Roles
    • 4.2 Users
  • 5. Modes for visualizing and managing data on your deployment
    • 5.1 Map View
    • 5.2 Data view
    • 5.3 Activity view
    • 5.4 Data managing functionalities shared among views
  • 6. Managing Data in your deployment
    • 6.1 Viewing Posts
    • 6.2 Filtering and Sorting Posts
    • 6.3 Adding Posts
    • 6.4 Editing Posts
    • 6.5 Translating Posts
    • 6.6 Publishing Posts
    • 6.7 Deleting Posts
    • Page
    • 6.8 Importing Data
    • 6.9 Exporting and Tagging Data
      • 6.9.1 Exporting Data
      • 6.9.2 Tagging Data - HDX integration
  • 7. Analysing Data on your deployment
    • Untitled
    • 7.1 Saved Searches
    • 7.2 Collections
  • 8. Additional Links
Powered by GitBook
On this page
Export as PDF
  1. Overview of Ushahidi Platform [Mzima]

Technical Specifications

PreviousOverview of Ushahidi Platform [Mzima]Next1. Installing Ushahidi Platform

Last updated 1 year ago

Better development stack

Ushahidi mzima platform Backend API is built on PHP stack: as with v3 platform, we’ve isolated the core logic of the platform standalone Entity and Usecase classes. The mzima platfrom API uses the Laravel framework.

The user interface of Ushahidi mzima platform is a separate app with a codebase that has the web client and mobile client in it. The web client is built with Javascript, HTML + CSS using modern Angular 14+ and the Angular material library for styling. The mobile client is built using the Ionic framework.

What’s new (and improved)?

Largely similar to v3:

  • Dependencies are properly managed and easier to update or replace needed.

  • We’re using our own API to build the app, it gets first class support.

  • You can work on just the UI without delving into the API code

  • Modern libraries mean they’re still being supported, we don’t have the burden of supporting legacy libraries ourselves.

Code is easier to customize

  • It’s more structured making it easier to find what you want - architectural changes still ongoing

  • It doesn’t repeat itself so a change can be made in one place, not need to be copied everywhere else - architectural changes still ongoing

  • UI is isolated to the backend API, allowing work on just the UI without having to delve into the API code

The stack

  • Back-end: , , /, or PostgreSQL

  • Front-end: , , , . Built with . Using for mapping, and a collection of other frontend libraries

Linux
PHP
Apache
Nginx
MySQL
Angular
Javascript
Html
CSS
NodeJS
Leaflet