Founder-led side project · Working prototype
A calmer route from choosing a cause to seeing its impact
I researched, designed and built Altrue as a working Flutter prototype for recurring microdonations. It was tested through early community conversations; it is not a launched service and this case does not claim product traction.
Relevant for: 0→1 products · Founder-led MVPs · Research to prototype
- Role
- Founder / Product Designer
- Period
- 2023–Present
- Built
- Flutter prototype · Supabase · GlobalGiving API
- State
- Prototype—not a launched service
Core sequence: choose the causes that matter, then see what recurring contributions funded.
01 · Problem and evidence
Giving required too much certainty too early
People wanted to help but faced too many charities, unclear evidence and guilt-led appeals. The product question became: how might a small recurring contribution feel understandable, voluntary and worth continuing?
01
Transparency
People wanted to know where money went and receive regular impact updates.
02
Manageable commitment
Recurring contributions of €10–€25 per month felt more approachable than a large one-off ask.
03
Familiar framing
A subscription model made the commitment easier to understand without presenting it as irreversible.
Evidence came from a Typeform survey, early interviews and conversations in effective-altruism communities. The sample supported product direction, not a market-size or traction claim.
02 · From structure to product
Two screens defined the MVP
Early wireframes tested whether cause selection could reduce choice overload and whether an impact report could close the feedback loop. Profile, community and partner features stayed outside the core sequence.
Cause selection: a small, curated set rather than an open-ended directory.
Impact report: concrete funded outcomes instead of points, streaks or social pressure.
03 · Core product sequence
Choose, contribute, understand
The high-fidelity flow keeps commitment calm and reversible. Cause choices shape a monthly plan; the product then reports specific outcomes funded by the recurring contribution.
Choose causes
Set a monthly plan
See funded outcomes
04 · Optional guidance
Guidance for questions—not a persuasion engine
The guide explored how dense effectiveness research might become easier to ask about. It was designed to stay neutral, show source context and leave the final choice with the user. It remains a prototype feature, not evidence of recommendation accuracy.
Mobile guidance with a cautious answer and a visible charity recommendation.
Desktop view keeps previous questions, evidence and action in one place.
05 · Interface system
Warmth with explicit trust states
Fraunces distinguishes explanatory guidance from the utilitarian interface; Inter carries actions and navigation. Pink and purple mark moments of progress, while verified and secondary states stay quieter. The same components map into the Flutter prototype.
Primary, secondary and new-chat actions.
Favourite and verified-charity states keep trust cues close to the action.
06 · Contribution and reflection
What the prototype proved—and what it did not
Altrue proved that I could move from research and product framing into a working cross-platform prototype. It helped make cause discovery and impact reporting tangible enough for early conversations. It did not prove acquisition, retention, donation volume or charity impact.
The product lesson
Calm, unpressured giving was the stronger direction. Shareable reports can remain optional, but points, streaks and community comparison should not drive the core experience. Trust comes from clear choices, cautious claims and a visible feedback loop.
CURRENT STATE
Working Flutter prototype using Supabase and the GlobalGiving API. Founder-led concept; not a launched service.