What Problem Does This Solve?
Empty state is the screen that people see when they start working on a task but there is no data to show yet. In the context of a map application one can easily get the impression that a map is not empty because it shows colorful content of the whole country when the opposite is true. . The end user blanks out the noise (the map without actual content) and ends up seeing nothing until focused back on something.
When to Use This Pattern
The empty state is an important (first) touch point between the user and the interface that requires special consideration when designing a map application. Typical encounters include the arrival at the application when the map shows a default extent that is most likely meaningless to the user, unfamiliar data and potentially empty content that requires some form of selection or definition to show up or being created.
What’s the Solution?
To make the empty state useful consider the user’s task and anticipate first steps so that the empty space can be utilized with call to action-elements, cartographic elements that allow the user to start interacting, or even let the user add content and therefore fill the space in a way that makes sense.
Why Use This Pattern?
Leaving something blank, empty or without cues on what to do next does not make a good first impression and leaves the user wondering of what to do next.