Well I'm sad than you plan a full rewrite in Swift, it means that I'll never have the chance to use it on my Android Best of luck for your app though, it seems nice
It was already fully native Swift and I began the apps before React Native existed. But it’s not true what you say! I have begun prototyping experiments in running my Swift and SQLite in the browser via WASM, and I’m also evaluating https://skip.tools for running SwiftUI on Android. I will go cross platform without ditching Swift.
But to be honest I am more likely to pursue web than native Android (Skip runs Swift natively on Android and binds SwiftUI to Compose) because Google is such a nightmare on top of Apple compared to the revenue Android apps tend to bring - I’ve seen others recently port 6 digit MRR apps to Android and make less than 1/100 as much for instance. But maybe for valuable language learning apps it wouldn’t be so bad. Anyway I am thinking to prioritize web apps first that could run on mobile too and perhaps later upgrade that into an Android app (whether with Skip for native UI or as a wrapper around web UI).
But to be honest I am more likely to pursue web than native Android (Skip runs Swift natively on Android and binds SwiftUI to Compose) because Google is such a nightmare on top of Apple compared to the revenue Android apps tend to bring - I’ve seen others recently port 6 digit MRR apps to Android and make less than 1/100 as much for instance. But maybe for valuable language learning apps it wouldn’t be so bad. Anyway I am thinking to prioritize web apps first that could run on mobile too and perhaps later upgrade that into an Android app (whether with Skip for native UI or as a wrapper around web UI).