design and build a high-quality iOS application based on an existing product concept and web platform that I am currently developing. The objective is to translate the core functionality of the platform into a clean, premium, and highly reliable native iOS application. The application should feel modern, elegant, and intuitive while maintaining strong performance, scalable architecture, and production-level code quality. The product is centered around a platform that allows teachers or instructors to manage and conduct classes with their students. The platform combines scheduling, class management, communication, and payment tracking into a single streamlined interface. The iOS application should replicate and enhance these capabilities for mobile users while ensuring that the experience is smooth, responsive, and easy to navigate. The app will have two primary user roles: teachers (or instructors) and students (or parents). Each role will have its own interface, permissions, and workflow. Teachers will primarily manage scheduling, classes, and payments, while students or parents will be able to view schedules, attend classes, and make payments. The engineer should design the architecture so these two roles are clearly separated while still maintaining a unified system. One of the most important features is class scheduling and calendar integration. Teachers should be able to create classes or sessions directly from the app by entering details such as the student name, class type, date, time, and fee per session. Once scheduled, these classes should automatically sync with the teacher’s preferred calendar, such as Google Calendar or Apple Calendar. Students should receive the corresponding class event as an invite so that the session appears in their own calendar as well. Each class should be recorded in a structured log so that both the teacher and the student can track past classes, upcoming classes, and remaining sessions. The system should allow teachers to set conditions such as price per class, the number of scheduled sessions, and a base fee requirement. For example, a teacher may define a minimum payment threshold even if fewer sessions are taken. This structure should be reflected clearly within the mobile interface. Another key component is payment tracking and invoicing. Teachers should be able to generate invoices or payment requests directly from the application. Students or parents should be able to view these invoices and make payments through integrated payment systems. The system should support modern payment integrations such as Razorpay or similar providers. The mobile experience for payments should be simple, secure, and optimized for quick completion. In addition to payments, the platform should support automated notifications and reminders. For example, students should receive reminders for upcoming classes, payment due alerts, and confirmations when payments are successfully processed. Notifications may be delivered through push notifications, email, or messaging integrations. The architecture should be flexible enough to support these communication channels. Authentication and account management are also critical components. Users should be able to create accounts using email authentication and optionally social logins such as Google or Apple. The login process should be secure and straightforward while maintaining good onboarding flow for new users. The system should also support role-based onboarding so that teachers and students enter the platform through the correct interface. The user interface and user experience should feel premium and minimal. I want the design to be clean, modern, and highly intuitive. Navigation should be simple and clear so that users can quickly access key features such as scheduling, class history, invoices, and payments. The visual style should avoid clutter and instead prioritize readability and smooth interactions. Performance and reliability are extremely important. The application should load quickly, handle real-time updates properly, and remain stable during frequent use. The engineer should ensure efficient data synchronization between the mobile application and the backend services so that schedules, payments, and class records remain accurate across devices. The technical stack should use modern iOS development standards. Ideally the application should be built using Swift and SwiftUI, although UIKit can be used if necessary for certain components. The codebase should be modular, maintainable, and scalable so that additional features can be added in future updates without requiring major rewrites. The application will need to integrate with existing backend services and APIs that power the platform. The engineer should be comfortable working with REST APIs and authentication tokens, handling network requests, and managing data synchronization. Proper error handling and fallback states should be implemented to maintain a stable user experience even if network conditions are unstable. Security and data protection should also be considered during development. Sensitive information such as authentication tokens, payment data, and personal information must be handled securely using best practices for iOS applications. The final deliverable should be a fully functional iOS application that can be tested internally and eventually prepared for App Store deployment. The engineer should follow clean coding practices, maintain proper documentation, and ensure the application meets Apple’s design and development guidelines. Ideally I am looking for an engineer who not only writes strong code but can also think about product quality and user experience. The goal is to create an app that feels polished, premium, and reliable from the first release. Experience with building production-grade iOS applications, integrating payment systems, handling calendar APIs, and implementing modern UI frameworks will be highly valuable for this project. This project will start with the core features mentioned above, but the architecture should allow the platform to expand with additional functionality over time. Future possibilities may include live class interfaces, resource sharing, analytics dashboards, and other advanced features. The main objective at this stage is to build a strong, well-structured iOS foundation that delivers a smooth experience for both teachers and students while supporting scheduling, payments, and communication in a single streamlined mobile application.