Building Tamermap: A Map for Pokémon Card Collectors and Local Shops
How Mark DeVore built Tamermap, and the product decisions behind a map for collectors and independent card shops.
I built Tamermap because collectors were piecing together shop hours, kiosk lists, and routes from too many sites, while independent shops had no simple way to correct their own listings. It is an independent software project I develop and operate, separate from client advisory work.
The useful part for a business owner is not the Pokémon theme. It is the set of decisions: two kinds of users, a free core, paid extras that do not buy ranking, and a refusal to pretend the map knows what is in stock.
Finding the right shop shouldn’t require ten different websites
A collector planning a Saturday trip may bounce among search results, shop websites, social pages, and separate kiosk lists just to answer three questions: what is nearby, when is it open, and which stops make a sensible route? Tamermap brings those tasks into one map, with independent card shops treated as destinations and vending kiosks available as additional stops.
The information is only as useful as it is current. Shops change hours, move, or close, while some listings have incomplete details. Tamermap therefore combines maintained location records with owner corrections and claims. It improves discovery without pretending that every listing is perfect—or that a shop shown on the map has cards in stock.
More than a map of card shops
The collector experience follows the decisions involved in a real outing. A user can search an area, compare nearby shops and kiosks, review public hours and contact information where available, and filter the visible results. “Open Now” uses published operating hours; it is a planning aid, not a guarantee that a door is open or product is available.
From there, route planning turns a group of pins into a multi-stop trip. A free account can keep private visit notes. Optional planning tools extend that workflow. The tradeoff I kept: personal history stays private, and none of it claims to know what a shop has on the shelf.
Giving independent card shops a place on the map
Tamermap also has to work for the businesses collectors hope to find. An independent shop owner can claim an existing listing for free. After approval, the owner dashboard provides controls for business hours, contact details, descriptions, notices, and storefront photography.
Optional Spotlight features give participating shops a richer presentation, including additional profile and gallery elements. They do not purchase preferential route ranking. That distinction matters: the collector side depends on useful, credible planning, while the merchant side needs practical tools for presenting accurate public information. Serving both audiences in one application requires clear boundaries between discovery, listing management, and paid presentation features.
The technology behind the map
Location data is the foundation, but storing coordinates is only the beginning. Records need useful business details, hours need to support filters, and a dense field of markers has to remain navigable on both a desktop screen and a phone. The interface must reveal enough information to support a decision without burying the map under controls.
The more interesting work is turning those records into tools. Search, operating hours, map filters, route planning, and private visit history each answer a different part of the same question: where should a collector go next? Their value comes from working together while keeping activity heatmaps and personal observations clearly separate from live inventory—which Tamermap does not provide.
Underneath that experience is a custom web application built with Python and Flask, PostgreSQL-backed location data, Google Maps, and cloud infrastructure that includes Cloudflare. The collector map and shop-owner dashboard share data, but they present different workflows. Keeping those experiences coherent is as much a product-design problem as a programming one.
What stays free
Browsing the map is free, and shop owners can claim a listing without paying. Optional collector planning tools and an optional shop presentation are separate. Paying does not buy a better place in someone else’s route, and it does not promise inventory, traffic, or sales. That boundary was a product decision, not a footnote.
And then there’s Hunter
Hunter, the raccoon mascot, stands in for the collector: he plans a loop and remembers an earlier stop, and he still does not know what is on the shelf.
From a practical problem to a working product
Tamermap illustrates what practical software development looks like after the map first appears on screen. Different users need different controls. Complex location information must become understandable actions. Free access and optional services need boundaries that make sense, and a working application must keep adapting as data, devices, and user expectations change.
The result is a working system for a narrower problem. The part that carries into advisory work is the judgment underneath it: who the system is for, what it should refuse to promise, and what still has to work after launch.