Flutter Developer – Emulator & Root/Jailbreak Detection (Android & iOS)

We need a security layer added to an existing Flutter app (PHP backend) to stop it running on anything that isn't a genuine, physical phone or tablet. What needs to happen: On launch, the app checks whether it's running on a real, unmodified device. If it detects an emulator, simulator, or a rooted/jailbroken device, it shows a brief message and shuts down completely before any content loads - nothing left running in the background. Scope of work: Android -Detect and block common emulators - BlueStacks, NoxPlayer, Android Studio emulator, Genymotion, and other virtual environments -Detect rooted devices -Integrate Google Play Integrity API as the primary verification layer -Must not interfere with Google Play's own automated pre-launch/review testing - the app still needs to pass store review normally -Log detection attempts (destination likely our PHP backend - to confirm) iOS -Detect and block Xcode Simulator -Detect jailbroken devices -Integrate Apple DeviceCheck / App Attest -Must not interfere with Apple's App Store review process -Same logging behavior as Android The app is built in Flutter, so this needs to be implemented through native platform channels (or a well-maintained Flutter security package) rather than dropped in as pure native code - platform channel experience is essential. Testing & deliverables: -Video or APK/IPA evidence: app launching normally on real hardware, and detecting + shutting down on BlueStacks, NoxPlayer, Android Studio emulator, Genymotion, Xcode Simulator, and a rooted/jailbroken device -A short technical note explaining the checks, APIs, and libraries used -All code delivered via pull request on a feature branch in our GitHub repo - no direct pushes to main Timeline: deadline is tight - please only apply if you can start immediately. Acceptance criteria: -Detection must fire reliably against all the named emulators plus common desktop VM setups, not just the standalone emulator apps -No noticeable performance hit on legitimate real devices -Code must be clean, well-commented, and store-compliant (no private API usage or anything that risks App Store/Play Store rejection) Context that may help with implementation decisions: -The app currently has no DRM — content protection relies only on expiring URLs, so this detection layer is effectively the main line of defense, not a backup -The underlying goal is stopping piracy/screen-capture, so detection needs to hold up against reasonably motivated attempts, not just casual ones