almasumdev
- 40 skills
- 0 followers
- 16 hours ago last updated
- ▌ Conflict Resolution · almasumdevPragmatic conflict resolution for mobile sync - last-write-wins, field-level merge, three-way merge, vector clocks, and CRDT basics. Use when two clients can modify the same record offline.
- ▌ App Store Submission · almasumdevApple App Store submission - review guidelines, metadata, privacy nutrition labels, encryption compliance, and common rejection patterns. Use when preparing a first or recurring submission.
- ▌ Play Store Submission · almasumdevGoogle Play Store submission - Data Safety form, target API policy, App Bundles, signing by Google Play, testing tracks, and staged rollout. Use when preparing a first or recurring submission.
- ▌ Offline First Strategy · almasumdevDesigning a mobile app as offline-first - caching tiers, authoritative sources, read and write paths, and the boundaries between device and server. Use when a feature needs to work without connectivity or when diagnosing stale/inconsistent data.
- ▌ Mobile UI Patterns · almasumdevCanonical mobile UI patterns (list, detail, tab, sheet, master-detail, search, form) with platform-aware guidance across SwiftUI, Compose, Flutter, and React Native. Use when designing or reviewing screens.
- ▌ Mobile Testing Strategy · almasumdevMobile testing strategy - pyramid, device selection, flake reduction, device clouds, and test-category scope. Use when setting up or auditing the testing approach of a mobile project.
- ▌ Mobile CI CD Overview · almasumdevMobile CI/CD fundamentals - branching, build matrices, signing, artifact caching, store uploads, and common pipeline shapes across Xcode Cloud, GitHub Actions, Bitrise, and Codemagic. Use when designing or rebuilding a mobile pipeline.
- ▌ Mobile Project Planning · almasumdevExpert guidance on scoping a mobile application, cutting an MVP, prioritizing platforms, and sequencing milestones. Use this when a project is starting or a major feature set is being defined.
- ▌ Crash Reporting Strategy · almasumdevCrash reporting for mobile - symbolication, SLOs, tagging, triage workflow, and comparing Crashlytics, Sentry, Bugsnag, Firebase, and native (APM) reporters. Use when setting up or improving crash reporting.
- ▌ Mitm Prevention · almasumdevPreventing man-in-the-middle attacks on mobile — user CA posture on newer Android and iOS, cleartext traffic policies, and platform configuration. Use when configuring the app's network security baseline.
- ▌ Mobile Owasp Masvs · almasumdevAligning a mobile app against the OWASP Mobile Application Security Verification Standard (MASVS v2). Use as a review rubric and as the source of truth for which controls apply.
- ▌ Dependency Scanning · almasumdevScanning mobile app dependencies for known vulnerabilities — Gradle Versions, Snyk, Dependabot, CocoaPods Audit, and npm audit. Use to keep the dependency surface patched.
- ▌ Privacy By Design · almasumdevPrivacy-by-design principles on mobile — data minimization, purpose binding, consent. Use when introducing new data collection or third-party SDKs.
- ▌ Keystore Keychain · almasumdevUsing the Android Keystore (StrongBox / TEE) and iOS Keychain / Secure Enclave for hardware-backed keys, including biometric-gated keys. Use when generating or using long-lived cryptographic keys on device.
- ▌ Consent Management · almasumdevPlatform consent frameworks on mobile — iOS App Tracking Transparency (ATT) and Android User Messaging Platform (UMP) for GDPR / CCPA. Use when integrating analytics, ads, or any cross-app tracking.
- ▌ Build Time Secrets · almasumdevKeeping build-time secrets out of the repository — gitleaks, .gitignore discipline, and scoped CI credentials. Use when wiring up signing, store deploys, or CI secrets.
- ▌ Secrets Management · almasumdevHandling secrets for mobile clients — why the client should not hold secrets, how to use a config server, and how App Check / Play Integrity replace API keys. Use when adding third-party SDKs or new server endpoints.
- ▌ Encrypted Databases · almasumdevEncrypting local databases on mobile with SQLCipher, Room + EncryptedFile, or Realm encryption. Use when persisting structured sensitive data on device.
- ▌ API Abuse Protection · almasumdevDevice attestation and anti-abuse on mobile APIs using App Attest, DeviceCheck, and Google Play Integrity. Use to make "is this a real app on a real device" decisions server-side.
- ▌ Root Jailbreak Detection · almasumdevDetecting rooted Android and jailbroken iOS devices as a risk signal — not a silver bullet. Use when deciding which operations to allow on a compromised device.
- ▌ App Lifecycle · almasumdevMobile app lifecycle across iOS and Android (foreground, background, suspended, killed), state restoration, process death, and cross-platform parallels in Flutter and React Native. Use when handling background work, persistence of in-flight state, or resume flows.
- ▌ Sync Strategies · almasumdevMobile sync strategies - pull, push, delta, bidirectional, event log, and CRDT - with tradeoffs, payload shapes, and cross-platform snippets. Use when designing how a mobile client stays consistent with a server.
- ▌ Staged Rollouts · almasumdevStaged rollouts for mobile - percentage schedules, halt criteria, feature flags, and coordinating App Store Phased Release with Play Store staged rollout. Use when planning any production release.
- ▌ Mobile QA Process · almasumdevRelease checklists, regression suites, exploratory bug bashes, and how to run QA for a mobile app without burning the team out. Use when preparing a release or standing up a QA practice.
- ▌ OAUTH Mobile · almasumdevOAuth 2.1 + PKCE for native mobile apps. Covers redirect URIs, AppAuth libraries, and the flows that are safe vs deprecated. Use when implementing or reviewing user login.
- ▌ Mfa On Mobile · almasumdevMulti-factor authentication on mobile — TOTP, push-based MFA, and recovery UX. Use when adding or reviewing a second factor.
- ▌ Token Storage · almasumdevHandling access and refresh tokens on mobile — storage, rotation, revocation, and expiration. Use when wiring up the authenticated HTTP layer.
- ▌ Biometric Auth · almasumdevBiometric authentication on mobile using BiometricPrompt and LAContext, with keys cryptographically gated by user biometry. Use when adding unlock, re-auth, or step-up auth flows.
- ▌ Anti Tampering · almasumdevAnti-tampering on mobile — signature checks, runtime application self-protection (RASP), and realistic return on investment. Use to decide which integrity controls are worth shipping.
- ▌ Tls Pinning · almasumdevTLS certificate pinning on mobile — pin sets, backup pins, kill switch, and library-specific wiring for OkHttp, URLSession, Dio, and TrustKit. Use when hardening the network layer.
- ▌ Code Obfuscation · almasumdevCode obfuscation on mobile — R8 / ProGuard on Android, SwiftShield and its limitations on iOS, and realistic expectations. Use when hardening release builds.
- ▌ Gdpr Mobile · almasumdevGDPR on mobile — lawful basis per processing purpose, Data Subject Access Requests (DSAR), and deletion workflows. Use when shipping in the EEA / UK or any GDPR-aligned jurisdiction.
- ▌ Secure Storage · almasumdevCross-platform secure storage on mobile. Covers Android EncryptedSharedPreferences / Tink, iOS Keychain, flutter_secure_storage, and react-native-keychain. Use when persisting tokens, credentials, or PII on device.
- ▌ Deep Links Universal Links · almasumdevImplementing and testing deep links on mobile - Android App Links, iOS Universal Links, custom URL schemes, attribution providers, and sunset guidance for Firebase Dynamic Links. Use when adding, debugging, or migrating deep link behavior.
- ▌ Mobile Tech Stack Selection · almasumdevDecision framework for choosing between native iOS/Android, Flutter, React Native, and Kotlin Multiplatform for a new or migrating mobile project. Use when the stack is undecided or being revisited.
- ▌ Push Notifications Overview · almasumdevEnd-to-end push notifications on mobile - FCM and APNs architecture, payload shapes, notification vs data messages, permissions, and cross-platform handling in Flutter and React Native. Use when adding, debugging, or rearchitecting push.
- ▌ Mobile Architecture Decisions · almasumdevHow to write and maintain Architecture Decision Records (ADRs) for mobile teams, and the canonical set of decisions every mobile project must record. Use when starting a project or when an architectural change is being proposed.
- ▌ Mobile Navigation Patterns · almasumdevNavigation patterns for mobile apps (stack, tab, modal, drawer, nested flows) with platform conventions across SwiftUI, Compose, Flutter, and React Native. Use when structuring navigation or handling deep links.
- ▌ Mobile Observability Overview · almasumdevMobile observability - metrics, traces, logs, and events within the constraints of battery, network, and storage. Use when defining what to collect, how to sample, and how to pipe signals to analytics and APM tools.
- ▌ Mobile State Management Patterns · almasumdevComparison of mobile state management patterns (MVVM, MVI, TEA, Redux, BLoC, Observable, Compose state, SwiftUI state) and how to choose. Use when designing state flow or evaluating a state library.