Demo Approach
HYPOTHESIS: thoughtful placement of page elements and interactivity can build a sense of curiosity and empowerment in the user, while content can create an emotional connection that drives action.
Key points
- The front-end makes calls to a minimally designed API, backed by mocked demo data.
- The tech stack aligns with GoFundMe preferences, including deployment to AWS.
- The focus of AI in this project was development acceleration and fraud metrics.
Stack and rationale
| Layer | Choice | Why it matters |
|---|---|---|
| Frontend | Next.js App Router + React | Fast route iteration and static-first demo pages without tooling overhead. |
| Contracts | TypeScript contract module | Shared response types keep page and API assumptions aligned. |
| Data model | Projection layer over snapshot fixtures | Deterministic outputs for reliable demos and reproducible walkthroughs. |
| Deployment | AWS Amplify hosting | Production-like URL and repeatable measurement environment. |
Delivery tracks
| Track | Scope | Executive signal |
|---|---|---|
| Experience routes | Profile, Fundraiser, Community, Dashboard | End-to-end user and internal workflow narrative is visible. |
| Trust posture | Integrity signals + fraud triage artifacts | Explains how platform trust and safety concerns are surfaced. |
| Operational proof | Metrics + performance validation pages | Claims are backed with measured data and explicit thresholds. |
Risk and mitigation
- Risk: over-indexing on slideware. Mitigation: live route walkthrough is center of demo.
- Risk: stale claims. Mitigation: values on demo pages are sourced from committed artifacts.
- Risk: trust ambiguity. Mitigation: AI/fraud actions are made explicit in metric tables.