In Progress
  • iOS

Esports Super App

My role: iOS app and NestJS backend

Esports Super App brings matches, team and player stats, a social feed and fan clubs into one iOS app. It is built at Fame Yazılım under its games and esports brand, Findie Studios. The work covers the SwiftUI client and the NestJS REST API behind it.

  • Swift
  • SwiftUI
  • NestJS
  • TypeScript
  • PostgreSQL
  • TypeORM
  • Redis
  • BullMQ

Highlights

  • iOS app505 Swift files, 19 feature folders, dark theme, Turkish + English
  • BackendNestJS 11 · 26 domain modules · 60 controllers · 80 spec files
  • DataPostgreSQL via TypeORM, Redis + BullMQ queues, scheduled external syncs
  • StatusIn development · iOS 26.5 target · not in the App Store yet

iOS Architecture

SwiftUI with MVVM and @Observable, no Swift packages. Data moves one way through five layers: backend DTO, repository, screen model, view model, view. Only repositories read DTOs, screen models are typed (status, game, date, money) and never store display strings, and text and colour are computed when a view draws, so they follow the app language and theme.

Each repository is a protocol with a mock and an API implementation that return the same screen models. Moving a screen from mock to live data changes one file, the composition root in AppEnvironment. Navigation uses one NavigationStack per tab and a single AppDestination enum. The layer rules are written down in an architecture document and a CLAUDE.md file.

Backend and Data Sync

NestJS 11 modular monolith with 26 domain modules under src/app: auth, social, follows, achievements, notifications, matches, teams, players, tournaments and more. TypeORM entities on PostgreSQL, Swagger docs, a Terminus health endpoint, and a Throttler rate limit.

Scheduled jobs (@nestjs/schedule) pull data from PandaScore, LoL Esports, Leaguepedia, FACEIT, Steam, Data Dragon and Esports Earnings into the catalog. Email sending runs on a BullMQ queue so a slow SMTP server never blocks a request.

Authentication

Email with a one-time code, Sign in with Apple and Google sign-in. The API is bearer-token only: short-lived JWT access tokens plus rotating refresh tokens. If a used refresh token comes back, the backend revokes the whole session family. Passwords are hashed with argon2.

On iOS, the session lives in the Keychain, and APIClient sends a single refresh when several requests get a 401 at the same time.

Skills Demonstrated

Skill AreaEvidence in Project
SwiftUI / MVVMFive-layer architecture, @Observable view models, typed screen models
NestJS26 domain modules, Swagger, Terminus health, Throttler, scheduled jobs
PostgreSQL / TypeORM73 entity files and a migration history for the esports data model
Queues and sync jobsBullMQ mail queue, cron syncs from PandaScore, FACEIT, Steam and more
Auth and securityJWT with refresh rotation, argon2, Apple/Google sign-in, Keychain storage

Want to discuss this project or work together?

Get in touch

© 2026 Abdullah Doğanay