I'm facing a problem about a design of a platform which provides to users a list of restaurants.
Currently, we have only 10 restaurants on it, and we're working to improve the number of the restaurants, but we need to develop a mobile app (we have only a web app at the moment).
In the web app we decided to show all the restaurants without providing a search functionality. I took this decision because I wanted to avoid having users perform a search that likely would not provide any results, as a user after the 2nd attempt will likely leave the site.
For the mobile app I think it's the same, but differently from the web version, in the mobile scope is frequently used geolocation, especially for the target to which this app will appeal (workers who are looking for a restaurant near their office).
So, I have to avoid providing textual research by providing only the geolocation, or should I avoid even the geolocation, showing only a list of restaurants?
And, what happen if a user is located in a completely different place than the restaurants? I think that is better provide only the geolocation (with a map, of course, which shows where are the restaurants).
I came up with this solution:
This is the second page of the app (the first is a sort of tutorial with the option to login and registration).
When users land in this page they are not still localized with geoloc. In this way the app can show the restaurants that are in it, to make possible that users are aware of their presence (of the restaurant). After the tap on geolocation button (SCOPRI INTORNO A ME = discover around me) the view switches on the map.
If there aren't restaurants nearby user's position, the app shows a modal dialog which says : "Sorry, there are no restaurants nearby. setted distance is 30km", and at the bottom of the dialog, two buttons, one to stay on map (to move it and look for some restaurant in other areas) and one to go back on previous page (all restaurants showed).