Summary: Entry point for the planned migration of the 7Mind app from Flutter to React Native, the stack of the Gymondo app (current direction: a sibling app apps/sevenmind inside pulse-app). Living namespace, updated before and during the migration.
Sources: code inspection of sevenmind/7mind-mobile-apps-monorepo and Gymondo-git/pulse-app (2026-11-06), conversation with Nikolas Haag; 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-19
React Native migration
Status (2026-11-16): four stacked PRs, about 45% of the feature surface and about 30 to 35% of the way to a releasable app (rn-migration-plan). PR #264 (the app, auth, onboarding, For you, Profile) waits for approval; #287 (detail screens, Favourites, History, SOS), #288 (Library) and #289 (Prevention and quiz) are drafts on top. Player, paywall, tracking and release work have not started. Kickoff on 2026-11-09 set minimum OS (iOS 17, Android API 28), kept backend, analytics and attribution unchanged, and agreed what to retire. After spikes of both repo layouts, the direction since 2026-11-10 is a sibling app apps/sevenmind in pulse-app (draft PR #264; its base, the Expo 58 upgrade, is merged), not the separate ripple-app repo decided on 2026-11-06; formal confirmation pending. PR #264 has auth, onboarding, a read-only For you tab and most of Profile; player, paywall, tracking, the release pipeline and most of the Flutter data takeover are not started. Details per step in rn-migration-plan. The Flutter app (7mind-mobile-apps-monorepo) is the only shipping 7Mind app.
Why
7Mind moves its app to the same stack as the Gymondo app so that more developers across 7NXT can contribute to it. The Gymondo and Buddyfit apps are being rebuilt as one white-label React Native + Expo app, pulse-app. The goal decides most of the architecture: see rn-migration-goals-and-architecture.
Pages
- rn-migration-goals-and-architecture — the goal, the current direction (sibling app in pulse-app) with Ali Kayhan’s spikes and ground rules, kickoff constraints, why the tenant model does not fit
- rn-migration-dependency-mapping — every Flutter dependency mapped to its counterpart in the new app, with keep, replace or gap per row (Sentry to Crashlytics, ConfigCat to Remote Config, …)
- rn-migration-not-migrated — what the new app does not take over: ZPP flavor, legacy migration code, Flutter workarounds, replaced vendors, Flutter-only CI, product candidates
- rn-migration-flutter-inventory — what the Flutter app consists of today: size, native code, flavors
- rn-migration-risks — the risks that decide whether the migration goes well: audio player, purchases, keeping user data on update, analytics and statistics, ZPP, API surface
- rn-migration-audio-player — audio player spike: Flutter player behaviour, pulse-app’s player, candidates, recommendation
expo-audio - rn-migration-crash-reporting — crash reporting: Sentry in the Flutter app, Crashlytics in pulse-app, recommendation Crashlytics via
@pulseapp/observability, migration period and alerts - rn-migration-plan — phases and steps with status
- rn-migration-decision-log — decisions taken and open questions, newest first
- pulse-app — repo note for the Gymondo React Native app
How to keep this namespace current
- A decision (library, architecture, scope, date) goes into rn-migration-decision-log first, then into the page it changes.
- Plan progress: update the status column in rn-migration-plan when a step starts or finishes.
- A finding from a spike or from building (a library limitation, a pulse-app convention that bites, a data migration detail) goes into the topical page, with the date and the source (ticket, PR).
- Bump Last updated on every page you touch. New pages in this folder use the
rn-migration-prefix and get a line in the list above; structural changes also get a line inlog.md. - Facts about the current Flutter app stay in 7mind-mobile-apps-monorepo; facts about pulse-app itself go to pulse-app. This namespace holds what is specific to the migration.