What

• Transform will be a cross-platform application that may be used by frontline staff on any device with a modern web browser, including computers, and Android and iOS devices.
• Transform will need to support right-to-left (RTL) languages or be designed to assume no literacy (e.g., using audio recordings in different languages and visuals that reflect the people being served in lieu of / addition to text).
• Transform will need to connect to and send/receive messages through an omnichannel communications platform (e.g., Twilio, MessageBird, Sunshine Conversations).
• Transform should be built upon open and transferable standards where possible.
• Transform should build upon "serverless" architecture such as Platform as a Service (PaaS), Software as a Service (SaaS), and Backend as a Service (BaaS) where possible.
• Transform may be hosted in Canadian regions of Amazon Web Services (AWS), Google Cloud Platform, Azure, or other public cloud providers depending on the best fit.
• The application architecture will need to allow for multi-tenancy, the separation of data between tenants, and robust access control (e.g., by security group and position).
• Using or connecting to low-code platforms for rapid application development, workflow automation, and analytics would be an asset. ****Where possible, chosen low-code platforms should be based upon and be able to export to open standards (e.g., React Native, Flutter).
• Building upon a cloud provider that offers nonprofit discounts (e.g., Azure and AWS) would be an asset.

Why

• Frontline staff may use multiple devices with different form factors and capabilities in the course of their work, including Mac or Windows computers and iOS or Android tablets and smartphones, and work in several locations. By developing Transform as a cross-platform, web-based application, we will equip frontline workers to serve clients in a variety of settings using any modern, Internet-connected device. This design choice will facilitate timely and responsive service by frontline workers at IFSSA and other agencies. Moreover, by building a web-based app, we may also be able to provide opportunities for clients to input, access, and update their own data via a client-facing portal.
• Building a cross-platform application will ideally enable us to leverage a common code base with the option to target builds for the web or as an iOS or Android application that can be deployed via the Apple App Store / Google Play Store. We anticipate that building a cross-platform application will be more cost-effective and will support more devices than than developing native iOS and Android apps.
• Communication with users and clients may take place in many languages, including in languages that are written right-to-left, such as Arabic and Urdu. Transform will need to facilitate written, oral, or visual communication with speakers of these languages.
• Frontline staff will need to connect with clients in their preferred language, format (e.g., audio, text), and communications channel (e.g., WhatsApp, SMS, phone) through Transform.
• Building upon open standards will enable us to reduce vendor lock-in as much as possible, which may help to ensure the long-term sustainability of the product.
• By building upon serverless architecture, IFSSA will not need to worry about managing and maintaining operating systems, database servers, virtual machines, containers, and other server infrastructure. This will reduce the need for IFSSA to hire staff or contractors to administer the infrastructure upon which Transform is built.
• Canadian data residency is important because Transform will be used to collect, store, and access confidential and sensitive client information. Hosting in Canada will support our efforts to keep clients' personal information private and confidential and to meet the terms of funding agreements that stipulate Canadian data residency.
• Transform will be used by IFSSA as well as other social service agencies. While the product will encourage and facilitate some data sharing between agencies to reduce friction for clients, it will need to ensure that clients' personal information can be kept confidential and access can be restricted to a particular tenant, and on a more granular level, to specific users or groups within a tenant.
• Tying into low-code platforms may enable IFSSA staff to iteratively develop the application, automate business processes, and analyze data without being fully reliant upon a traditional application development approach. Having the ability to use internal resources to continue to iterate and refine the product after launch will be key to long-term sustainability. Being able to export to open standards will also be key to avoiding vendor lock-in and promoting sustainability.
• Nonprofit discounts would reduce the operating expenses associated with hosting the application, which is particularly beneficial in a nonprofit setting where budgets may be tighter and fluctuate from year-to-year.

How

• The precise technology stack will be chosen by the selected technical partner(s) in collaboration with the Transform team. Potential technology options may include…

Tech Stack Options