A knowledgebase for leaders in nonprofit organisations, on issues related to software technology and its use in community programs. It is based on our experience of working in many such community programs for dozens of organisations over years.
Factoring software codebase size and complexity is most important factor to consider when taking ownership of generic open source products
Generic software solutions have very large codebases compared to custom solutions. Nonprofit organizations must factor in this when taking over ownership of such products.
A simple technology idea to bring the communities voice into social programs. A hyperlink in the physical world.
Short note on Gunak software system used in health programs for improving the quality of health services and facilities at public hospitals and clinics
We often discover that PWAs and cloud-based solutions, though applicable sometimes, but are often wrongly applied to low-resource setups. Hence, we attempt to develop a simple thumb rule for choosing deployment architecture for low-resource environments - with their tradeoffs.
In a reporting software system (unlike point of work), the users don't use it when they are providing services to their clients (citizens). They use them later on, periodically, to report data about their work. Intuitively we like the point of work system, but it is the reporting systems that have dominated.
This is the main underlying cause behind many poorly designed software. The low resource constraints require learning it as a cross-cutting domain.
Affordable technology is available, but there are other issues to be tackled to allow for in-house data analysis in nonprofits
Making the community health and hospital systems data available to each other holds promise to improve health outcomes for the community member/patient. If you are planning or considering doing something like this, this article may help uncover certain issues beforehand and may help you make the right decision.
More and more nonprofits have to think about, how should they get the software developed for themselves. Should they outsource or have in-house teams or do something else? We go through the challenges in each of the approaches and what are the sustainable options.
The term open source often invokes fear in nonprofit organisations about whether it implies a lack of control over data and software behaviour. It is mistaken with open data, open API, free-for-all software. In this article, we explain open-source software from basics from a customer experience standpoint.