DEV Community

Yurii Nazarenko
Yurii Nazarenko

Posted on Edited on Fully Autonomous

Building TapMap: why we put discovery and friends on the same map

TapMap app screenshots: maps, place cards and discovery

I'm Yurii Nazarenko, the founder of TapMap. Our five-person team is building a social app around a question people ask every day: where should we go right now, and who with?

We started in Phuket and released on web, Android and iOS. This is a product development note adapted from our new TapMap overview, with a few lessons from validating the app.

The map is the starting point

Choosing a place often means switching between a map, restaurant reviews, a menu, an events list and a group chat. Our product decision was to bring those steps into one place.

TapMap combines a map with a swipeable deck of places. A card shows a photo, cuisine, price information, distance and available opening-hour information. Saving a card puts it in Favourites. Recommendations take account of preferences, time of day and weather.

That makes data quality part of the interaction design. A compelling card is not useful if its opening hours or prices are wrong. Available information can be incomplete, so we describe opening hours as a ranking signal rather than a guarantee that a venue is open.

Discovery has a social next step

Finding a place is only half the task. The next question is often who can join you.

Friends can choose to share their location, chat, plan a route and call from the app. Location sharing is optional and controlled by the person sharing. We also make home visibility a separate choice: showing a friend where you are should not silently reveal your home to everyone.

There is a cold-start problem here. A social feature becomes useful when your friends are already using it. We therefore need discovery to be useful before a person has built a network inside the app. People can start exploring without creating an account and save their progress later.

Let users change the map

We also let people create and share maps of their own places. A personal collection can become a reusable guide instead of remaining a list of links in a chat.

The Style Studio lets users change colours, labels, icons and 3D buildings. Styles can be shared through the in-app marketplace. This makes the map a surface people can shape, rather than a fixed visual background.

How we tested demand

We launched in one initial market, Phuket, across all three platforms. With small test budgets in three languages, we looked for an audience that would actually use the app.

We tracked behaviour beyond installs: saved places, routes and returns after a day and a week. We compared the product with services such as Tripadvisor, Yelp and Polarsteps. We also saw people from Kazakhstan searching for TapMap by name after YouTube Shorts.

These observations are signals to investigate, not a claim that we have solved retention. The hardest part is still turning a first visit into a habit.

The challenges that remain

For a small team, the work is both social and technical: keeping a map with tens of thousands of places responsive on a phone, releasing updates across three platforms from one codebase, and making the app worth reopening before a user's friends arrive.

A virtual cat companion, quests and custom cars give the product personality. But the basic test remains practical: did someone find a place they wanted to visit, save it, plan a route, and come back?

The full product tour is available on Medium. TapMap is free on iPhone, Android and the web, in English, Thai and Russian.

What helped your app become useful before its social network reached critical mass?

Disclosure: I am TapMap's founder. This article was adapted and translated with AI assistance from our own product material and founder notes.

Top comments (0)