Summary: The risks that decide whether the 7Mind React Native migration goes well, and how to retire each one. Dependencies are not among them: every Flutter dependency has a React Native counterpart. Sources: code inspection of sevenmind/7mind-mobile-apps-monorepo and Gymondo-git/pulse-app (2026-11-06); 7mind-mobile-apps-monorepo, platform-unification, subscription-billing; kickoff meeting 2026-11-09 and Ali Kayhan’s spike report (Slack, 2026-11-10); pulse-app PR #264 read on 2026-11-13; pulse-app PRs #264, #287, #288 and #289 and their branches as of 2026-11-16 Last updated: 2026-11-17
1. Audio player
The player is the product: background playback, lock screen and notification controls, offline playback of downloads, playback intervals, chaining to the next item, completion tracking, Apple Health mindful minutes. React Native audio libraries differ most exactly here (Android foreground service rules since Android 14, audio focus, resuming after process death). pulse-app has no audio-first player; its react-native-video and download manager are built for workouts.
Retire by: a spike on real devices for both platforms with the candidates (react-native-video, react-native-track-player, expo-audio), including a downloaded file, lock screen, a phone call interruption and a kill/restore. Build the result as a shared package so other tenants can use it.
Status (2026-11-17): the spike recommends expo-audio in apps/sevenmind; Android emulator checks passed, iOS, downloaded files and kill/restore are still open. See rn-migration-audio-player.
Status (2026-11-16): not started. PRs #287 to #289 build every screen that leads to the player but leave the play, play-next and download taps inert, so the player now gates For you, Library, Prevention and Downloads alike.
2. Purchases and receipt sync
Revenue path. The Flutter app syncs receipts to api/v4/sevenmind/receipts/google/sync and api/v1/sevenmind/receipts/transactions and gets products from api/v3/sevenmind/products/{platform}. pulse-app’s @pulseapp/purchases uses StoreKit 2 + Play Billing via expo-iap, a derived UUID as appAccountToken / obfuscatedAccountId, and its own receipt relay with an offline queue. Existing 7Mind subscribers must keep their entitlement, and renewals must keep flowing through the same backend.
Retire by: comparing both receipt flows against subscription-billing and app-subscription-products, then a staging purchase and restore with an existing subscriber on the React Native build.
3. Keeping user data on update
The React Native app ships as an update with the same bundle ids, so on first launch it must take over what the Flutter app stored, or every user is logged out and loses downloads:
- tokens in
flutter_secure_storage(iOS keychain, accessibilityfirst_unlock; Android encrypted storage written by the Flutter plugin) shared_preferencesvalues (stored with aflutter.key prefix on both platforms)- the Drift SQLite database
drift_databasein the documents directory: downloads, playback positions, recent searches, active session marker, all in user-prefixed boxes (see the MIND-828 notes in 7mind-mobile-apps-monorepo) - downloaded audio files in the documents directory
- the
legacy_user_idbookkeeping from the identity migration
There is precedent: UpgradeDachToken (ACC-57, 2025-03) took over the token of the previous native 7Mind app when Flutter shipped. The Android side of flutter_secure_storage likely needs a small native reader.
Retire by: install the current Flutter build, log in, download, play halfway, set reminders; install the React Native build over it; everything must still be there. Do this in the spike phase, not at the end.
Progress (2026-11-13, pulse-app PR #264): a native module (apps/sevenmind/modules/flutter-secure-storage, iOS and Android) reads the Flutter keychain and encrypted storage and the shared_preferences values; on first launch the app adopts the Flutter session and the language choice. The Drift database, downloaded files and the other preferences are not taken over yet. The install-over test cannot run yet: the build is signed with the Expo debug keystore, so Android refuses to install it over a store or Play-signed Flutter install; it needs the real 7Mind signing keys first.
4. Analytics, attribution and the statistics service
Rudderstack content events are the only path by which 7Mind practice history reaches the Gymondo statistics service (mobile-analytics-stack). pulse-app has no Rudderstack; it records training activities through the API (outbox in @pulseapp/data) and fans out events to Firebase, Braze and Adjust under a typed taxonomy. Braze campaigns and CRM automations trigger on exact event names. A silent change here loses user history, breaks campaigns or attribution.
Retire by: the kickoff (2026-11-09) decided to keep analytics and attribution as they are, so the new app sends the same Rudderstack, Braze and Adjust events as the Flutter app. What is left: list the events and properties CRM, data and the statistics service rely on, and compare both builds’ events before release.
5. API surface
Decided at the kickoff (2026-11-09): backend unchanged during the migration. The new app calls the same endpoints as the Flutter app; moving 7Mind domains to Gymondo APIs is later work. Ali Kayhan’s spike already does this: Gymondo SSO (app.6mind.de) for login, social exchange and password reset, the legacy gateway (magic.6mind.de) for profile.
Most 7Mind domains are only served by function-sevenmind-legacy-gateway. Reusing @pulseapp/api pulls toward Gymondo APIs, which do not exist yet for meditation content, courses, prevention, Aury or content-piece history. That is backend work in Gymondo teams, outside the app team’s control.
Retire by: a per-domain table (Gymondo API exists / gateway only / needs new API) agreed with the backend owners before porting features.
Already known (2026-11-06 spike): app.6mind.de and app.7mind.de answer pulse-app’s login route for a 7Mind/... user agent, and the purchase endpoints pulse-app calls with a tenant (/api/v3/{tenant}/products/{platform}, /api/v1/{tenant}/receipts/transactions, /api/v4/{tenant}/receipts/google/sync) are the same ones the Flutter app calls with sevenmind.
6. ZPP and prevention
The prevention courses are certified by the ZPP and German only; a dedicated zpp build exists for the submission. A rewritten app may need a new submission or at least a check with whoever owns the certification.
Retire by: asking the prevention owner early. The zpp build itself is not carried over (rn-migration-not-migrated); a reviewer would get a test account with access instead.
7. Sharing pulse-app with the fitness apps
Direction since 2026-11-10: 7Mind is a sibling app inside pulse-app (rn-migration-goals-and-architecture). That removes the import and version problem of a separate repo, and brings others: 7Mind follows pulse-app’s Expo and React Native upgrades (PR #264 already sits on the Expo 58 upgrade, PR #253), pulse-app pins some native versions on purpose, and a 7Mind change could break Gymondo, Buddyfit or TV.
Retire by: Ali Kayhan’s ground rules (7Mind code only in apps/sevenmind and src/sevenmind, shared packages only extended, no version changes unless all apps benefit), the product-boundaries lint rule, a CI run over all apps on 7Mind PRs, and agreed review rules.
Seen in PR #264 (2026-11-13): setting up the sibling app already needed small changes to existing shared and Gymondo code (ui Typography, the api client and interceptors, config types with TenantId becoming BrandId, the Gymondo AccountScreen, the TV theme, the root AGENTS.md split into per-app files). Such foundation PRs need Gymondo review even if later 7Mind-only PRs might not.
8. Minimum OS raised
The new app needs iOS 17 and Android API 28 (kickoff 2026-11-09); the Flutter app supports iOS 15 and API 26. Users on iOS 15 and 16 (about 6%) cannot install the update and stay on the last Flutter version. Because the backend stays unchanged, that version keeps working; it just stops receiving updates.
Retire by: deciding what those users get (stay on the last Flutter build, a notice before the switch) and keeping the endpoints the last Flutter build uses alive until their share is negligible.
9. Two apps in parallel
Until parity, features land in Flutter and must be redone in React Native. Retire by: a feature freeze policy for the Flutter app with a parity checklist.