Health, home and travel decision
São Miguel Bus
A solo developer can build a usable schedule-and-weather web app in about a week using existing open-source trip planners and map/weather APIs, but reproducing any operator relationships, brand, or polished multi-platform product would be harder.
Visit website↗Built by Sousa, who ships 5 products in this index
Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$100one-off40 h to build
$20/mo3 h/mo upkeep
No published price to break even against.
No open-source build does this yet
Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.
What a replacement has to do
- Lookup bus routes and times, view route on map, check local weather
What it still won’t have
- existing brand and user base
- any proprietary live-data feeds or operator contracts
- polished UX, translations, and native mobile apps
- historical usage analytics and operational support
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
São Miguel Bus does not publish a price we could read, so there is nothing to compare against. What building costs is below.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a small web app using Node.js/Express, Postgres, React and Leaflet that serves bus schedules and a local weather forecast. In scope: CSV or GTFS import to normalize schedules into Postgres, REST API endpoints for stops/routes/timetables, React UI to search routes, render timetables, and display routes/stops on a Leaflet map, a scheduled job to fetch and cache weather from OpenWeatherMap, and a minimal admin UI to upload/replace schedule files. Out of scope: native mobile apps, payment processing, operator contract integrations, advanced analytics. Include input validation, error handling, basic tests for API endpoints, and Dockerfiles to run the stack locally and in production.
How we checked
How the score was reached
- Partly verdict base52
- Evidence score52
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 1
Every page the run actually retrieved.
- official productSão Miguel Bus — Horários, Meteorologia e Guia dos Açores
Integrity checks
What held up, and what did not.
