Cross-Platform VS. Native - What's better?

Subscribe for more Android tips :)

[ryugalaw]

Both. I use both at work and I can't say one is better than the other. Although, Kotlin for me is the best Programmierung Language

[DennisEspiritu]

Native first. Then cross-platform as secondary skill.

[pradiptapriya]

Oh my god. I'm so happy to see a lot of comments prefer native, or is it because it's in your channel?
In my workplace, they absolutely prefer cross-platform than native that you can only find 1 to 3 native deloper in whole company. Now I'm slowly learning cross-platform too to survive lol.

[Camlon]

I earlier worked on a multiplatform project in Xamarin and I am confident that choosing Xamarin has hurt the company significantly and could potentially lead to the company failing.

Unless you want to develop for android, iOS and web, then I think native is better.

1. Native has better development tools, which speeds up development.
2. Native gives you more components and makes it easier to style them. Creating a special native renderer can take days and clients don't get happy if you tell them that only certain looks are acceptable.
3. Multiplatform forces app to rely on plugins and testing that is slow and unreliable.
4. Many multiplatform technologies do not provide a proper web solution. The result is that you end up with 2 code bases anyway as the clients request a web solution.
5. Many multiplatform technologies use special syntax that makes it hard to bring in new developers.

That's so true, complex apps native, simple apps cross platform, that's what I think

[patrickbateman]

Looking pretty jacked. 💪 BTW I think there are way more job opportunities for ReactNative or Hybrid Apps developers than native.

[rajushingadiya]

hello Philips sir, big fan

i was totally confused about what to choose ... flutter growing super fast and my friends was getting hike about 110% in flutter line, who ever i see, everybudy was making lot's of money 💰, for one second it's literally change my mind but i am big fan of kotlin and then compose arrived...so i decided to be in native path instead of new butterfly 🦋

TLDR
Native is Life time stable ways

look back in past ... flutter is not first cross platform tech. many comes and many goes. onces tech is gone you are outdated, my few old friends are still working in ionic, phonegape, and there are very low vacancy chances for them.

[udbhavsinha]

Once a native lover, always a native lover. Period.😌

[khemmahato]

You are best bro never give uploading clean architecture

[provokator-provocateur]

I use cross-platform for video rendering, sensors and native for simple apps

[MetehanBOLAT]

Now, definetly native but in the future KMM 😎

[elmonni]

I was a native developer for Android, Windows Phone and iOS for about six years. The last four years I have used only React Native, and will never switch back to pure native development.

[jihoha]

But solid knowledge with native still would be priority before getting into any cross-platform whatsoever

[tiagosutter]

I like native development more, but I would go with cross platform, as much as i enjoy native android way more than cross platform solutions, in the end i need to choose the client's needs over my preferences. Most apps don't need optimization and don't need to be close to native APIs.
Going the native path also doesn't guarantee good performance.
It is also important to note that if a cross platform solution works, and there are libraries to interact with camera, sensors etc, someone had to write the code for those to work, so it's not like cross platform solutions prevent you from interacting with native APIs, you can write your own library to do what you need with the native APIs, of course you would need to write 2 snippets of code, one for Android and one for iOS, but at least is not writing the whole application for both platforms.
And one last point, i think native options don't have "Code Push", so every change needs to go through the "release in the app store" process, which Google and Apple have the power to prevent from getting to the users (doesn't happen always, but can happen) and that may impact on the time it takes for bugfixes to get to users.
These are just things i know of, i don't have experience with these problems yet, but looking at these points it does seem like cross platform benefits outweigh the cons, that's why I would recommend going with something like React Native unless there is a really strong reason not to (other then preference).

[TriNguyen-ymhf]

Since Jetpack compose release, I prefer android native than crossplatform. Its so much easier

[VilRapt]

Currently if you have dedicated teams per platform - they will deliver same amount, regardless. Developing adapters for cross platform infrastructure is taking same, if not more time, than just native development per platform and yet does not deliver same flexibility. The quality of deliverables will also be questionable. If you're not a startup, with limited funding and resources - you should always consider native.
Another aspect is performance, many people use to claim that modern hardware allows us to ignore this aspect. Me on the other hand seen too many apps unable to find an audience just because it takes 500mls longer to load a splash screen than competitor. Yes hardware is getting better for some, but code quality is getting worse for all and often those 5 low end devices will deliver better income than 1 higher end...

[SriHarshaChilakapati]

Cross platform is not completely there yet. While it is true that you can make multi-platform apps in Flutter/React Native/KMM, maintaining these codebases over the years become a lot harder. I have seen many of people who started new projects in RN or Flutter do rewrite entire app in native after an year or two. However, this is only a time based problem happening because of non-existent best practices for these toolkits.

[bwoogie]

Native is the way to go. But takes longer. I've tried writing apps in xamarin and it gets frustrating because it just doesnt seem like its there yet. and the documentation is lacking.

[theophilus]

The funny thing is the big tech company are not cross platforming their applications but the start ups that cannot afford maintaining two teams run with cross platform. I prefer and use native cos of programming standards and design patterns. Just a preference though..

[lutfiikbalmajid]

i am building in project sealing the QR Code content, approximately more than 2000 character, using react native, its fast development, just working fine using iphone, but, when it comes using android, my scanning time its not responsive, then i move to native app using kotlin and boofcv library. yeah you are right, when it come using native API, the performance using cross platform is slower