ArriveAble

Company: ArriveAble

Self-reported basis: The analysis is based entirely on the project description provided by the author — its name, tagline, the author's own write-up, and any technology tags. No external verification or archived data are available.

What it appears to be: A lightweight web application that recommends accessible on-campus journeys using a mix of official campus data sources, OpenStreetMap, and AI-assisted development tools. It is designed for university students and staff navigating campuses with mobility needs.

What changed: The author describes building a prototype over the course of a hackathon, integrating multiple data sources into a single route-planning tool with accessibility preferences.

Most important open question: Is there evidence of traction or user adoption beyond the prototype?

The description states that ArriveAble is a lightweight web app built with HTML, CSS, JavaScript, Leaflet, and a small Node.js API layer. It uses a campus-adapter architecture to integrate data from various sources including:

• Official campus maps and PDFs
• Live ArcGIS parking feeds
• MazeMap POIs
• OpenStreetMap geometry (footways, cycleways, transit stops, parking)
• Publicly available parking data

The app supports journey planning for car, motorcycle, bicycle, and on-campus public transport, with accessibility preferences such as wheelchair/mobility needs, ACROD, permit, courtesy-bay, and electric-parking. It also includes a backup parking recommendation system and a weekly late-class safety planner.

The app is described as using GPT 5.6 and Codex to assist in development, debugging, and UI refinement.

Inference: The product appears to be a proof-of-concept prototype built for a hackathon, not yet a commercial offering.

The author states that ArriveAble was inspired by the idea that “the journey on-campus deserves the same care as the journey to campus.” It is positioned to make arrival planning more inclusive by recommending fast and reliable journeys tailored to user needs, including accessibility requirements.

It also claims scalability to larger areas such as city parking, with support for live parking occupancy data from cities.

Inference: The positioning suggests a focus on accessibility and inclusivity in campus navigation. However, the claim of scalability is not substantiated by evidence of real-world deployment or integration beyond university-level prototypes.

The description states that ArriveAble is designed for university students and staff navigating campuses with mobility needs. It supports users who require accessible entrances, parking, and pathways, including those with wheelchair access, ACROD, permit, or electric-parking requirements.

It also mentions support for late-class safety planning, suggesting a user base that may include students with irregular schedules or those needing extra time to reach their destinations.

Inference: The ICP appears to be university users with mobility needs. No evidence is provided of broader customer segments or commercial targeting beyond the prototype.

The description does not provide any information on pricing, revenue streams, or business model. It only describes a prototype built for a hackathon and does not mention monetization, subscriptions, partnerships, or sales.

Inference: No evidence of a business model or pricing strategy exists in the provided description.

The app is built with:

• Frontend: HTML, CSS, JavaScript, Leaflet
• Backend: Node.js API layer
• Data sources: Campus maps, ArcGIS feeds, MazeMap, OpenStreetMap, PDFs, live parking data
• Development tools: GPT 5.6 and Codex

It uses a campus-adapter architecture to normalize route data from multiple sources and supports:

• Typed building/classroom destinations
• Multiple travel modes (car, bike, public transport)
• Accessibility preferences
• Source-linked parking costs and availability
• Backup parking recommendations
• Mobile-navigation concept with terrain-aware alerts

Inference: The technical approach shows a modular, scalable architecture. However, no evidence of production deployment or performance metrics is provided.

The description states that ArriveAble was built as a hackathon prototype, and the author mentions working on it over the course of a single hackathon. It supports three universities: Curtin University Bentley, James Cook University Townsville, and Charles Darwin University Casuarina.

There is no evidence of:

• User adoption
• Customer feedback
• Revenue or monetization
• Product iteration beyond prototype stage
• Deployment in production

Inference: The product is at a prototype stage, with no evidence of traction or commercial maturity.

The description does not mention any direct competitors. It focuses on accessibility and campus navigation, but does not compare ArriveAble to existing tools or platforms in the market.

Inference: No competitive landscape is described or implied.

• Prototype-only status: The product is described as a hackathon prototype with no evidence of commercialization or traction.
• No revenue or monetization strategy: No indication of how the product would generate income.
• Data dependency and quality issues: The app relies on multiple data sources, some of which may be inconsistent or incomplete.
• Limited scalability claims: While it mentions scalability to city parking, no evidence supports this beyond the prototype stage.
• No user feedback or testing: No mention of real-world user testing or feedback loops.

Inference: The lack of traction, monetization strategy, and production deployment raises significant questions about commercial viability.

1. What is the current status of the prototype — is it being used by any university or campus group?
2. How are you planning to monetize this product if at all?
3. Have you tested the app with real users, and what feedback have you received?
4. What are your plans for expanding beyond the three universities currently supported?
5. How do you plan to handle data quality issues across different campuses and sources?
6. Are there any partnerships or institutional support in place for scaling this product?