Where it started
An educational visitor guide needs places, images and narration to work on phones across different school levels. Physical-device playback and package constraints matter as much as the interface.
My contribution
I worked on the guide's implementation and troubleshooting, including profile and school-level entry flows, device-side voice failures and asset synchronization across delivery packages.
The final mile often lives in a real phone and a publishing constraint.
Three engineering decisions
Organize around the visitor
Separate entry points and permissions by school level, with higher levels able to access lower-level content.
Give voice failures a fallback
Investigate playback paths and voice services, and provide subtitles on failure or timeout.
Treat packaging as delivery
Check and adjust image and audio size while preserving resource paths, then synchronize the delivery packages.
What came out of it
- Historical conversations document guide features, school-level access, device voice troubleshooting and package synchronization.
- Later user feedback accepted the application at that stage, followed by a request to address upload asset sizes.
- No claim is made about current live availability, official partnerships, audience size or real-time AI narration.
Historical feature and delivery records; live service not retested here
What's next
Prepare shareable interface assets and a current physical-device recording before a new end-to-end acceptance check.
Project notes are grounded in reviewed source, experiment records and personal confirmations.
Content reviewed: 2026.10.28