r/androiddev • • Mar 19 '22

Flutter replacing native development

Hi to everyone! Are you guys thinking that flutter will replace native development? I have a friend of mine who claims that, but i think it otherwise, you have so much power and control with native development. What are your opinions?

0 Upvotes

38 comments sorted by

29

u/TheDarkCanuck2017 Mar 19 '22

Not unless Google replaces the current Android SDK with Flutter. Zero chance if you ask me, and in that case Flutter would become the native solution anyway.

36

u/Cykon Mar 20 '22

I think it's more likely that we'll see Kotlin / Compose go completely cross platform, before we see Flutter overtake native Android dev.

5

u/SpiderHack Mar 20 '22

Agreed, but I still don't think that'll be as common as just using kotlin business specific core libraries for networking and some core business logic on mobile, and maybe desktop, etc...

I've been researching this on my own past few weeks and it looks like ios UI will be the biggest hurdle, but we'll see

19

u/[deleted] Mar 20 '22

Many cross platform frameworks have come and gone. I was told the same of react native. Flutter might gain popularity but native development will never go away unless google forcibly replaces it

29

u/the-dark_physicist Mar 19 '22

Nope. This is mostly used by startups who wants to spend less money and less devs. But flutter is not native at all, you can develop some business apps and thats all. If you are going to develop a big app forget it, it is slow and complex to maintain. Native is for best developmeng experience and productivity, frameworks come and go.

9

u/Zhuinden Mar 20 '22

frameworks come and go

Still wondering about whether Compose will be deprecated in 3 years

7

u/droi86 Mar 20 '22

You know it will

2

u/[deleted] Mar 20 '22

It's much more easy to maintain a Flutter app with real testing than native which is a pain to test (dagger exists for that)

3

u/the-dark_physicist Mar 20 '22

For me it is more easier to work in C++ rathen than high level languages, I miss pointers.

2

u/[deleted] Mar 20 '22

I rarely find people loving pointers :)

1

u/the-dark_physicist Mar 20 '22

What's wrong with pointers?

2

u/[deleted] Mar 20 '22

Nothing, just people are afraid when I tell a particular language has pointers. Most of the people think pointers are complex though I find them sort of intermediate. I am only afraid with malloc :)

1

u/the-dark_physicist Mar 20 '22

True. But mos of the people are learning high level languages and frameworks and they think they can learn for one month. That's why they are scared, to learn pointers you need to learn computers.

-7

u/[deleted] Mar 20 '22

frameworks come and go

Sure but Flutter could last long enough for Fuscia to replace Android, in which case native Android development is really on its way out.

15

u/Inevitable2ndOpinion Mar 20 '22

Fuscia isn't an Android replacement.

1

u/penuserectus69 Mar 20 '22

Came here to say this

-2

u/[deleted] Mar 20 '22

I don't think it's realistic to believe that Google has an appetite to support two full featured mobile operating systems.

There's general agreement now that Fuchsia is intended to replace Android. I'm curious why you think it's not?

4

u/Inevitable2ndOpinion Mar 20 '22

Why not? They already maintain flutter and Android.

It is rumored that fuscia will replace Android, yes, but right now it is nowhere close. You can take a look yourself.

Since fuchsia was announced, it's been nearly 4 years of click bait. With all the support around kotlin from JetBrains and others as well as incredible tooling and hundreds of thousands of developers comfortable with the status quo, even if fuscia was the replacement it won't be soon.

Also, this probably doesn't hold much weight but I have been told by my "sources" that fuscia is still focused primarily on iot devices.

0

u/[deleted] Mar 20 '22 edited Mar 20 '22

I think we mainly agree on the details, although possibly not on the big picture.

It will definitely be on the order of years before Fuchsia replaces Android on flagship phones. That's consistent with the timeline that both Google and Samsung are rumored to be thinking about with respect to replacing Android with Fuchsia on their devices. Even if Fuchsia were ready now, it would probably take at least 2 years to move a flagship phone so you and I agree that the replacement isn't imminent.

But my comment above was just that Flutter could outlive Android. If Flutter is supposed to outlive Android, then Flutter is the bridge between Android and Fuchsia and will be Google's focus. This means that Android native tools will start to see less investment, even though Fuchsia may not be ready to take its place.

