
GigSA
iOS Engineer, end to end · GigSA · 2026
- Apps shipped
- 2
- Timeline
- 3 months
- Automated tests
- 1,000+
- Feature modules
- 24
The journey
Month 1 · Foundations
A demoable product before the backend existed
The freelancer app went from an empty repo to a full design system, domain layer, and every feature module in two days, all running on in-memory repositories so the product could be demoed and reviewed on day three. Later that month the organizer app followed the same blueprint: an on-site operations console first, then events, hiring, payroll, team, messaging, and QR check-in in phases.
Month 2 · Real data
Swapping fakes for the live API, one seam at a time
Because features depended only on domain protocols, wiring the real backend meant swapping repository implementations, not rewriting screens. Earnings and payout states, push notifications, and crash reporting landed behind vendor-neutral seams, and TestFlight builds went out every few days for real feedback.
Month 3 · Release readiness
Making it boringly reliable
A staged readiness programme: an injected clock for deterministic behaviour, a snapshot-test harness, a design-system pass, and accessibility and contrast sweeps in both Arabic and English. The freelancer app shipped to the App Store, with a guarded release pipeline that verifies every build points at the right environment.
After launch
Hardening in the field
Production observability, offline launch, in-app messaging, and geofence alerts for staff who leave the venue. Shift tracking moved from continuous background location to region monitoring: kinder to the battery and to privacy, with the same on-site guarantees.
Context
GigSA is a temporary-staffing platform for events in Saudi Arabia: exhibitions, conferences, concerts, sports, and government events. It is two products sharing one backend. GigSA is the freelancer app, where people find nearby gigs, apply, check in to shifts with a QR badge, and track their earnings. GigSA Organizer is the on-site operations console, where event teams hire, run attendance across zones, scan staff in, handle break requests, review performance, and close the day with a report and payroll.
What I did
I built both iOS apps end to end: architecture, every feature, the release pipeline, and the API contract work with the backend team. Close to 500 commits across the two repositories, about 89,000 lines of Swift, and more than a thousand automated tests.
Both apps share one foundation, designed so a second app would cost a fraction of the first:
- Clean Architecture in Swift packages. Domain, Data, Networking, Design System, and Localization as separate targets, with one target per feature: 8 in the freelancer app and 16 in the organizer app. Features never import the data layer.
- Dependency injection without singletons. Live builds resolve remote repositories; previews and tests resolve in-memory ones. That one decision is what made the two-day prototype and the later backend switch possible.
- Swift 6 with complete strict concurrency,
@Observableview models, and SwiftUI throughout, with Liquid Glass on iOS 26 and graceful fallbacks down to iOS 17. - Arabic first. Right-to-left is the default layout, English is a first-class second language, and switching between them is instant, in light and dark themes.
- Quality gates in the loop. Strict SwiftLint and SwiftFormat on every commit, Swift Testing and snapshot tests pinned to an exact simulator runtime, and Fastlane lanes for staging, TestFlight, and App Store review.
Outcome
Two production apps, both live on the App Store, built by one engineer in about three months. Together they cover the whole loop of an event workforce: from a freelancer discovering a gig to an organizer approving the payroll that pays them.