For anyone reading this and if you want to develop mobile apps, just first learn native iOS/Android platforms, they are not going anywhere before you get tempted by other flashy technologies like Flutter or React Native. Most companies including the ones that created these cross platform frameworks, build thier core apps using native stack for a reason.
I used to say just this. And I did native Android dev for many years, but I gave it up around 2019.
When I finally checked out, native Android was a teetering mess of compatibility libraries, half-baked never-finished “new ways of doing things”, lacking docs, forever-bugs, and overall neglect. Simple ui would take you 5x as long as equivalent css and have you dropping down to low level drawing in frustration.
Back then, I felt native Android didn’t deserve my time or patience.
Jetpack Compose, and Kotlin coroutines, mixed with kotlin multiplatform code, came and made many things nicer, especially UI. With so many libraries and so many ways of doing things with so many opinions it’s still hard to digest of course.
It’s better than non native for performance and experience but many companies will of course care more about the money saved from a sub native experience with fewer developers.
> It’s better than non native for performance and experience but many companies will of course care more about the money saved from a sub native experience with fewer developers.
I currently work at an agency doing Android apps (not a typical pump and dump agency mind you, I've been the lead on this single project for 5 years and we've had them as a client for 8+), and I'm so happy to see our client buck that.
They've had us on a native app that we've been supporting for the entire 8 years, and had deep technical issues from before us ("lets reinvent the web browser for UI"). They had a secondary internal team (known to us, no hidden surprise, you're gone stuff) working to replace us with a greenfield cross platform app (I think react native). That project went on for a year before they cut their losses and said "cross platform can't be good enough."
We're now in the planning phase of a complete greenfield rewrite of the existing app to take advantage of Compose + Kotlin, and ditch 12 years of tech debt and I'm practically ecstatic.
I'd argue the opposite. For a lot of people, getting quick results is absolutely needed for motivation. Focusing on learning "the fundamentals" before getting to the enjoyable parts is bad advice for most, as it often leads to people dropping out before they get hooked.
I agree that you probably can't be a decent mobile dev in the long term without learning basic iOS/Swift or Android/Java(/probably Kotlin nowadays) but that is not a good place to start for people who are just getting started.
>Most companies including the ones that created these cross platform frameworks, build thier core apps using native stack for a reason.
yes, because they are a company and have 2 separate teams maintaining each stack.
TBH I mostly blame Apple for my reluctance. Given the barrier of entry, I'd rather just work with a cross platform tool, launch android, and then figure out any potential IOS issues when I decide I need an IOS port and the need to pay for a license (and find/buy the Apple hardware).
