Related Problem
Fredy already lets users add home/work addresses and shows the distance
(km/miles) between those addresses and each listing. It also shows nearby
transit stops and their upcoming departures on the listing detail map
(transit.nearbyTitle etc.).
However, there is currently no way to see how long a transit journey would
actually take between a saved home/work address and a listing — e.g. "45
min, 1 transfer" via public transport. Straight-line distance alone is not
very useful in cities where transit routes are indirect (rivers, lack of
direct lines, etc.), which matters a lot for apartment hunting in Germany.
Proposed Feature
For each listing (and/or in the map/detail view), show an estimated public
transit travel time and route summary between each saved address and the
listing, similar to how Google Maps shows "Directions - transit" results
(duration, number of transfers, departure/arrival time).
Alternatives Considered
No response
Benefits
- More realistic apartment comparisons: straight-line distance can be
misleading in cities with rivers, parks, or indirect transit networks
(e.g. two listings 2 km apart can differ by 20+ minutes in actual commute
time). Transit duration reflects what commuting actually feels like.
- Faster decision-making: users could filter or sort listings by
"under 30 min to work" instead of manually checking each address on
Google Maps, saving time during a stressful apartment search.
- Consistent with Fredy's existing philosophy: Fredy already computes
distance and shows nearby transit stops/departures — this feature closes
the gap between "how far" and "how long it actually takes to get there,"
making the existing location data genuinely actionable.
- Differentiator vs. manual portal browsing: none of the scraped
portals (ImmoScout24, Immowelt, etc.) show commute time against a
personal address, so this would be a meaningful advantage unique to
using Fredy.
Additional Context
No response
Related Problem
Fredy already lets users add home/work addresses and shows the distance
(km/miles) between those addresses and each listing. It also shows nearby
transit stops and their upcoming departures on the listing detail map
(
transit.nearbyTitleetc.).However, there is currently no way to see how long a transit journey would
actually take between a saved home/work address and a listing — e.g. "45
min, 1 transfer" via public transport. Straight-line distance alone is not
very useful in cities where transit routes are indirect (rivers, lack of
direct lines, etc.), which matters a lot for apartment hunting in Germany.
Proposed Feature
For each listing (and/or in the map/detail view), show an estimated public
transit travel time and route summary between each saved address and the
listing, similar to how Google Maps shows "Directions - transit" results
(duration, number of transfers, departure/arrival time).
Alternatives Considered
No response
Benefits
misleading in cities with rivers, parks, or indirect transit networks
(e.g. two listings 2 km apart can differ by 20+ minutes in actual commute
time). Transit duration reflects what commuting actually feels like.
"under 30 min to work" instead of manually checking each address on
Google Maps, saving time during a stressful apartment search.
distance and shows nearby transit stops/departures — this feature closes
the gap between "how far" and "how long it actually takes to get there,"
making the existing location data genuinely actionable.
portals (ImmoScout24, Immowelt, etc.) show commute time against a
personal address, so this would be a meaningful advantage unique to
using Fredy.
Additional Context
No response