The return from a listing is discarding the trip context guests used to judge it.
Fast comparison protects guest momentum, while a shared mobile contract protects native consistency.
Who you’d be doing this for
“I picked the dates twice, then went back and it acted like I was starting over.”
Mariama Owusu · Traveler
A guest comparing several family stays after narrowing dates and party size in the mobile app.
What is at stake
Guests returning from an AI-filtered listing lose dates or guest counts instead of continuing their comparison. You must weigh a quick state fix against keeping Swift and Kotlin on one dependable contract.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- guest comparison momentum vs. fresh-search behavior
- shared GraphQL stability vs. targeted mobile repair
- iOS and Android parity vs. platform-idiomatic state handling
- release speed vs. regression coverage
Why AirBnB
AI search filters make trip context part of how travelers narrow millions of stay choices on mobile.
Written with these in mind
Not your kind of problem? 45 more at AirBnB, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.