Aim: The student must architect, build, and deploy a fully functional Software-as-a-Service (SaaS) platform capable of handling real users, transactions, and concurrent traffic.
Aim: The student must architect, build, and deploy a fully functional Software-as-a-Service (SaaS) platform capable of handling real users, transactions, and concurrent traffic.
The platform cannot be a simple single-user app. It must support multiple isolated organizations or tenants (e.g., a B2B SaaS). It must implement robust Role-Based Access Control (RBAC) with hierarchical permissions (Owner, Admin, Viewer), secure session management, and OAuth2.0 integration (Google/GitHub SSO).
The system must transcend basic CRUD operations. It must feature a complex core engine (e.g., scheduling algorithms, automated document generation, data aggregation). Heavy computations or third-party API integrations must be decoupled from the main thread using background job queues (e.g., Redis/BullMQ) and Webhooks.
The database architecture must be strictly normalized (PostgreSQL/MySQL) with proper indexing. The platform must implement a caching strategy (Redis or Memcached) to minimize database hits on high-traffic endpoints. Search functionality must be optimized (e.g., using Elasticsearch or vector embeddings).
A true SaaS must be able to accept money. The platform must integrate a payment gateway (Stripe, Razorpay, or Paddle) handling complex billing scenarios such as recurring subscriptions, usage-based metering, or tier-based access control, complete with automated invoice generation and webhook event handling.
The application must not be manually deployed. Students must configure a fully automated CI/CD pipeline (GitHub Actions) that runs integration tests before containerizing the app via Docker. The production environment must include an SSL certificate, custom domain routing, and telemetry (Logs and Metrics via Prometheus/Grafana or Datadog) to monitor uptime and API latency.
Aim: The student must design, engineer, and publish a native, high-performance iOS application that strictly adheres to Apple’s Human Interface Guidelines (HIG) and leverages the unique hardware capabilities of the device.
The application cannot simply be a wrapper for a web API. It must rely heavily on native iOS frameworks to solve a problem. This includes significant utilization of at least two of the following: CoreML (On-device AI), ARKit (Spatial Computing), HealthKit, CoreBluetooth (IoT), or background location tracking, making the app uniquely "Mobile-First."
The app must remain fully functional without an internet connection. Students must implement a robust local database (SwiftData or Realm) combined with an intelligent background synchronization engine. Conflict resolution strategies must be implemented for when the device reconnects to the network to ensure data integrity with the cloud backend.
The codebase must be structurally sound and maintainable. It must be split into independent modules using Swift Package Manager (SPM). The UI layer must strictly decouple from business logic using a modern architectural pattern (MVVM, VIPER, or The Composable Architecture), with completely reactive state management (Combine or Swift Async/Await).