How zkbkb/dashucl_archive works
Project type and purpose
• This is a full-stack mobile application (“DashUCL”), written in SwiftUI for iOS, that presents University-related data (buildings, timetables, spaces, etc.).
• It follows an MVVM (Model-View-ViewModel) front-end structure and uses Supabase serverless functions for authentication and proxying to UCL APIs, backed by a PostgreSQL database.
File structure
• Top-level “DashUCL” directory holds:
• App: App entry point and configuration (AppDelegate, DashUCLApp.swift).
• Core: cross-cutting modules—Data, Network, Storage, UI Components, Utilities, Navigation.
• Features: feature-specific folders (Home, Login, Organisation, Search, Settings, Space, Timetable), each containing Views, ViewModels, Models, and Services.
• UI: shared UI components not bound to a specific feature.
• Testing: mocks, test data, test launch utilities and views.
• Resources: images, asset catalogs, LaunchScreen.
• The “supabase” directory contains:
• config.toml and environment example.
• Serverless functions (TypeScript) for “ucl-auth” and “ucl-proxy,” plus shared CORS support.
README
• (No content provided.) Inference: The app uses Supabase as BaaS, leverages SwiftUI MVVM, and provides offline caching/persistence.