From what I can tell they are still focusing on iot devices. But I haven't seen a Fuchsia UI demo that showed anything looking like a modern OS. So what that should tell us is that Google has fleets of production Fuchsia devices running the OS core doing security-sensitive network IO etc. And that is a sign that the OS is doing very well and they're serious about it. The part it's missing is the UI. The UI is pretty obviously going to be something web-browser focused, likely driven by Flutter. So again this is another reason to suspect they're serious about Flutter.

You're right that they don't want to burn developer good will, especially since they don't want to push Android users to Apple.

[A few edits for clarity and typos]

[Edit 2:]

Here's the short way to say what I've been stumbling around to say:

Google is doing a pincer movement on the OS core (think Linux + GNU utils) and the GUI (think x11). Fuchsia core on IOT devices, Flutter on Android devices. These are real production devices that they're getting monitoring information from that they're using to improve the OS. At some point, the two sides will meet in the middle to from a much stronger OS than you'd think if you were only watching one of the sides of the pincer movement.

I can't think of a another OS that had the luxury of evolving the OS and GUI independently like this, and it's a bit interesting to think about.

3

u/the-dark_physicist Mar 20 '22

I would love if google invests more in ndk, to write an android app completely in C/C++ without the JNI.Some people like love to reinvent the wheel. I write desktop apps completely using win32 api, in the begining was a pain but now I'm comfortable with it and for s framework it is very difficult to use. Fortunately microsoft deprecates methods every 20 years.

1

u/Beautiful-Chain7615 Mar 20 '22 edited Jan 17 '26

fact busy different judicious cheerful existence afterthought attraction butter dime

This post was mass deleted and anonymized with Redact

1

u/[deleted] Mar 20 '22

Google is targeting 5 years and investing accordingly. Samsung is assisting, but I'm not sure what their timeline is. My guess is also around 5 years.

I think it's possible Flutter could last another 5 years, per my original comment.

0

u/the-dark_physicist Mar 20 '22

I don't know about it

6

u/[deleted] Mar 20 '22

No Chance.

2

u/plusturk Mar 20 '22

As many says here, unless Google forces it, native is not going anywhere. However, if things keep going this way, in the not so distant future, most of the new simple applications will prefer Flutter over Native.

2

u/kbcool Mar 20 '22

Google would have to work out a way to kill React Native first since it's far more popular than Flutter.

2

u/Inevitable2ndOpinion Mar 20 '22

With compose multiplatform (when it is released) flutter won't be around too long.

4

u/Zhuinden Mar 20 '22

If KMP keeps up its build complexity, tooling complexity and lack of dedicated repository for KMP library projects, Flutter might emerge victorious after all for already having resolved this set of issues.

5

u/Inevitable2ndOpinion Mar 20 '22

This is a fair statement, although, in my experience, the tools keep improving and the build complexity has already been simplified.

Flutter has failed so far to capture broad appeal for obvious reasons and I think with continued support for alternatives that are technically more "native" and the kotlin vs dart is an easy fight for kotlin to win.

1

u/Usual-Application-52 May 19 '23

Kotlin / Compose

Literally none of the "reasons" are obvious, or this thread would not exist.

3

u/old-new-programmer Mar 20 '22

Agree, KMP is very confusing to get going.

1

u/adambahm Mar 20 '22

No. Never.

1

u/Cool_Bite_5553 Jun 05 '23

We've just started using Flutter (wholesalers) and the results are far better than the previous apps we've built. Flutter apps are more responsive and faster in my experience.

1

u/RyanTheLionHearMeRor Mar 22 '22

Yes I switched to Flutter and it's so much better to work with than native Android development. Oh it's also cross platform

My real concern here is that html 5 will replace nayive app development. If you look at Amazon's app, it's just a web app and it works great. Scary stuff....

-1

u/Zhuinden Mar 20 '22 edited Mar 20 '22

If Compose keeps up the trend that it barely supports anything except the immediate need for Google material design products, then Flutter might truly become a valid contender - especially with how they're more refined for multi-platform than Compose or KMP (which are still only alpha, not even beta) when it comes to multi-platform support.

But even if Flutter becomes strong, it won't completely replace all existing native Android dev projects.