The builder's path
For: Screen-reader users in Thunderbird for Android can't reach the quick actions sighted users get by swiping.
“The true creator is necessity, which is the mother of our invention.”
Routes to a solution
Each route is a different kind of journey, with real people and organisations to contact at each step, starting with those in every country.
Step 1
Build in the open
Publish the code and invite contributors from the community.
Let the people a free tool helps fund its maintainer directly.
Raise and spend money in the open for a community project.
Grants for open source that makes the internet better.
Network of civic tech groups in many countries; find the one near the problem.
Step 2
Fund the maintainers
Sponsors, collectives and open source grants.
Let the people a free tool helps fund its maintainer directly.
Raise and spend money in the open for a community project.
Grants for open source that makes the internet better.
Network of civic tech groups in many countries; find the one near the problem.
Step 3
Get it adopted
Civic tech groups and public bodies take it up.
Y Combinator's free course and co-founder matching.
Raise and spend money in the open for a community project.
Network of civic tech groups in many countries; find the one near the problem.
Volunteer data scientists working with social-sector organisations.
Ideas, sources and tools for this problem, from first interviews to funding.
the legacy and Compose message lists
the team deciding when the new message list ships
Starter prompt
Built from this problem's brief. Paste it into Claude or any AI assistant.
Help me design and build a first working prototype for this problem in Anywhere. Problem: Screen-reader users in Thunderbird for Android can't reach the quick actions sighted users get by swiping. Who it hurts: People who use TalkBack, Android's screen reader, to read email in Thunderbird. The moment it hurts: When they want to archive, delete or mark a message as read from the message list. What people do today: The configured swipe actions are not offered in TalkBack's Actions menu on the message list the app ships. Why it is still unsolved: The new message list has the actions, but the app still uses the old one, so it's unclear whether to fix the old list or switch over. What solved looks like: Every configured swipe action is offered as a TalkBack action on each message in the list users actually get, confirmed on a real device by a TalkBack user. Where: Anywhere First, list what you would need to learn from the people affected before building, as interview questions. Then propose the simplest version that would help, the screens or messages it needs, and the data it would use. Keep it cheap to run, accessible, and respectful of people's privacy. Flag anything you are unsure about instead of guessing.
Talk to the people who live it before you build.
“Some things are under our control, while others are not under our control.”
Get a working version in front of people fast.
Using AI is not cheating. Every tool carries the work of the people who made it, and using it well is how knowledge has always moved forward. The thinking, the care for the people who live the problem, and the judgement are still yours.
“The Analytical Engine weaves algebraical patterns just as the Jacquard-loom weaves flowers and leaves.”
Open data that fits this problem.
“When you know a thing, to hold that you know it; and when you do not know a thing, to allow that you do not know it: this is knowledge.”
Tools matched to what this problem needs.
“Arise, awake; seek out the wise and learn.”
उत्तिष्ठत जाग्रत प्राप्य वरान्निबोधत
uttiṣṭhata jāgrata prāpya varān nibodhata
Ship it responsibly, and find help and funding.
“Your right is to the work alone, never to its fruits.”
कर्मण्येवाधिकारस्ते मा फलेषु कदाचन
karmaṇy evādhikāras te mā phaleṣu kadācana
Kit written for this problem from its brief; every link was checked. Links go to each provider's own site. Zetema is not paid for any listing.