Nicheloom

Market intelligence for builders — see what's gaining traction before it's crowded.

Rollin

Wheelchair accessibility scores for 56K+ locations (free API)

Details

External ID
47038151
Source
HN
Company
—
Product
Rollin
Website domain
joinrollin.com
Launched
Feb. 16, 2026
Cohort
—
Upvotes
6
Upvotes percentile
0.28099730458221023
Tags
—
Fetched at
Sept. 7, 2026, 9:25 p.m.
Updated at
Sept. 7, 2026, 9:25 p.m.

Description

Solo dev, Hudson Valley NY. I built ROLLIN because Google Maps gives wheelchair users a yes/no checkbox and calls it accessibility data. ROLLIN scores locations 0-100 across 6 features: wheelchair entry, accessible restroom, level entry, parking, wide aisles, elevator. Data pipeline pulls from OpenStreetMap, cross-references Google Places, and layers in community verification with a trust-weighted scoring system. Stack: Vanilla JS (no frameworks), Netlify serverless, Supabase/Postgres, Leaflet maps. ~56K locations across NY, CA, FL, MA, NJ, PA. Free to use, free API tier for developers. Paid tiers for higher volume and commercial use. Ill be happy to answer any questions. :) https://joinrollin.com API docs: https://joinrollin.com/developers

Enrichment

Theme
digital accessibility and compliance tools
Vertical
Real estate
Function
Analytics & BI
Audience
B2B
AI stance
Not AI
Project type
Commercial product
Normalized one-liner
wheelchair accessibility scores for locations
Manually corrected
False

Could you build this?

Partial The map interface and directory API are straightforward to vibe-code, but curating and accurately scoring multiple granular physical accessibility attributes across over 50,000 venues requires a complex data pipeline.

What it would actually take: The system requires a PostGIS spatial database feeding a Next.js/Mapbox frontend, backed by an ETL data pipeline that pulls from OpenStreetMap, municipal datasets, and runs NLP/vision models over venue reviews and user photos to extract specific accessibility features. The hard challenge is data resolution, deduplication, and accuracy validation for physical metrics that Google Maps and public APIs omit.

Discussion

4 comments analyzed.

Concerns raised: Documentation out of sync with actual API responses

Competitors

Other products that read as similar to this one — 15 launches clear the similarity bar, closest 8 shown.

Attention rank: #14 of 16 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).

Launched 37 days after the earliest competitor.

Other launches for this product

Same idea, different domain

Nobody's really built a analytics & bi tool for Legal yet.