Córdoba Connect: Smart Multimodal Mobility

The description states that Córdoba Connect is an Android app built in Kotlin using Jetpack Compose and Material 3. It compares AUCORSA buses, Renfe Proximidad rail services, walking, and cycling for door-to-door journeys.

It uses:

• Google Maps and Places for location search.
• FastAPI as a backend API layer between the Android app and OpenTripPlanner.
• OpenTripPlanner with an OpenStreetMap extract of Córdoba and GTFS datasets from AUCORSA and Renfe.
• Firebase for optional cloud synchronization (anonymous authentication, Firestore).
• Local storage using Room and SQLCipher with encryption via Android Keystore.

The app supports:

• Address-based origin/destination selection.
• Time-based journey planning (now or specific time).
• Visualized routes with distinct styling per transport mode.
• Fare notices for separate tickets or transfers.
• Saved commutes stored locally and optionally synced to Firebase.
• Bilingual interface in English and Spanish.

Not evidenced No revenue, customer base, pricing model, or user adoption data is provided. The app is described as a prototype built during a hackathon.

The author positions Córdoba Connect as:

• A bilingual Android companion for navigating Córdoba.
• A tool that brings together multiple transport modes in one interface.
• An alternative to Google Maps, which the author claims sometimes misses AUCORSA connections due to misconfigurations.

Key claims include:

• It offers door-to-door experience designed specifically for Córdoba.
• It helps users avoid checking several apps or memorizing timetables.
• It provides practical journey alternatives, including walking/cycling recommendations when competitive with public transport.

The app is described as a “coherent, working product”, not just a demonstration. The author emphasizes that it treats data quality as part of the user experience — clearly indicating scheduled data rather than real-time.

Inferred The positioning suggests a local-first mobility solution aimed at improving urban navigation for residents and commuters in Córdoba.

The description states:

• The app is built specifically for Córdoba, targeting users who travel within the city.
• It caters to recurring journeys such as commuting to work or university.
• Users can save frequently used routes as workday or weekend commutes.

Not evidenced No explicit segmentation beyond “users of Córdoba’s transport system.” No demographic data, usage frequency, or geographic scope beyond Córdoba is stated.

The description does not provide any information about:

• Revenue streams.
• Pricing models.
• Monetization strategy.
• Subscription plans or in-app purchases.

Not evidenced There is no indication of how the app would generate income, if at all. The project is described as a hackathon prototype with no mention of commercial viability or business model.

The author reports:

• The app is built using Kotlin, Jetpack Compose, and Material 3.
• Backend uses FastAPI to interface with OpenTripPlanner.
• Routing engine powered by OpenTripPlanner, using GTFS and OpenStreetMap data.
• Data persistence handled via Room + SQLCipher, with encryption via Android Keystore.
• Optional cloud sync through Firebase Anonymous Authentication and Firestore.
• Infrastructure is containerized using Docker.
• CI/CD pipelines include validation for both Android and Python code.

Inferred The technical stack suggests a modern, scalable architecture that supports local-first design, secure data handling, and reproducible builds. The use of AI tools (Codex + GPT-5.6) indicates an engineering process focused on rapid iteration and problem-solving across layers.

The description states:

• This is a hackathon submission.
• It is described as a working prototype, not a production-ready product.
• The app includes encrypted local storage, optional cloud sync, and bilingual support.
• It has been tested in CI/CD environments and supports automated validation.

The description does not mention:

• Direct competitors.
• Existing mobility apps in Córdoba.
• How this differs from Google Maps, Citymapper, or other transit planners.

Not evidenced No competitive analysis is provided. The author only claims that Google Maps sometimes misses AUCORSA connections — no comparison with other tools or market positioning.

Key risks inferred from the description:

1. Data dependency on outdated GTFS feeds: The app uses an expired AUCORSA snapshot and relies on a projected calendar, which may not reflect real-time service changes.
2. Limited scope: The app is built for Córdoba only; no indication of expansion plans or multi-city support.
3. Prototype nature: It’s described as a hackathon prototype with no commercial traction or monetization strategy.
4. No user feedback loop: No mention of user testing, surveys, or iterative improvements beyond the hackathon phase.
5. AI dependency: While GPT-5.6 was used for engineering, there is no indication that AI will be used at runtime in the app.

1. Is Córdoba Connect intended to evolve into a commercial product or remain a local prototype?
2. What are the plans for updating and maintaining the GTFS data feed from AUCORSA?
3. Are there any partnerships or agreements with local transport providers (AUCORSA, Renfe)?
4. How does the app handle disruptions or delays in real-time, if at all?
5. Has there been any user testing beyond the hackathon environment?
6. What is the long-term vision for expanding to other cities or regions?
7. Are there any plans for monetization or revenue generation?