Survey App

Design Process

The brief arrived as a technical problem, so we spent the first conversations turning geofencing and offline sync back into a question about people standing in a store with a phone and a schedule. We mapped a surveyor's day across multiple sites, where appointments stack up, signal drops without warning, and a lost form means driving back. That gave us the rule the whole design runs on: nothing the surveyor does should ever depend on a connection, and nothing should silently fail. We designed the offline state first instead of last, so saved, queued and submitted are three visibly different things a person can check at a glance. Forms had to adapt per project without becoming a settings maze, so we built a configuration model in the web portal that produces short, ordered questions in the app rather than long ones. We are testing the capture flow with real site conditions in mind, one-handed, outdoors, sometimes in a hurry, because a survey that is easier to postpone than to complete will get postponed. The system is being built as one component set across the app and the portal, so a form configured on a laptop and answered on a phone stay recognisably the same thing.