China's Travel AI Is Already Booking Through the Phone's OS, Not an App

Chinese travel platform Fliggy has pushed its open-source “flyai” travel skill — covering flights, hotels, attractions, ground transport, and packages — directly into the native device skill stores of Huawei, Xiaomi, OPPO, and Honor, according to a Hospitality Net opinion piece by Terence Ronson. That lets guests book without ever opening the Fliggy app: the decision-making layer moves from app-based discovery to whatever AI agent already lives on the phone. Ronson cites an 800% surge in AI-driven bookings during Spring Festival, with conversion rates for air tickets, train tickets, and attractions now matching traditional OTA channels, and 755 million monthly active users across these OEM-native assistants combined.

The infrastructure shift behind that number is real: HarmonyOS now holds 19% of the China OS market, ahead of iOS’s 16%, and Ctrip is separately forecasting inter-provincial travel orders up 45% year-over-year for Golden Week. Rather than betting on one OS winner, Fliggy is hedging across every major device platform — embedding travel services at the infrastructure level where the booking decision actually happens, instead of waiting for guests to search an app or a browser.

This is the same structural shift Mirai’s Pablo Delgado has been describing for the US and European market: hotel distribution splitting into a traditional web ecosystem and a parallel AI-agent ecosystem that needs structured, machine-readable knowledge instead of conventional SEO. Delgado estimates only about 30% of the questions travelers actually ask can be answered from a hotel’s own website today — the other 70% is operational knowledge nobody has published anywhere a machine can read it.

Put the China numbers next to Delgado’s framework and the takeaway sharpens: properties that wait for a single dominant AI booking channel to standardize around are optimizing for a channel structure that may never consolidate. The winning move is machine-readable presence everywhere at once — clean schema, MCP-compatible feeds, and APIs — not a bet on which app or OS wins.