Suixing

Project: Suixing

Self-reported purpose: A native iOS travel decision console that turns places into an explainable route, launches live navigation, tracks expenses from payment screenshots, and creates a shareable trip replay.

Team size: 1

Founders: zxx chen

Technology stack: app, core, ios, openai, swift, swiftui

Context: Submitted to the OpenAI 2026 hackathon on Devpost

What it is: Suixing is a native iOS application built as a travel decision console. It allows users to plan routes based on attractions and preferences, launch navigation, track expenses via OCR from payment screenshots, and replay trips visually as animated GIFs. The app uses Swift 6 and SwiftUI, integrates with MapKit and AMap for location data, and leverages App Intents and Vision for OCR and Shortcut integration.

What changed: The project is a self-contained iOS app built in a hackathon context. It does not appear to have launched or scaled beyond the prototype stage, nor does it show evidence of revenue, customers, or adoption. The description indicates that the team used AI tools (Codex and GPT-5.6) to accelerate development but did not rely on LLMs for itinerary generation.

Key open question: Is there any evidence of traction, monetization, or user feedback beyond the self-reported project description?

The description states that Suixing is a native iOS travel decision console. It allows users to:

• Turn selected attractions into an explainable route.
• Launch navigation using installed map apps.
• Check weather for both city and attraction locations.
• Record real spending via OCR from payment screenshots.
• Create a shareable trip replay as an animated GIF.

It is built with Swift 6 and SwiftUI, uses MapKit for planning and playback, integrates AMap for China POI and route data, and leverages Vision for local OCR. Payment recognition is handled via App Intents and a pure-Swift parser that ranks field semantics.

The app is structured with a core module (SuixingCore) to support models without UI, and integrates with iOS Shortcuts for payment capture.

Claim: Suixing is a travel decision console.

Evidence: The description explicitly states this.

Inference: It is an iOS-native app built in Swift and SwiftUI.

Evidence: The technology stack and architecture are self-reported.

The project’s tagline says: “A native iOS travel decision console that turns places into an explainable route, launches live navigation, tracks expenses from payment screenshots, and creates a shareable trip replay.”

It positions itself as a focused tool for travelers, not a general-purpose booking or social platform. The app is described as:

• A decision console.
• Not a booking platform.
• Not a social travel network.

The team emphasizes that it avoids LLM-generated itineraries, instead using rules and heuristics to order attractions.

Claim: Suixing is a focused travel decision tool.

Evidence: The description explicitly states this.

Inference: It is not a booking or social platform.

Evidence: The team says it avoids booking features and social sharing beyond GIFs.

The description does not name specific customer segments, but implies:

• Travelers who plan multi-stop routes.
• Users who want to track expenses from payment screenshots.
• People who value visual trip replays.
• iOS users in China (due to AMap integration and Tenpay recognition).

It is implied that the app targets individual travelers rather than groups or businesses.

Claim: The target customer is an individual traveler.

Evidence: The description implies this, but no explicit segmentation or persona is given.

Inference: It is likely for iOS users in China.

Evidence: AMap integration and Tenpay recognition suggest a Chinese market focus.

There is no evidence of pricing, monetization, or business model in the description.

Claim: No pricing or business model details are provided.

Evidence: The description does not mention revenue, subscriptions, or monetization strategies.

The app is built with:

• Swift 6
• SwiftUI
• MapKit for planning and playback
• AMap for China POI and route data
• Vision for local OCR
• App Intents for Shortcut integration
• A pure-Swift parser for OCR results

The team used AI tools (Codex, GPT-5.6) to accelerate development, particularly in debugging, UI design, and parsing OCR outputs.

Claim: The app is built with native iOS technologies and integrates with Apple ecosystem features.

Evidence: The technology stack and integration points are self-reported.

Inference: It uses AI tools for engineering acceleration.

Evidence: The authors describe using Codex and GPT-5.6 in development.

There is no evidence of traction, revenue, or user adoption beyond the project description.

The app is described as a hackathon prototype, not a launched product.

Claim: No traction or maturity signals are evident.

Evidence: The project is a hackathon submission with no mention of users, customers, or revenue.

The description does not name competitors or describe the competitive landscape.

It implies that Suixing is not a booking platform or social network, but rather a decision tool for route planning and expense tracking.

Claim: No competitor analysis is provided.

Evidence: The description does not mention any direct or indirect competitors.

• No traction or revenue evidence: The app is described as a hackathon prototype with no user base.
• Single-founder team: A team of one may limit execution capacity.
• Limited scope: The app focuses on iOS and China, which could restrict scalability.
• Dependency on third-party tools: Reliance on AMap and Apple ecosystem features may create integration risks.
• Unclear monetization path: No business model or pricing is described.

Inference: Lack of traction suggests a high risk of failure to scale.

Evidence: The project is self-reported as a hackathon submission with no evidence of adoption.

1. What is the current status of Suixing? Is it in production or still a prototype?
2. Have you tested the app with real users, and what feedback have you received?
3. How do you plan to monetize the product?
4. Are there any plans to expand beyond iOS or China?
5. What are the key technical challenges that remain unresolved?
6. How does Suixing differentiate from existing travel tools like Google Maps or TripIt?