Skip to content
Soufiene Cherif
Al-Nassr Saudi — النصر السعودي

CASE STUDY · PERSONAL PROJECT · SPORTS · FAN APP

Al-Nassr Saudi — النصر السعودي

Flutter app for Al-Nassr FC supporters: news, social posts, videos and live streams, fixtures and standings in one place, with comments, likes and push notifications.

ROLE
Solo Developer — Mobile, Backend & Admin
PERIOD
Dec 2023 - Present
TYPE
Personal project
LOCATION
Sfax, Tunisia
SCOPEMobile appCRM & adminBack endCloud & domainStore publishingMonetisation

01 — OVERVIEW

Al-Nassr Saudi is an Android and iOS app (single Flutter codebase) for fans of Al-Nassr FC (Saudi Pro League), published on Google Play.

It is monetised with AdMob and a VIP subscription and runs on a serverless Firebase backend. In v2 I rewrote the app with Clean Architecture and Bloc, moved all sensitive logic to Cloud Functions, and built a web admin console for moderation, push campaigns, sponsored content and analytics.

02 — SCREENSHOTS

Screenshots

Swipe · Click to enlarge

03 — KEY FEATURES

01

Unified news feed: press articles, Facebook posts, national team news and videos, merged by date with independent pagination per source. Source filters, HTML article reader, zoomable image viewer, sharing.

02

Videos & live: embedded YouTube player, live tab with live chat (tab can be enabled remotely).

03

Matches & standings: fixtures, results, match details and Saudi Pro League table, synced server-side (ESPN, with TheSportsDB as fallback). Kick-off and full-time alerts.

04

Community: comments with replies, likes on posts and comments, view counter, reply and like notifications.

05

User-side moderation: hide a source, block a user, report a post or comment.

06

Push notifications: per-channel subscriptions (news, Facebook, national team, videos, matches), deep links to content, local inbox of received notifications.

07

Library: saved items available offline, reading history. Search across all feeds.

08

Feedback: private conversation with the app team (replies arrive by push) and rating.

09

VIP: in-app subscription (RevenueCat) that removes ads and shows a VIP badge. One subscription per account, “manage subscription” button, server-side expiry.

10

Ads: anchored banner, native ads in feeds and videos, frequency-capped interstitial. Sponsored posts managed from the console (impression and click tracking) and an “Advertise with us” form with a discussion thread.

11

Account: Google sign-in, privacy policy consent, account deletion (store requirement), bilingual terms and privacy pages.

12

Experience: Material 3, light and dark themes, Arabic RTL and English, adjustable text size, bars that hide on scroll, splash and adaptive icons, remote-controlled update prompt, in-app review, wallpapers (save or set an image).

04 — MY ROLE

  1. 01Sole developer, end to end: mobile app, Firebase / Cloud Functions backend, web admin console.
  2. 02Architecture and full v2 rewrite of the Flutter app (Clean Architecture, Bloc).
  3. 03Store publishing and maintenance on Google Play.
  4. 04Monetisation: AdMob ads, VIP subscription with RevenueCat, sponsored posts.

05 — IMPACT

  • 15 feature modules in the mobile app.
  • 20+ Cloud Functions (callables, triggers, scheduled jobs, webhook, admin API).
  • 12 admin console pages with 3 role levels.

06

Admin console (new in v2)

  • Web app on Firebase Hosting built with Astro (pre-rendered pages served from a CDN) + React islands + Tailwind CSS 4. No secrets and no dedicated server: all data goes through a secured back-office API in Cloud Functions.
  • Access: Google sign-in only, no self sign-up. Three roles: Moderator, Admin, Owner. Access requires both a Firebase custom claim (set only by the backend) and an active admin record, so access can be revoked instantly. Owners invite and activate admins.
  • Dashboard: users, activity, VIP subscribers, devices, languages, engagement, top content and items to handle, with a period filter. Stats are cached to reduce Firestore reads.
  • Users: search, filters (VIP, banned), sorting (created, last active, name, time in app), detail view (device, time spent), ban / unban, grant / revoke VIP, send a notification, delete the account.
  • Feedback: inbox (unread / open / resolved), replies delivered by push, canned replies, user ratings.
  • Reports & content: handle reported news and comments, delete a comment or post, ban the author, see views, likes and comments per post.
  • Push campaigns: send to everyone, VIPs, a channel’s subscribers or a single user. Filters by language and activity (active / inactive / joined since a period or date). Image, link, in-app action, preview and history.
  • Sponsoring: create and track sponsored posts, manage “Advertise with us” requests, export an ad report as PDF for the advertiser.
  • Remote app settings: ads on/off, live tab, update prompt (version, title, message).
  • Activity log: every action taken in the console is recorded.

Admin console screenshots

Swipe · Click to enlarge

07

Backend (Firebase + Cloud Functions)

  • Firebase Authentication, Cloud Firestore, Cloud Messaging, Cloud Functions (TypeScript, Node 22, europe-west1), Analytics and Hosting.
  • Callable functions: likes, comments and views (transactions and atomic increments), user blocking, account deletion, sponsored posts, ad requests.
  • Firestore triggers: comment, reply, like and feedback-reply notifications sent with the Admin SDK.
  • Scheduled jobs: match and standings sync (paused at night, Riyadh time, to save API calls), VIP subscription expiry.
  • RevenueCat webhook for subscription status.
  • Dedicated indexes (push audience, feedback inbox) so the console never scans whole collections.

08

Technical challenges

  • Rewriting without breaking production: v1 and a news crawler still use the same Firestore database. I froze the existing schema and only made additive changes, so v1 and v2 run side by side.
  • Security: v1 sent push notifications from the app with an FCM server key embedded in the APK (legacy API, since shut down by Google). In v2, all sensitive logic (push, likes, comments, blocking, account deletion) runs server-side.
  • Data reliability: client-written likes and comments (which rewrote whole lists) were replaced by server-side transactions. The view counter now uses an atomic increment.
  • Multi-source feed: a Bloc merges several collections, each with its own cursor and a watermark, to keep correct chronological order while paginating.
  • Costs: fewer Firestore reads in the console (cached stats, dedicated indexes), match sync paused at night.
  • i18n & RTL: Arabic by default (RTL) and English, with correct text direction based on content (scores, mixed-language text).

09

Timeline

  • Dec 2023: project start (v1).
  • Nov 2024: published on Google Play.
  • Jul 2025: target SDK update and fixes.
  • Nov 2026: v2, full rewrite (architecture, design, backend, admin console).

10 — TECHNICAL STACK

  • Flutter
  • Dart
  • Bloc / Cubit
  • Clean Architecture
  • Firebase
  • Cloud Functions
  • TypeScript
  • Cloud Firestore
  • Firebase Cloud Messaging
  • Firebase Auth
  • Firebase Analytics
  • Firebase Hosting
  • Node.js 22
  • get_it
  • go_router
  • Material 3
  • Astro
  • React 19
  • Tailwind CSS 4
  • Recharts
  • jsPDF
  • Google AdMob
  • RevenueCat
  • YouTube
  • ESPN API
  • TheSportsDB
  • Google Sign-In
  • bloc_test
  • mocktail
Contact meCV ↓

Try: Kotlin · Firebase · Kuwait · security · SOS