As of 27 September 2026, the 8 October showcase is 11 days away. A staffed collection point and a 20–50-device physical pilot cannot responsibly be promised within that window. The public app can be demonstrated now; user testing and partnership conversations are the immediate priority.
- Invite a small group of actual students, ideally 6–9 as a recruitment target, to try the live app with a device they own or a realistic hypothetical. Do not write a result before a session occurs.
- Observe whether they can complete an assessment, understand the route and caution, identify the correct public endpoint, and explain what marking a step done does and does not prove. Ask what they would do next and whether anything was confusing.
- Record anonymous session outcomes in the showcase test log; do not capture names, student IDs, serials, IMEIs, screenshots of personal devices or sensitive contents.
- Correct any misleading paths or wording, then present the actual participant count and observed findings. If no sessions occur, say so.
- Follow up on the MobileMuster feedback email. A response is feedback, not a signed partnership unless it explicitly authorises a defined arrangement.
An initial 20–50 devices is a planning range only, contingent on promotion, permission, staffing and an agreed handover process. A university owner must approve the site, privacy handling, safety protocol and communications. University IT must define managed-device handling. Any donation/repair/recycling endpoint must confirm accepted items, data responsibilities and evidence available. The team should not accept, store, transport or wipe devices under the public app alone.
Start with one approved campus location and a limited category (for example, ordinary personal phones). Keep the app as a decision layer; a named operator handles the physical service. Establish what qualifies as a completed outcome and how to count it without personal identifiers before the first event.
| Gate | Evidence needed before launch |
|---|---|
| Campus owner | Written approval for location, dates, staffing and communications |
| Privacy and safety | Agreed data minimisation, retention, incident and damaged-battery procedures |
| Handover | Named provider, accepted items, custody boundary and data-handling responsibility |
| Measurement | Anonymous definitions for assessed, prepared, handed over, accepted, completed, rejected and unverified |
| Claims | No mass or carbon result unless measured inputs, method and verification support it |
No university, MobileMuster or NTCRS agreement is currently confirmed. No pickup service or revenue exists. The institution-funded service model is a hypothesis for interviews, not a financial forecast.