I quit because of 1) Overdependence on Google and their many policies 2 ) Lack of remote jobs 3) Lack of physical jobs , everyone wants a flutter or React Native developer.
same, i almost quit and switched to backend & flutter mainly due to 2 reasons 1. Lack of Native jobs as you said or even some jobs but minimum experience required 5-7 Yrs 2. Even if found a job, the salary is less. :( Pretty sad.
Let me tell you something. I started android development with java back in 2017. about a year later I found React native very charming with its cross platform nature so I switched to React native .now after five years I am switching back to native android with Kotlin and jetpack compose . My reason for switching back is as a cross platform mobile developer you don’t have any dominance over your platforms. You don’t know the internals of how things of get done. Your knowledge about the platform you are developing app for is very low and you always work with prewritten plugins and don’t get engaged in native platform apis . For example a cross platform developer does’t know about work managers, content providers, broadcast receivers or scoped storage. If you are an android developer you should understand the OS very well not just working with plugins and libraries
the problem with android is too fast deprecating some features, this happen to me when first time learning async task, i just learn in that day, but then after less than 1 week, it got deprecated
@@luckydevil1601 i'm not talking about the deprecation is only in android dev, i'm talking about how quick they decide to make some api and then deprecating it, altough, it is not much problem for professionals or experts, but this kind of thing really stressfull for beginners
I do both Android and iOS -- hear the truth. 1. DI is convoluted in Android and sold as the second coming, when in most cases it's not needed. 2. Google has changed APIs completely, leading to two very different implementations (Camera API, Instant Aps API, etc...) 3. APIs are more important than basics, if you learn Retrofit, would you learn how to write an HTTP client? Why would you need to understand how it works? Have not quit Android, took a job where I focus on Android, because I was close to quitting and becoming an iOS dev.
True for me. Couldnt find a job in native Android in my area so i had to switch to web dev. Where I work they use cross platform like flutter for mobile apps as it can Target multiple platforms from one codebase and suits most project requirements
People also don't realise that android can be a kind of a fullstack on it's own compared to web, where every website needs a well done backend to seem easy to work on.
Android dev is getting better and better IMO - I could not go back to the days when everything was done in the Activity, and state was shared via Intents from Activity to Activity. Nowadays with Jetpack Compose and Viewmodels, plus your favourite DI (Hilt or Koin), it's actually a rather beautiful thing to work with - if people are leaving, well, more work for the rest of us!
I started in Android and now do web dev. I have not quit android though, I just wanted to build a home page for my app. I will say this. Coding in Android feels more official while webdev feels super hacky sometimes. I love them both.
@@vectoralphaSec It's a tool kit for building UIs. I think compose is easier and more fun compared to XML. Jetpack compose reminds me of Flutter. I'd recommend it =)
@@vectoralphaSec older way is hard compared to jetpack compose. Basically jetpack compose is a new/modern way to code for Android ui. It has no connection with old approach (xml) . But many industry has legacy code. So it's good to learn the old approach too, so u know what's going on in the code and can convert it with jetpack compose. Imo focus on one thing. Once u grasp the basic principles then focus on logic separation (using mvvm and other codding patterns, but for Android mvvm is more than enough)
@@vectoralphaSec i'd say that Compose is easier in the long run, but xml is easier in the short run. Compose is much more elegant (and less bug-prone) in terms of keeping the UI in sync with whatever data has to be displayed = basically state management. however, you have to wrap your head around some new concepts before you can benefit from this and use Compose properly.
Google is making unnecessary things complex so many are finding difficult to update. Even if they get update it is hard to find a job for 10+ years experience...
I will keep doing Android, but backend also gets my attentions, because it doesn't depend on Google, and it is nice to take a break from having to keep an eye out for every google policy
I used to be a native iOS developer, now I am primarily a backend developer. I still love native mobile development, unfortunately the project came to an end and I had to look for alternatives. Like many others have said, there just aren't as many native mobile developer jobs outside of the main tech centres, and the few companies that are looking for mobile devs, they want cross-platform. I haven't done much Android, but I have worked in Kotlin, which is a lot like Swift. My issue with Android is all the dependencies it seems to require. A lot of iOS development you can mainly rely on first party stuff for everything.
As a beginner I find Android very difficult and I think it's really overengineered, I'm currently struggling so much to understand just an architecture to start a project, but who want to quit?
@@meenotekittutorials348 I'm currently trying to develop my first app to publish on play store, just to learn the process from the creation to the publish and management of the app
It's not that it's complex, but that it's a mess of overbloated code that's getting needlessly changed for no apparent reason and, most importantly , a complete lack of documentation.
Those were the golden times, when Android 2.2 Froyo, and 2.3 gingerbread were there, until GOOGLE's shitty developers unnecessarily started their egoistic path to modify already stable framework, created wrapper classes over wrapper classes over and over again. Android was way easy than iOS, but not now.
Unfortunately I think the grass is indeed greener on the other side, android is complex but the problem is there aren't actually that much resources. I am not joking there are people indeed explaining the basics but once you are in the intermediate-advanced territory I think its only you Phillip. We often joke about it with my friend
@@vibovitold i agree, but we are referring to the new projects. Most new devs are choosing the Flutter route. If you've been following the growth of Flutter you would see what I'm saying. Jetpack compose came in late to the party
@@ka61er See the basic implementation of RecyclerView, for showing simple list we have to create 2 XML + 2 classes. On other hand in compose it is literally 5/6 lines.
Android development has been improved alot over the years. Google has invested much into Android developer ecosystem and we have started seeing results
For our app which is delivered in several platforms, the Android version is the slowest to develop, and the Roku is the fastest. That's with the bulk of our developers working in Android.
@@enossalar8837 I think that user is just trolling. Kotlin Multiplatform is already used by many companies in production apps (including 9GAG, Netflix, McDonald's to name a few) and even Google is migrating their Workspace suite (Docs, Slides et cetera) towards KMP.
I hate finding comment sections like this, I just learned enough jetpack compose to start doing projects and now I'm questioning everything. I heard Flutter has less jobs and you still need a background in native android or ios dev but now it seems like getting a native android job is harder. What do I do 😢
@shubham.pandey I stayed with it for a pretty dumb reason, flutter apps just don't seem as fluid as native apps to me. Most big companies still rely on native apps too, and even if I eventually switch, background in native android still looks quite good on a resume.
well if one compares apple development and google android it´s hilarious how google thinks to have dozens of languages and dozens of frameworks around the languages (flutter, dart, java, kotlin, go ...). well apple has only swift ... complex doesn't necessarily mean high tech ...
Well, the argument, that you should not leave because something else might be troublesome as well: Would you stay in a place, year after year, only because someone says "Somewhere else it might suck as well."? And I have to disagree: iOS have become more and more accessible over the years. In iOS they REALLY try to reduce the complexity.
Its just because hiring manager doesnt respect person having only android experience, so ppl have to switch to add more skills. At job hunt everyone expects to have iOS & web exp. as well. OR cross platform. Irony is if you skip android and start learning & working on react native, you will be left behind in Android.
I may leave android one day because of following reasons 1. Flutter is rising 2. In Android classes and methods keeps on deprecating 3. KMM is not less than a shit. Really its garbage. 4. When you can build better apps with flutter then why android 5. Both flutter and React Native offer better salary packages as compared to Native Android 6. KOTLIN is not new language it is just enhanced version of java. 7. Google is focusing more on flutter as compared to KMM. Share you reasons if you are thinking to switch.
iOS development does have its perks for sure! Apple offers a great codebase for native app development, their own beautiful programming language, a first-party cross-platform native UI framework and an audience of users who are willing to pay good money for good software. However, neither the users nor the developers have as much freedom as does the Android community: Apple basically rules everything. On Android, however, the development is quite a bit more complex, the "device zoo" is much more diverse, the libraries and build tools are far from perfect (but I have to admit - really catching up lately), the APIs are always changing, but the freedom is always there: you can make whatever app you want, distribute it however you want, and the user can install anything they please from anywhere they please.
As much as many of us love Android, the conditions offered by companies to developers and by Google to freelancers who want to publish apps are no longer attractive. The ecosystem is saturated with endless new bells and whistles to learn at a borderline irrational rate, in what is being marketing as an "exciting learning opportunity". Anybody who is not an Android content creator is already in a disadvantage, and competition is numerous even if they are not as good as they look.
Everyone wants to use JS on everything and companies to want save money too by hiring 1 person who use crossplatform solution and like to take two roles of both iOS and Android for less
It's a harsh truth that app development community is dying😢 and there are very few creators like Phillip who are still there to keep the community uplive
Nothing is dying, there are lots of creators. If you just look at native android with kotlin, yes there are little, but it's quite a small niche which can't be compared to web dev or so
I disagree. I've coded in native iOS, flutter and native android with Android Studio and can confidently say that android studio sucks really bad - gives unnecessary errors (especially with Gradle), extremely slow, and unnecessarily complex. Just go with flutter or web if you can.
What I don't like is some example are overly complicated while other examples are too simple, if you follow the documentation from the official android doc. But otherwise GPT can really help with their examples if sometimes you don't understand
I think it's not about complexity moreover it depends about what kind of project you are doing, there are many frameworks nowadays that you can use to do the same project in a shorter amount of time, and even to ios or even web applications like react-native. so such a thing would interest any developer I guess to switch from android native to something else
The problem is that developers are great at making things unnecessarily complicated. The issue will occur for them no matter which technology they choose.
I switch to web dev for a couple years and now back on Android with a much better understanding of the ideas that android uses I can do backend iOS dev now thanks to Phillip!
Is there really a trend in people leaving android development in such large numbers that it has an impact on the market? I cant find any source that says this is true.
Old Android devs who started 2005-2015 who are still using java and xml are faced with a choice, learn Kotlin and JC, or learn flutter and have the IOS and web app version made for free as well as the android version. People who used to post job offers for native android are now offering jobs for flutter devs instead, so they don't have to hire as many devs.
Everyone wants hybrid developers, be it React Native, flutter, Ionic or any other hybrid cross multi platform.. since kmm has come.. I guess people would stick to native
Complex ? I dont understand why people say its complex. Well there's always some versioning issues with gradle but i dont think its complex.Things are going well on my side.
I am 17 and working in Android from past one year with java and i like it very much 😊😊😊 but i am unable to move with kotlin as i get confused with kotlin
Which I've never questioned with this short, but the complexity one doesn't count for me (and I get messages from followers on a daily basis about this)
Im also one of those who like to complain , in a web project managing state became hell for me, in wpf I couldnt figure out how to bind a radio button and its value to a variable, in android cannot understand why are they so many lifecycles, and why are fragments with their weird lifecycles so annoying
@PhilippLackner what should i do if im corrently in school trying to learn physics and calculus. And im going heavy on that. How do i keep coding at the same time??
Google and it's policies are the problem
Excuse?
I agree, google policies in PlayStore are RIDICULOUS!
I quit because of
1) Overdependence on Google and their many policies
2 ) Lack of remote jobs
3) Lack of physical jobs , everyone wants a flutter or React Native developer.
Which niche has more remote jobs?
@@619ry7web dev
same, i almost quit and switched to backend & flutter mainly due to 2 reasons
1. Lack of Native jobs as you said or even some jobs but minimum experience required 5-7 Yrs
2. Even if found a job, the salary is less.
:( Pretty sad.
I switched too. Now i have a dev remote job and i love it. I'm liberated
what did you switch to and how long did it take?@@OnichanDeez
Let me tell you something. I started android development with java back in 2017. about a year later I found React native very charming with its cross platform nature so I switched to React native .now after five years I am switching back to native android with Kotlin and jetpack compose . My reason for switching back is as a cross platform mobile developer you don’t have any dominance over your platforms. You don’t know the internals of how things of get done. Your knowledge about the platform you are developing app for is very low and you always work with prewritten plugins and don’t get engaged in native platform apis . For example a cross platform developer does’t know about work managers, content providers, broadcast receivers or scoped storage. If you are an android developer you should understand the OS very well not just working with plugins and libraries
I agree.
In my opinion if a tool can do what I want, then it is good😅
Nah @@pemrograman-cepat3393
Basically no Android jobs in my area. The question should be why no/so little companies are hiring Android devs?
the problem with android is too fast deprecating some features, this happen to me when first time learning async task, i just learn in that day, but then after less than 1 week, it got deprecated
Agree. And leaving development aside, we should have stopped at Abdroid 10
the async task was an acceptable solution for many years, however, it was wrong from the very beginning.
You do realise that features being deprecated is typical for any development, not just android?
@@luckydevil1601 i'm not talking about the deprecation is only in android dev, i'm talking about how quick they decide to make some api and then deprecating it, altough, it is not much problem for professionals or experts, but this kind of thing really stressfull for beginners
and it still somehow works :D
Dude, the problem is the company who think hybrid app development is cheaper, hiring 2 developers ios and android as 1 salary with 2 workloads.
I do both Android and iOS -- hear the truth.
1. DI is convoluted in Android and sold as the second coming, when in most cases it's not needed.
2. Google has changed APIs completely, leading to two very different implementations (Camera API, Instant Aps API, etc...)
3. APIs are more important than basics, if you learn Retrofit, would you learn how to write an HTTP client? Why would you need to understand how it works?
Have not quit Android, took a job where I focus on Android, because I was close to quitting and becoming an iOS dev.
they're quitting because it's becoming impossible to find good jobs
Why is that?
@@Elkasinox i wish i knew why 😭
True for me. Couldnt find a job in native Android in my area so i had to switch to web dev. Where I work they use cross platform like flutter for mobile apps as it can Target multiple platforms from one codebase and suits most project requirements
Jobs are there but for less experienced people, but for 10+ year people having less opportunities due to salary expectations. 😮
This job need more exp to work, so hard for student who just graduated from university
People also don't realise that android can be a kind of a fullstack on it's own compared to web, where every website needs a well done backend to seem easy to work on.
Being a bit complex is always good.. as due to this complexity this too pays well..
And teaching complex things is also fun at a certain level
I hate it but have to learn it i guess. its too wordy though but I write down a categorise expressions and helps
Android dev is getting better and better IMO - I could not go back to the days when everything was done in the Activity, and state was shared via Intents from Activity to Activity. Nowadays with Jetpack Compose and Viewmodels, plus your favourite DI (Hilt or Koin), it's actually a rather beautiful thing to work with - if people are leaving, well, more work for the rest of us!
What about Google policies?
They literally sucks
Now they asking for 20 testers
I started in Android and now do web dev. I have not quit android though, I just wanted to build a home page for my app. I will say this. Coding in Android feels more official while webdev feels super hacky sometimes. I love them both.
Lol this is spot on
The most of them quit,, the better is for us
Im learning flutter development so I can get freelance projects. Still I focus on android development. Jetpack compose is much fun to code with
i quit android dev...but again start with jetpack
Im new to android. I just started 4 days ago. What is Jetpack Compse? Is it harder and more complex? Was the older XML way easier?
@@vectoralphaSec It's a tool kit for building UIs. I think compose is easier and more fun compared to XML. Jetpack compose reminds me of Flutter. I'd recommend it =)
@@vectoralphaSec older way is hard compared to jetpack compose. Basically jetpack compose is a new/modern way to code for Android ui. It has no connection with old approach (xml) .
But many industry has legacy code. So it's good to learn the old approach too, so u know what's going on in the code and can convert it with jetpack compose.
Imo focus on one thing. Once u grasp the basic principles then focus on logic separation (using mvvm and other codding patterns, but for Android mvvm is more than enough)
@@vectoralphaSec i'd say that Compose is easier in the long run, but xml is easier in the short run.
Compose is much more elegant (and less bug-prone) in terms of keeping the UI in sync with whatever data has to be displayed = basically state management.
however, you have to wrap your head around some new concepts before you can benefit from this and use Compose properly.
Google is making unnecessary things complex so many are finding difficult to update. Even if they get update it is hard to find a job for 10+ years experience...
I will keep doing Android, but backend also gets my attentions, because it doesn't depend on Google, and it is nice to take a break from having to keep an eye out for every google policy
I used to be a native iOS developer, now I am primarily a backend developer. I still love native mobile development, unfortunately the project came to an end and I had to look for alternatives. Like many others have said, there just aren't as many native mobile developer jobs outside of the main tech centres, and the few companies that are looking for mobile devs, they want cross-platform.
I haven't done much Android, but I have worked in Kotlin, which is a lot like Swift. My issue with Android is all the dependencies it seems to require. A lot of iOS development you can mainly rely on first party stuff for everything.
As a beginner I find Android very difficult and I think it's really overengineered, I'm currently struggling so much to understand just an architecture to start a project, but who want to quit?
How's your journey going now?
@@meenotekittutorials348 I'm currently trying to develop my first app to publish on play store, just to learn the process from the creation to the publish and management of the app
Complex may be, but incredible rewarding
It's not that it's complex, but that it's a mess of overbloated code that's getting needlessly changed for no apparent reason and, most importantly , a complete lack of documentation.
Those were the golden times, when Android 2.2 Froyo, and 2.3 gingerbread were there, until GOOGLE's shitty developers unnecessarily started their egoistic path to modify already stable framework, created wrapper classes over wrapper classes over and over again. Android was way easy than iOS, but not now.
Google themselves are responsible for this mess
Apperantly Back into Lapland development is a thing😂
Check the subtitles of the backend development Phillip
I caught that too...well done fellow techie with an eye for details 👍
He is using an Ai Probably
@@Asterx5Who isn't?
Unfortunately I think the grass is indeed greener on the other side, android is complex but the problem is there aren't actually that much resources. I am not joking there are people indeed explaining the basics but once you are in the intermediate-advanced territory I think its only you Phillip. We often joke about it with my friend
It's Philip, Coding in Flow and couple of American devs + Udacity Android Course. The rest is BS...
Sadly coding in flow has also moved to web dev.
Agreed. Bigger the community, better the help
When developers can't even be bothered to manually subtitle their own videos...
Android was unnecessarily complex. Unfortunately Jetpack Compose came in late. Also Flutter has cannibalized native Android development.
Is jetpack compose any good? Ive never used it. Does it even change anything for Android dev??
"cannibalized"? native Android projects outnumber Flutter projects by a vast margin.
@@vibovitold i agree, but we are referring to the new projects. Most new devs are choosing the Flutter route. If you've been following the growth of Flutter you would see what I'm saying. Jetpack compose came in late to the party
@@nejitawo9657 can you provide some source for this claim?
When we mix android complex with MVVM we understand why people leave this
If Google would launch Jetpack Compose much earlier, then it will be more easier for the developers as compared to XML.
:)) you think xml is harder than jetpack because you dont have exp about that
@@ka61er See the basic implementation of RecyclerView, for showing simple list we have to create 2 XML + 2 classes. On other hand in compose it is literally 5/6 lines.
Xml is shit
@@hdkloh6857but then you have "to offer a dance to the sun" to get it perform as you want, lag is always there😂
As i scroll through comment, the problem is on the market phillip. We are doomed to Flutter and i agree because it is hard to native jobs.
I believe many are quitting due lack of job offers
Lack of job offers in android dev ?? 🤨🤨🤨 Are you blind ? Or maybe you live in madagascar ?
Exactly, I just started React.
Well getting an offer in other areas are hard too
True, :( sad
Android development has been improved alot over the years. Google has invested much into Android developer ecosystem and we have started seeing results
"if you switch to ios development to back into lapland" - Philipp Lackner, 2023
😂😂😂😂 those captions
I can't believe that Philipp was web!
That's everywhere
people who did android and ios and web said that android was the hardest because of the variety of devices
It's all about having an interest in that particular technology.
For our app which is delivered in several platforms, the Android version is the slowest to develop, and the Roku is the fastest. That's with the bulk of our developers working in Android.
personally had been contemplating switching to iOS, but kmm made me change my mind!
You're joking? Kmm is still garbage
@@j2shoes288why is it garbage?, can you explain a little bit more, I'm thinking to start KMM, if you give more info, I will appreciate it
Threads app from Meta used entire KMM bro
@@enossalar8837 I think that user is just trolling. Kotlin Multiplatform is already used by many companies in production apps (including 9GAG, Netflix, McDonald's to name a few) and even Google is migrating their Workspace suite (Docs, Slides et cetera) towards KMP.
@@ka61erthat’s why it didn’t do well 😭😂
Industry is also slightly moving towards Flutter & React Native. But demand for native will always there.
But why?? Does Flutter & React still have any drwaback?
@@user-ow7sh3rq9vthere Ux feel like web page and the size issue is always there
In other words. Dont quit keep going 😊
I hate finding comment sections like this, I just learned enough jetpack compose to start doing projects and now I'm questioning everything. I heard Flutter has less jobs and you still need a background in native android or ios dev but now it seems like getting a native android job is harder. What do I do 😢
Same situation bro..😢
I'm in similar confusion.
Are you still doing Android or switched?
@shubham.pandey I stayed with it for a pretty dumb reason, flutter apps just don't seem as fluid as native apps to me. Most big companies still rely on native apps too, and even if I eventually switch, background in native android still looks quite good on a resume.
@@magar6247 How's android dev going?
A fancy way so say "skill issue"
well if one compares apple development and google android it´s hilarious how google thinks to have dozens of languages and dozens of frameworks around the languages (flutter, dart, java, kotlin, go ...). well apple has only swift ... complex doesn't necessarily mean high tech ...
back into lapland
When others quit, that's when I step in. My niche has been made
Well, the argument, that you should not leave because something else might be troublesome as well: Would you stay in a place, year after year, only because someone says "Somewhere else it might suck as well."? And I have to disagree: iOS have become more and more accessible over the years. In iOS they REALLY try to reduce the complexity.
"deprecated"
I'm a web developer. It's not less complex over here.
I quit last year after doing 5 years. I'm 💯 sure I'm not going to miss Gradle.
I am an android developer since 2013, android development is getting more complex
what makes things complex now?
Its just because hiring manager doesnt respect person having only android experience, so ppl have to switch to add more skills. At job hunt everyone expects to have iOS & web exp. as well. OR cross platform. Irony is if you skip android and start learning & working on react native, you will be left behind in Android.
I may leave android one day because of following reasons
1. Flutter is rising
2. In Android classes and methods keeps on deprecating
3. KMM is not less than a shit. Really its garbage.
4. When you can build better apps with flutter then why android
5. Both flutter and React Native offer better salary packages as compared to Native Android
6. KOTLIN is not new language it is just enhanced version of java.
7. Google is focusing more on flutter as compared to KMM.
Share you reasons if you are thinking to switch.
I’m thinking to switching to IOS but if it’s actually worth it
Gradle!! Tooling sucks. When i tried Android development and run my app it took ages after that I uninstalled android studio immediately
iOS development does have its perks for sure! Apple offers a great codebase for native app development, their own beautiful programming language, a first-party cross-platform native UI framework and an audience of users who are willing to pay good money for good software. However, neither the users nor the developers have as much freedom as does the Android community: Apple basically rules everything.
On Android, however, the development is quite a bit more complex, the "device zoo" is much more diverse, the libraries and build tools are far from perfect (but I have to admit - really catching up lately), the APIs are always changing, but the freedom is always there: you can make whatever app you want, distribute it however you want, and the user can install anything they please from anywhere they please.
As much as many of us love Android, the conditions offered by companies to developers and by Google to freelancers who want to publish apps are no longer attractive. The ecosystem is saturated with endless new bells and whistles to learn at a borderline irrational rate, in what is being marketing as an "exciting learning opportunity". Anybody who is not an Android content creator is already in a disadvantage, and competition is numerous even if they are not as good as they look.
Good advice sir...keep rocking with compose
Im new. Is compose hard? Was the older way of xml easier?
@@vectoralphaSecits kinda like a version of flutter framework.(for design part)
Like people talking about a useEffect 😂but just using it ....
Yes, Android is becoming too complex. I switched to Flutter. Way easier and it's cross platform.
android its a pain, its hard implements a simple rich editor, for implements a unordered list🙄🙄..
there are mistakes in the subtitles, need to check automatic work next time.
Developing/programming is complex and hard.
Everyone wants to use JS on everything and companies to want save money too by hiring 1 person who use crossplatform solution and like to take two roles of both iOS and Android for less
"Android is too dependent on Google so I'll learn a frontend framework owned by other companies THANK YOU VERY MUCH"
It's a harsh truth that app development community is dying😢 and there are very few creators like Phillip who are still there to keep the community uplive
Nothing is dying, there are lots of creators. If you just look at native android with kotlin, yes there are little, but it's quite a small niche which can't be compared to web dev or so
I go into android from iOS for android’s challenge. It is more interesting.
Coding in Flow left us :(
What do you mean?
@@niteshgupta1118 he switched to web dev
Sad bro. He's the friend to newbies
I disagree. I've coded in native iOS, flutter and native android with Android Studio and can confidently say that android studio sucks really bad - gives unnecessary errors (especially with Gradle), extremely slow, and unnecessarily complex. Just go with flutter or web if you can.
Don't let this dude guilt you in doing unnecessarily complex stuff. Life is too short for that.
so true Philip!!
Actually people quite native development and switching to cross platform Flutter, I think as per market demand is also the reason
What I don't like is some example are overly complicated while other examples are too simple, if you follow the documentation from the official android doc. But otherwise GPT can really help with their examples if sometimes you don't understand
I hate when official android doc is pice of shit, with only few code examples without any contet what its do or where i should put it...
I think it's not about complexity moreover it depends about what kind of project you are doing, there are many frameworks nowadays that you can use to do the same project in a shorter amount of time, and even to ios or even web applications like react-native. so such a thing would interest any developer I guess to switch from android native to something else
finally someone talks about this
Developers like to complain 😭 well put 😂
Lapland development appearing as I'm currently in Lapland 😎
The problem is that developers are great at making things unnecessarily complicated. The issue will occur for them no matter which technology they choose.
U are right 100%
Ich bin extra von Web zu Android, da Web Entwicklung frustrierend und old school ist. Android mit compose und kotlin sehr modern.
Don't try. Just do it 💪
Well said... 🥰
Well said
I switch to web dev for a couple years and now back on Android with a much better understanding of the ideas that android uses
I can do backend iOS dev now thanks to Phillip!
nice automatic captions... back into lapland :D
But what if I enjoy Lapland development? Don’t the Sami deserve development too?
Well , i think they quit android and join flutter as flutter is now multiplatform
Is there really a trend in people leaving android development in such large numbers that it has an impact on the market? I cant find any source that says this is true.
I believe that after rounds of layoffs people struggled to find jobs as Android so they switched techs
Old Android devs who started 2005-2015 who are still using java and xml are faced with a choice, learn Kotlin and JC, or learn flutter and have the IOS and web app version made for free as well as the android version.
People who used to post job offers for native android are now offering jobs for flutter devs instead, so they don't have to hire as many devs.
the choice of learning Kotlin was made years ago, otherwise they wouldn't really be Android devs anymore.
@@vibovitoldNot if you work in a company with an old enough code base that hasn't made the jump to Kotlin. There's a TON of legacy code in the world.
Everyone wants hybrid developers, be it React Native, flutter, Ionic or any other hybrid cross multi platform.. since kmm has come.. I guess people would stick to native
I would rather quit Android because is controlled by Google…
Yes, it's true, but that is not the main reason, I don't think it's a reason to quit something at all
Complex ? I dont understand why people say its complex. Well there's always some versioning issues with gradle but i dont think its complex.Things are going well on my side.
Ya but can u reverse a linked list
I am 17 and working in Android from past one year with java and i like it very much 😊😊😊 but i am unable to move with kotlin as i get confused with kotlin
If you pick up another functional language or two, you'll find syntax and other similarities that Kotlin has amalgamated into it's language model.
I've done some C and Java before Kotlin and I found the switch so easy... Kotlin i s easier and less code than Java. You should give it anotehr try.
This short 😂. There are tons of legit reasons to switch from android. Ive never heard the "to complex" excuse
Which I've never questioned with this short, but the complexity one doesn't count for me (and I get messages from followers on a daily basis about this)
Im also one of those who like to complain , in a web project managing state became hell for me, in wpf I couldnt figure out how to bind a radio button and its value to a variable, in android cannot understand why are they so many lifecycles, and why are fragments with their weird lifecycles so annoying
Android devs should become full stack instead or at least have a bit of experience in another areas, in order to become irreplaceables.
@@SinnuC So a generalist is less replaceable than a specialist?🤔
@PhilippLackner what should i do if im corrently in school trying to learn physics and calculus. And im going heavy on that. How do i keep coding at the same time??
Reading all this, as someone who just started learning Android dev last week, should i be discouraged?
From my perspective, Android is still a great technology to learn
Perfect
they themselves have been pushing flutter like crazy for the past few years. why won't the devs quit it themself
I heard Flutter is easier than Native development + it's cross platform. Any thoughts?
Watch the video 😁
@@PhilippLackner😢
@@PhilippLackner Lol. Self goal by me. 😂
@@PhilippLackner😢
If compose multiplatforn gets easier i will switch to it...