How to use Codex to build flight-time widgets
Codex turned Figma travel designs into offline Fly Mode and time-zone widgets, with human privacy choices, regression review and TestFlight release preparation.
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Implement offline flight itinerary state from this approved SwiftUI design. Keep departure, layover and arrival dates consistent across time zones and WidgetKit views, including date changes and saved contacts. Add unit and UI regressions, preserve on-device storage, and pause for human design and release acceptance.
Reach people exploring AI agents
See placements →What happened
The creator reports working offline Fly Mode and widgets, release tests and a TestFlight/App Store review path; no completed trip or store approval is inferred.
Reported by Jaishg29 Garg — DevpostHow the agent did it
- Garg supplied Figma designs and explicit travel, privacy and interaction requirements.
- Codex implemented Fly Mode itinerary state, time-zone logic and interactive travel widgets.
- The owner reviewed regressions and release tests before TestFlight and App Store review preparation.
Where a person stepped in
Garg retained product, design, privacy and final implementation decisions, tested time zones and widgets, and judged whether changes preserved the intended experience.
Designer Jaishg29 Garg used Codex to extend a native iOS world-clock app with Fly Mode. The task was to follow departures, layovers and arrivals offline while continuing to show saved people’s local times. It was a travel-tool build, not an account of Codex booking or completing a trip.
Garg supplied product decisions and Figma designs. Codex translated them into SwiftUI, developed itinerary and journey-state logic, reasoned through time-zone edge cases and tested across iPhone sizes. Interactive WidgetKit views exposed travel state and time scrubbing without requiring the full application to be open.
The source identifies the hard part as keeping flight dates, multiple zones and saved contacts consistent across the app and widgets. Garg reviewed changes, caught regressions and retained every product, privacy and final implementation decision. Unit tests, UI tests and release preparation supported a TestFlight build and App Store review.
The app stores information on-device without requiring an account. Availability guidance is currently set by the user; shared circles, calendar synchronization and automatic boarding-pass setup are future features. The demonstrated outcome is an implemented offline itinerary and widget workflow with human design control. App Store approval, a completed personal journey and measured travel time savings are not established by the submission.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: Devpost · Jaishg29 Garg
Frequently asked questions
Did Codex book a flight?
No. It helped build an offline itinerary and time-zone application.
Does the app require an account?
The source says saved information stays on-device and no account is required.
Are boarding-pass imports already implemented?
No. Automatic trip setup from screenshots is listed as future work.
More details
About this account
Garg supplied Figma designs and explicit travel, privacy and interaction requirements. Codex implemented Fly Mode itinerary state, time-zone logic and interactive travel widgets.
Firsthand dated build account opened. Codex implements the travel tool; GPT-5.6 also supported UI and QA. No booking, completed journey, App Store approval or automatic screenshot import is claimed. Suggested prompt written by Agents In Use; no original task prompt was found in the verified text.
Credit: Jaishg29 Garg — Devpost
Source published 21 Jul 2026
Source checked 14 Oct 2026
Tools and topics
Codex · SwiftUI · WidgetKit · Figma · XCTest
flight time zones · offline itinerary · native widgets
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.