Archive position — measured, not model output
0 likes on Devpost
2,264 of the 7,856 archived projects have more likes, and 5,592 share exactly 0 — so this project's #7,701 place in the like-ranked listing is a tie-break inside that group, not a ranking.
Projects (log scale)
Likes on Devpost. ▲ marks this project's group.
Show the figures
| Likes | Projects | Share of archive |
|---|---|---|
| 0 | 5,592 | 71.2% |
| 1 | 1,758 | 22.4% |
| 2 | 285 | 3.6% |
| 3–4 | 132 | 1.7% |
| 5–9 | 75 | 1.0% |
| 10+ | 14 | 0.2% |
Executive Summary
What the company appears to be
WIMB (Where Is My Bus?) is a self-reported, single-person project that builds a glanceable, real-time bus arrival display for commuters. It uses public GTFS and GTFS-Realtime feeds from Golden Gate Transit to show scheduled and live bus data on a mobile interface.
What changed
The author states they built this in under a day as a personal solution to their daily commute. There is no evidence of prior product iteration or commercial traction.
Single most important open question
Is there any evidence that WIMB has been adopted by users beyond the founder, or that it has moved beyond a proof-of-concept?
What The Product Actually Is
The description states that WIMB is a mobile interface that displays real-time bus arrival information for a single route (154) and stop. It shows:
- Scheduled arrival time
- Live vehicle ID
- Second-accurate ETA
- Last confirmed stop behind the estimate
- Realtime-data freshness
- Honest timetable-only states when tracking is unavailable
- Clear message when service ends
It is built with FastAPI, HTML/CSS/JS, and deployed on a DigitalOcean Droplet. There is no database in this POC.
Evidence
- The author's own write-up describes the product’s features.
- Technology stack includes FastAPI, HTML/CSS/JS, Python, Git, Uvicorn, Caddy, systemd.
- No mention of any backend database or persistent storage beyond caching and audit logs.
Inference The product is a single-page application with no user accounts or data persistence beyond per-trip checkpoints and cache TTLs.
Positioning & Claim Evolution
The author states that WIMB is built for “the trip you take every day.” It aims to eliminate the need for transit apps that require navigation, maps, and multiple screens. The product is described as a “glanceable” experience that answers one question: Where is my bus?
Evidence
- Tagline: “WHIM is built for the trip you take every day.”
- Claim: “The bus stop arrival screen that actually works, on your phone.”
- Product philosophy: “No maps. No trip planner. One glance, one answer.”
Inference WIMB positions itself as a minimal, no-frills solution to a common commuter pain point — the lack of reliable, clear real-time information at bus stops.
Target Customer & ICP
The description states that WIMB is built for daily commuters who take the same route and stop. It is described as solving the problem of “guessing” when a bus will arrive, especially when physical displays are broken or unavailable.
Evidence
- The author’s personal commute is used as the example.
- The product is limited to one route (154) and one stop for this POC.
Inference The initial ICP appears to be a single user — the founder — who is solving their own problem. No evidence of broader customer segments or personas.
Business Model & Pricing Evidence
There is no evidence in the description of any business model, pricing, monetization, or revenue streams.
Evidence
- The product is described as a personal solution.
- No mention of users beyond the founder.
- No pricing, subscriptions, or commercial offerings are stated.
Inference The project is self-reported as a proof-of-concept with no indication of commercial intent or monetization.
Technical & Delivery Signals
WIMB integrates static GTFS data with GTFS-Realtime feeds from Golden Gate Transit. It uses:
- FastAPI for backend
- HTML/CSS/JS for frontend
- Uvicorn, Caddy, systemd for deployment
- A short-TTL memory cache to limit API traffic
- Cron jobs and expiring checkpoints for tracking
- Audit logs for validation
Evidence
- The author describes how the system is built.
- No database is used in this POC.
Inference The technical stack is minimal, focused on delivering a lightweight, real-time experience. It’s not scalable or production-ready beyond a single user and route.
Traction & Maturity Signals
There is no evidence of any traction, users, or adoption beyond the founder's personal use.
Evidence
- The product was built in less than a day.
- No mention of users, customers, or feedback.
- No data on usage frequency or retention.
- No mention of deployment beyond a single DigitalOcean Droplet.
Inference This is a proof-of-concept with no evidence of user engagement or product maturity.
Competitive Context
The author states that existing transit apps require “navigation maps, trip planners, and multiple screens” to answer the question “Where is my bus?” WIMB aims to be a simpler alternative.
Evidence
- The author identifies a gap in current tools.
- No mention of competitors or market analysis.
Inference WIMB competes with transit apps that are more complex than needed for simple, glanceable information. However, no competitive landscape is described.
Key Risks & Red Flags
- No user base or traction: The product is self-reported as a personal solution with no evidence of adoption.
- Limited scope: Only one route and stop in the POC.
- No commercialization strategy: No indication of monetization, scaling, or long-term vision.
- Single-person team: No team structure or support for growth.
- Unverified data reliability: The author notes that “realtime” data is not always reliable.
Inference This project is a personal hackathon solution with no commercial viability or scalability.
Diligence Questions To Ask The Founders
- What is the actual user base beyond yourself?
- How do you plan to scale beyond one route and stop?
- Are there any plans for monetization or commercial use?
- What are your long-term goals for WIMB?
- How do you handle data reliability issues in real-world deployment?
Investment/Partnership Verdict
Not evidenced: There is no evidence of revenue, customers, traction, or a scalable business model.
Confidence level Low. This is a self-reported personal project with no commercial evidence.
Verdict This is a proof-of-concept product with no demonstrated commercial viability or user adoption. It should not be considered for investment or partnership unless further evidence of traction, scalability, or commercial intent emerges.
Source
Submitted to the OpenAI 2026 hackathon on Devpost. Project home on DevPost.
The analysis above was generated by a language model from the project's own one-line description. It is not independent research and contains no verified traction, revenue or customer data.