Hi product Hunt!
I’m Lars, based in Stockholm. I’m not a full-time developer — I work in sales and build things on the side — so I’m still learning a lot as I go.
I’ve been working on ParkSpot, a small web app that offers a new way to find street parking in Stockholm. It came out of a problem I kept running into myself: constantly circling the block, never sure where I could actually park without getting a ticket on street-cleaning days.
The core idea — and the little trick that makes it different — is that ParkSpot shows you the streets where cleaning has just finished, and the ones where it’s coming up next. That way you always know where your odds of finding a spot are best.
It’s early and far from perfect, so I’d really appreciate any honest feedback or ideas. And I’d love to check out what you’re all building as well.
New feature: MC parking
Thanks for having me!
Replies
Welcome Lars. You buried your own tagline in the third paragraph.
Everyone treats street cleaning as the thing that gets you a ticket. You worked out that it is also the thing that empties a street, so the restriction is the supply signal. That is the whole product in one sentence: park where the cleaning just finished. I would put that line above the map, because every parking app has a map and none of them have that.
Does the schedule data come from the city, or are you inferring it from something else? That feels like the part that decides whether this stays Stockholm only.
Thanks Abdullah, this is really sharp feedback. You're right about the tagline — I'll pull "park where the cleaning just finished" up above the map. That's exactly the angle that sets ParkSpot apart from every other parking app, and it deserves to be the first thing people see.
Good question on the data. The schedule comes from the city's open data on street cleaning times per street. That's also the crux of whether this scales: every new city depends on equivalent data being available and in a format I can trust. Stockholm is a good starting point because the data is relatively structured here, but you put your finger on exactly the thing that decides how far this can go.
@lars_sjogren The structured data in Stockholm is the part that will mislead you. The break does not come at city two. It comes at the first city that publishes the same schedule in a different shape, and that is when you find out whether you built a Stockholm parser or a schedule model.
My own app had the country code hardcoded in five separate places. All five were invisible until there was a second country.
@abdullah_javaid3 Thanks for your wise comments. I do agree . Thats for sure next step. A parse plugin future