Summary: What the Flutter app carries that the new React Native app does not need: extra build flavors, legacy migration code, workarounds for Flutter itself, replaced vendors and Flutter-only tooling. Plus candidates that need a product decision, and things that look odd but must stay.
Sources: code of sevenmind/7mind-mobile-apps-monorepo (pubspec.yaml, android/app/build.gradle, codemagic.yaml, .github/workflows/, lib/), read 2026-11-06 and re-checked against origin/main at app 4.0.9 on 2026-11-09; the gateway’s internal/routes/routes.go for /upgradeauth; 7mind-mobile-apps-monorepo; platform-unification; conversation with Nikolas Haag; kickoff meeting 2026-11-09 and Ali Kayhan’s spike report (Slack, 2026-11-10)
Last updated: 2026-11-12
Status values: drop (agreed or obvious), candidate (needs the named owner to confirm). The kickoff on 2026-11-09 agreed to retire unused feature flags, the legacy DACH token upgrade and the ZPP flavor. When a candidate is decided, record it in rn-migration-decision-log and change the status here.
Build flavors and environments
The new app has two environments, test (7Mind staging, Gymondo test platform: app.6mind.de) and prod, plus pulse-app’s local which shares the test config.
Item
Where today
Status
Why
ZPP flavor (zpp, app name “7Mind [ZPP]“)
Android flavor in android/app/build.gradle, iOS AppIconZPP, Codemagic ios-workflow-zpp-submission and android-workflow-zpp-submission
drop
BuildConfig.isZPPSubmissionBuild (lib/initializations/settings/build_options.dart) is meant to unlock prevention content for the ZPP review, but nothing outside that file reads it on origin/main, so the flavor only changes the app name and icon today. If a ZPP reviewer needs unlocked prevention content, give them a test account with access instead of a build. Confirm with the prevention owner
DACH make targets (runDach, runStagingDach, main_*_dach.dart, --flavor productionDach)
removed from the Makefile in July 2026 (PR 1442)
drop
Nothing left to drop. Only the iOS production provisioning profile name 7mind-dach-flutter-distr in codemagic.yaml still says DACH
Two main files (main_staging.dart, main_production.dart)
UpgradeDachToken (takes over the token of the pre-Flutter native app, ACC-57, 2025-03)
lib/features/core/data/services/auth/upgrade_dach_token.dart, called from the splash screen
drop
All tokens were revoked at the 2026-09-14 platform cutover (platform-unification), so a native-app token found on a device can no longer be upgraded. The gateway deliberately does not implement /user_identity/upgradeauth and answers 404
LegacyUserDataMigration, legacy_user_id (UUID to numeric id adoption, MIND-828, MIND-829)
core module, run at startup and after every profile call
drop the component, keep the rule
the new app’s first-launch import of Flutter data replaces it. That import must still adopt rows under the old UUID prefix with the same caution (exact legacy id first, download boxes only on a guess), see 7mind-mobile-apps-monorepo and risk 3 in rn-migration-risks
Source re-check at 4.0.9: Google and Facebook are shown on both platforms; Apple is iOS-only. Storefront country in the auth modules supplies analytics properties, not button eligibility. Do not recreate the previously documented country gate
Workarounds that exist only because of Flutter
Item
Status
Why
MIND-817 engine sharing: AudioServiceFragmentActivity, EngineDestroyedGuard, singleTask reasoning in MainActivity.kt (three copies, one per flavor)
drop
No Flutter engine. The new audio player brings its own Android service rules, see risk 1
seven_mind/store method channel in AppDelegate.swift and MainActivity.kt (storefront country; on iOS also getIntroductoryOffers for the intro offer test)
localize-gen.yml, translations.yml (easy_localization key generation and checks)
drop
Lokalise pull and push workflows like pulse-app
Supernova Flutter token export (supernova.yml)
drop
7Mind token set in the GDS token pipeline
Widget catalog app (publish_catalog.yml, which also builds the PR previews)
candidate (mobile team)
Only useful if the new app wants a component catalog
MkDocs site on mobile.6mind.de (publish_documentation.yml)
candidate (mobile team)
pulse-app keeps docs as AGENTS.md and specs in the repo; product docs worth keeping (for example the SOS toolkit contract) can move to this wiki
FVM, Makefile
drop
pnpm scripts
Product candidates (need a product decision)
Features that are off, parked or barely used do not need to be rebuilt. The list below is what the code shows; usage numbers and flag states still need checking.
Item
Where today
Why it is a candidate
3P recommendations section on home
parked behind the Braze flag ff_3p_recommendations, which does not exist in Braze, so it is off (MIND-880, on main since app 4.0.6)
Check the share of Facebook logins before rebuilding it
Apple Health mindful minutes
behind isAppleHealthEnabled
Decided 2026-11-09: not ported; mindfulness minutes come back through Thryve after the migration
Features behind ConfigCat flags that are permanently off
isInspirationToGoEnabled, isCourseProgressionEnabled and others in feature_flags.dart (isAuryEnabled and isPreventionTabEnabled are defined but no longer read)
A feature that is off for everyone does not need migrating; check each flag’s value in ConfigCat
Looks odd, must stay
Item
Why it stays
Bundle ids de.7mind.iphone and de.7mind.ios.stg (iOS), de.sevenmind.android and de.seven_mind.android.stg (Android)
the new app ships as an update of the existing store apps; changing an id makes it a different app and loses every install and subscription
Firebase projects mind-flutter-stg and mind-flutter-5ef1a
Tied to the bundle ids and push tokens; the names are historical only