A portfolio too big to browse as a list
1:37 is a Latvian real estate company with more than 500 apartments on its website. We built them a custom map component inside their existing Framer site: every building on a Mapbox map, seven filters plus search, and each building showing which of its apartments are still available. It went live without another website migration and without a native Framer API.
This is the story behind it: the data problem, the workaround and what changed. The short version is on the 1:37 property map case study.
One building, fifty apartments
After 1:37 moved their website from WordPress to Framer, the portfolio grew past 500 apartments. A single building could hold 50 of them, some already reserved or sold. Visitors had no way to see where the properties were, or what was still available in a building, without opening listings one by one.
The real problem was the shape of the data. One building record links to many apartment records, and each apartment has its own status: available, reserved or sold. Framer's built-in components could not show one-to-many collections with filters on a map.
No API, so we built around the export
Framer had no native API for this at the time, and moving the whole site again was not an option. So we used what Framer did have: a CMS export file.
The team exports the collections and drops the file into a simple upload form. The map component syncs from it. Listings are still edited in Framer CMS exactly as before, and new ones go in as a batch, even hundreds at a time.
It is a small example of a bigger rule: keep the tool the team already knows, and build the missing part next to it. We wrote about that in What the layer between your tools actually is.
Seven filters that move the list and the map together
The component shows every property on a Mapbox map, with markers grouped into numbered clusters as you zoom out. Search and seven filters (price, rooms, type, availability, deal, district and whether the property is offered by 1:37) update the list and the map at the same time.
Because buildings and apartments are read as linked records, a building only shows what is still available inside it. On desktop, the list and the map sit side by side. On mobile there is a map and list switch with its own layout logic, because a split screen does not work on a phone.
A custom component inside the site they already had
The result is one code component on 1:37's existing Framer website, not a separate app and not a new platform. Visitors find properties by area instead of paging through a list. Reserved and sold units are filtered out, so buyers only see what they can still get.
“Now listings go in as a batch, even hundreds at a time, and show up on a dynamic property map.”Dzintars Berzins, CEO / Founder, 1:37
What changed
The team keeps working the way it did, and the website finally shows the portfolio the way buyers look for a home: by place first. If your website stops doing its job at a similar point, see our websites and web apps work.
