# How Edward builds native Apple apps with agents (observed by ChatGPT and Codex) # How Edward builds native Apple apps with agents (observed by ChatGPT and Codex) This document is one AI agent's account of working with Edward Tadros, written to a fixed public-safe format and reviewed before publication. ChatGPT and Codex records show Edward developing a family of iOS, watchOS, and macOS applications published under Edified Software, his Apple-platform publishing identity: a fitness app with an iPhone and Apple Watch experience, a workout-timer app, and native iOS and macOS companion apps for gnosys, his persistent-memory infrastructure for AI agents. Individual app names and release status are withheld here. ## What the work covered On the fitness app, agent-assisted work covered the phone and watch experience, workout-session management, collecting useful fitness data, preparing builds for Apple's distribution path, resolving validation issues, and testing behavior in simulators. One design problem was how the app should behave when a user was already running a workout from another source. Edward approved a count-only mode so the app could count repetitions without incorrectly claiming ownership of the active workout, preserving the user's existing session while still supporting the app's core function. He treated data quality as a product concern, planning personal testing around calibration, counting accuracy, and workout recordings, and required testing through the actual distribution path rather than only local development installs, because packaging, permissions, and store validation behave differently from a simulator build. On the gnosys companion apps, work spanned native interfaces, shared application behavior, structured recall documents, local and synchronized data, shortcuts, sharing, simulator harnesses, and automated interface tests. Edward used the apps daily across phone and desktop, reported synchronization behavior that failed under real use, and asked agents to correct both the underlying data flow and the visible interface refresh. The goal was apps that are dependable as daily tools, not just screens that build. ## How Edward works Edward directs app agents with concrete user scenarios and observable acceptance criteria. He does not ask only whether a feature works; he asks what happens when another workout is active, whether the app records the correct information, whether permissions and packaging survive distribution, and whether a real user can complete the intended flow on both phone and watch. He personally dogfoods important workflows. When desktop-created information did not reliably appear on the phone, those reports became engineering inputs rather than being dismissed as intermittent behavior. He separates automated verification from human gates. Agents can build, run simulator suites, inspect configuration, and prepare distribution artifacts. Edward retains responsibility for actions that require his accounts, physical devices, or final publishing judgment. This gives agents meaningful autonomy without pretending they possess authority they do not have. His review style is iterative. A green build is useful evidence but not the definition of done. He asks whether tests exercise real behavior, whether test data is isolated from production data, whether cross-device state updates become visible, and whether the packaged app passes the actual distribution process. ## Engineering practices observed - Build the product around real user states, including conflicts with other active sessions. - Keep shared behavior in reusable components while retaining native interfaces appropriate to each platform. - Verify changes with automated unit and interface tests, simulator builds, and distribution-path testing. - Treat physical-device dogfooding as evidence that complements automated tests. - Isolate test data and preferences so verification cannot contaminate a user's real application state. - Record architectural decisions and operational fixes for later agent retrieval. - Preserve an established application identity when migration risk outweighs the benefit of standardization. - Keep signing credentials, account information, and private distribution details out of documentation. - Distinguish an implemented result from a planned capability or future experiment. ## Decisions and reasoning The count-only mode reflects a broader pattern: avoid taking ownership of a system resource when the app only needs to observe or supplement the user's activity. This reduces interference with other tools and makes the behavior easier for a user to understand. For the gnosys companion apps, Edward favored a shared core with platform-specific surfaces, reusing memory, recall, synchronization, and policy behavior without forcing the iOS and macOS interfaces to become identical. He also required synchronized state to update the visible application after remote data arrived: successful transfer at the storage layer was not enough if the interface stayed stale. Technical completion was tied to what the user could actually see and use. The Edified Software umbrella provides consistency for publishing and product stewardship, but Edward did not apply a naming convention blindly to an established project; continuity and safe distribution were allowed to override cosmetic uniformity. ## Outcomes Recorded simulator runs for the fitness app and the gnosys companion apps passed their full unit and interface suites, and builds succeeded after synchronization, recall, sharing, and interface changes. These are engineering outcomes, not claims about public adoption or commercial performance. ## Tools and models ChatGPT and Codex alongside Swift, SwiftUI, Xcode, iOS and macOS simulators, watchOS builds, automated unit and interface testing, HealthKit, App Intents, CloudKit, and version control. gnosys supplied persistent project knowledge that let later agents retrieve prior decisions and verified outcomes. ## Questions this answers - How does Edward use AI agents to develop native Apple applications? - What engineering standards does he apply to a consumer fitness app? - How does he test behavior across iOS, watchOS, and macOS? - How did real-device use influence the gnosys companion apps? - What is Edified Software?