Flutter
One codebase for the iOS and Android apps.
D-01 · US nonprofit community app case study
An appbuilt forevery user
A community organisation serving families needs an app that every member can use, including those who rely on screen readers.
In buildNonprofit · mobile appUnited StatesKicked off June 2026
Mobile appAdmin portalAPIAccessibility
Platforms
01
At a glance
Kicked off June 20262Platforms, one codebase: iOS and AndroidIn build
WCAG 2.2 AAAccessibility standard, tested before launchIn build
12–14Week build, four milestones2026
100%Code, cloud and store accounts owned by the clientContracted
The short answer
AiS LABZ is building a US nonprofit a cross-platform mobile app for iOS and Android: news, events with ticketing and QR check-in, donations, push notifications and a member directory, run from an admin portal. It is designed and tested to WCAG 2.2 AA, with VoiceOver and TalkBack support, over a 12 to 14 week build.
02
Where things stood
the starting point- Updates, events and giving lived in separate places.
- Members relying on assistive technology needed an experience built for them, not retrofitted.
03
What changed
results2 Platforms, one codebase: iOS and Android
In build
- Scope agreed: 8 core modules from sign-in to donations.
- Four delivery milestones: kickoff, backend and staging, QA and accessibility, store submission and handover.
- Client ownership contracted: repository, cloud environment and both app store accounts.
04
In numbers
hover or tap for exact valuesBuild plan
Contracted scope, 2026
8Core modules, sign-in to donations
2Platforms from one codebase
4Delivery milestones
12–14Week build
Want a result like this for your business?2 Platforms, one codebase: iOS and Android. Book a free 15-minute diagnostic and we will tell you what would move your number.
05
How we did it
diagnose, model, build, compound01Diagnose
Discovery with the organisation's team: audiences, events, giving and the existing WordPress data.
02Model
One app, three jobs: stay informed, show up, give. Accessibility treated as a launch requirement, not a feature.
03Build
Flutter app for iOS and Android, an Angular admin portal, a .NET 9 API, and a MySQL layer that syncs with the existing WordPress site, hosted in the client's own cloud.
04Compound
A 90-day post-launch support window, then a roadmap for volunteers, fundraising tracking and learning resources.
06
How we leveraged the platforms
what each one did in this engagementAngular
The admin portal staff use to manage events, news and notifications.
.NET
The backend API connecting the app, the portal and the existing website data.
MySQL
The database, synced with the organisation’s existing WordPress site.
GitHub
Every line of code lives in a repository the client owns.
Microsoft Azure
The client-owned cloud environment for the API and data.
PayPal
Donations inside the app, one-time and recurring.
WordPress
The existing website whose content and members the app reads.
iOS
App Store submission and VoiceOver accessibility testing.
Google Play
Google Play submission and TalkBack accessibility testing.
07
Who we worked with
by level and roleNonprofit leadership teamProgramme and events staff
What happens nextBackend and staging delivery, with iOS and Android test builds, then accessibility QA.
08
Keep exploring
the services, proof and reading behind this resultServices behind this result
Digital Product DevelopmentWebsites, apps and platforms built fast, crawlable and accessible.09
Common questions
Why build for accessibility from day one?
Because retrofitting screen-reader support is slower and worse. WCAG 2.2 AA, VoiceOver and TalkBack are tested before launch, not after.
Who owns the app?
The organisation does: the code, the cloud environment and both app store accounts.
Can staff update content without a developer?
Yes. The admin portal manages news, events, banners, campaigns and push notifications.
Next step