Platform Developer Documentation
Search…
👋
Welcome | README
Code of Conduct
Contributing | Getting Involved
Frequently Asked Questions
Join the Ushahidi community
Contributors ✨
🛣️ The Ushahidi Platform Roadmap
Privacy and security best practices
Development & Code
Development: Overview
How to get the source code
Setup Guides
Add code to Ushahidi
Development process
Coding Standards
Track and submit issues in Github
Upgrading Ushahidi
⚙️ Installation Helper‌
Tech Stack
API Documentation
Third party app development
Database | Tables overview
Database | Database Schema Diagram
Database | Table details
📐
Architecture
Use case internals
QA & Testing
The QA process
How to run QA tests
Defect Management
How to write QA test scripts
Hotfixes
Front-end development
Changing UI styles: introduction to the pattern library
Design
🎨
Design: overview
'Best practice' design
Ushahidi Platform 'Sticker Sheet'
User testing process
User testing script examples
Synthesising user testing results examples
Open Source Design
Documentation
Documentation
Contributing docs via GitHub
Translation
Localization and Translation
The Ushahidi Platform Facebook bot
The Facebook bot
Hackathon and events
Installathon, May 2019
Write/Speak/Code 2019
Open Design: Bangalore
Open Design: Taipei
Enhancement Proposals
Exchange Format
Importing data from previous versions
Powered By GitBook
'Best practice' design
Guidance on how to design well for Ushahidi.

Best practice design

Ushahidi encourages everyone who wants to contribute to their OSS products regardless of perceived skill level. As an OSS contributor, you should be able to receive feedback and guidance with your contribution in order for your work to be merged into the project regardless if it is code, documentation or design.
We do expect you to be ready to discuss, collaborate and support your design efforts with appropriate user insight and research or good sound design logic.
We expect consideration of several aspects when designing for Ushahidi's products:
1 - Understanding of the Ushahidi product by using and investigating the tool yourself as well as the varied use cases of the tool. You can learn more about varied use cases by visiting our website grassroots section and case studies like Quakemap. Familiarity with the tool will help you understand how to design with the users in front of your mind. Reviewing the Pattern library is also very useful.
Ushahidi's products are used in high-stress scenarios. From natural disasters to trauma survivors and human rights activists. Always be aware of the vulnerability of these kinds of users and their safety.
2 - Make appropriate consideration of accessibility needs like colour impairments, sight-impairments, low connectivity/download speeds, older devices that might not run complex systems well, literacy levels, physical impairments etc. Learn more about designing inclusively with accessibility in mind at A11y.
3 - The user comes first and balancing a tech build is important. If the choice between a good user experience that works and is inclusive or what is 'easiset' to build technologically then is it best to not build or take longer to build than build something which at best, doesn't work well or at worst could potentially harm human life.
4 - When the above criteria have been met, design beautiful, engaging, visually pleasing work. Be mindful of design fashion and trends that will not age well.
Design - Previous
Design: overview
Next - Design
Ushahidi Platform 'Sticker Sheet'
Last modified 1yr ago
Copy link