Assume the backend already exists and design a flight booking iOS app. The flow runs search results → flight selection → seat and passenger entry → payment → confirmation. Focus on how you manage state across those screens.
Model the booking as an explicit state machine (searching→selected→held→paying→confirmed/failed) owned by one BookingSession. A hold carries a server expiry time, with a UI countdown and a re-hold on expiry. Search results can be cached; booking steps always treat the server as the truth.
iOS system designShort answerAdvanced
In an iOS chat app where the network drops often, messages the user sends must not be…
#idempotency #offline
iOS system designShort answerAdvanced
Design an infinite-scroll feed screen like Twitter's from the iOS client's point of view…
#offline
iOS system designShort answerExpert
Design the iOS client for a 1:1 chat like WhatsApp. Focus on message ordering…
#idempotency
iOS system designShort answerAdvanced
Sketch a single "save bookmark" feature as a Swift code skeleton. Instead of a…
#offline