iOS Developer for Puzzle App Automation

Замовник: AI | Опубліковано: 12.01.2026
Бюджет: 250 $

Project Overview I am looking for an experienced developer to build a UI automation solution for existing iOS and macOS applications. I do not have access to the source code of these applications, so the automation must work entirely through the user interface, simulating real user interactions. The primary goal is to create a stable, maintainable, and intelligent automation system that can detect UI elements, respond to different screen states, and recover from interruptions during long-running execution. ⸻ Technical Requirements • No source code access: The solution must operate externally via UI interaction only. • Preferred approach: A computer-vision–based solution (e.g., OpenCV) for detecting buttons, dialogs, pop-ups, and UI regions based on visuals. • Alternative approach: If feasible, a working Xcode/XCUITest-based automation that does not require app source code is acceptable. • macOS support: • The solution must be runnable on macOS. • The macOS implementation should support automation across multiple applications using a shared framework or configuration. • iOS support: • Automation should work with iPhone devices using standard iOS automation/testing practices. • Intelligent behavior: • Detect different UI states • Handle dynamic screens and pop-ups • Make decisions based on what is visible on screen • Recover gracefully from errors or unexpected flows ⸻ Stability & Maintainability The automation should be designed for: • Long-running execution • Robust error handling and recovery • Clear logging and reporting • Easy updates when UI layouts change • Clean project structure and documentation ⸻ Tools & Frameworks The choice of tools is flexible and open to recommendation. Possible approaches may include: • OpenCV or similar computer-vision techniques • XCUITest • Appium / WebDriverAgentRunner • Hybrid approaches combining UI automation and visual detection The final decision should prioritize reliability, maintainability, and platform compatibility What We Need • A developer experienced in iOS and macOS UI automation • Ability to build automation without access to application source code • Experience with computer-vision–based UI detection (e.g., OpenCV) • Strong understanding of iOS/macOS automation constraints and limitations • Ability to design automation that is stable, maintainable, and long-running • Clear communication and willingness to explain setup, usage, and limitations • Familiarity with tools such as OpenCV, XCUITest, Appium, or hybrid approaches ⸻ Deliverables • A working UI automation solution that runs on macOS and supports: • iOS automation via connected iPhone • Automation across multiple applications on macOS • Automation that: • Detects UI elements visually or via supported automation frameworks • Handles pop-ups, dialogs, and dynamic screens • Recovers from unexpected states or interruptions • Well-structured and maintainable automation project • Clear documentation explaining: • How to set up the environment (Mac, devices, dependencies) • How to run the automation • How to adjust or extend it for additional apps or UI changes • Basic logging and reporting to track execution ⸻ Working Relationship We value a transparent, professional, and collaborative relationship. This project has clearly defined goals, structured milestones, and a focus on long-term maintainability. We are responsive, organized, and respectful of a developer’s expertise and time. ⸻ Why Work With Us • Well-scoped technical challenge • Clear expectations and decision-making • Emphasis on quality, stability, and professionalism • Open communication and prompt feedback Screening Questions 1. What experience do you have with iOS (iPhone) UI automation or mobile test automation projects? 2. Which iOS automation tools or frameworks have you used (e.g., Appium, XCUITest), and in what context? 3. How do you design automation to remain stable when UI elements or screens change? 4. Have you worked on long-running or endurance automation tests before? If so, how did you ensure reliability?