Background

Piclo’s services are mainly web and API based. But some tasks are better suited for mobile apps. Mobile apps allow users to act quickly while on the go. I decided to create this app to show its value and features.

The Problem

Grid Operators send dispatch instructions to Flex Providers. These are signals asking them to adjust their energy consumption or generation. Sometimes, Flex Providers must confirm if they can deliver by a deadline. This gives the Grid confidence that the delivery will happen. If not, the Grid looks for other solutions.

Confirmations can happen outside office hours. Not all Flex Providers have API integration to automate this task. How can we make it easier for users to respond?

Currently, dispatch notifications are sent by email. Users might not see them fast enough. They may have as little as 30 minutes to respond.

The Challenge

The web version of this service was already live. Data showed that 95% of users accepted all dispatches, and 5% rejected all. No one accepted or rejected selected ones, but this option still needed to be supported.

There was no "accept all" or "reject all" button. Users complained that responding one by one took too much time.

The Solution

• Create the design system for the Android app, modified from the web version.

• Drawing on the feedback from the web version, I explored different UI designs.

• Created a high-fidelity prototype ready for user testing.

Assumptions:

• Marking each dispatch one by one is more error-prone than selecting groups of responses at once.

• Users care about the potential maximum income from their decisions.

• Dispatch is easier to understand when shown as a start time with a duration, not start and end times separately.

The Outcome

• Users can accept all or reject all in seconds.

• Dispatch instructions are now clearer and easier to read.

• Users get instant notifications on their phones.