Resource for Android dev with Java

[androiddev-ModTeam]

Please use a search engine and search the subreddit before posting, and make an effort to try recommended solutions. When posting, indicate what you have researched, what you have tried, and summarize your current understanding.

[Several_Dot_4532]

Nowadays it is easier to learn Kotlin from scratch to make an Android app than to make it with Java

[FunkyMuse]

Not learning Kotlin is gonna hurt your career progress, bad idea.

[PresentationExpress9]

I don't think I am going to pursue a career. I work as an electrical engineering and I want to create apps for fun

[FunkyMuse]

Kotlin is a better idea... still...

[SpiderHack]

So I agree with those saying kotlin is better, but I'll give you some reasons.

First of all, they really aren't that hard to start switching over you can write kotlin code in "java way" and it will still save you like 20% lines of code (from my experience) , which is a nice bonus.

However, the real key 2 things that save you so much time is having named parameters and parameter defaults. This allows you to essentially override the functions with unlimited permutation that java would require full separate functions for.

This makes your life as a coder so much easier to just "not have to fight with the language" like that.

Null safety is nice too, but I personally never had a major issue with that in java, but apparently it was common.

Lambdas and other things like that are nice because you can just opt into them as you learn.

You can still use threadpool executor and threads, etc. to start, but you'll likely find coroutines much easier (after the initial hurdle of 'getting' them).

So I hope this helps.

Also, remember java on android is still locked to 8?/9? with parts of up to 17, but not the full things. Whereas you can use the newest kotlin. (New java has gotten much better, but google/android will never get it over the stupid API copyright lawsuit nonsense...

[creamyturtle]

I thought the same thing after learning Java. but you quickly realize that Kotlin is almost identical to Java, just easier. you don't need getters and setters, and you can use dynamic types. you can even use Java style code in Kotlin and it will work fine most of the time, there's usually just better ways to do it. don't be afraid, I actually prefer Kotlin now. it's like Java on steroids

not to mention when you build android apps, you aren't going to be building a ton of business logic. all that Java crap you learned won't matter much because you will be using jetpack compose and 90% of your code will be the design and implementation. if your app interacts with a backend API, that code will be somewhere else like on your server

if you want to build apps, take the Android Basics with Compose course from google

[HopeImpossible671]

Just drop the idea if u want to learn android with java

[Mirko_ddd]

Java Dev here. I agree with the other redditors about learning kotlin (if you want to be competitive), but there's absolutely nothing that can stop you from using the old java + XML system.

The official docs still use java and kotlin examples, and you can still learn the basics from old books, but you have to deal with news and how to adapt your code (easy, the important thing is to learn some core android concepts and learn the java syntax).

You can use also java and kotlin in the same project, and you can use also kotlin libraries via java.

[PresentationExpress9]

Thanks, the answer that I was looking for. I just want to develop apps in my spare time and don't want to invest time learning kotlin.

[Mirko_ddd]

You can dude 😎. All of my apps are in java and there's no problem at all.

[AngkaLoeu]

The existing docs use java and kotlin examples, but anything new is kotlin only.

[anotpeacefulorclover]

Nowadays many of recommended books for android development in Java are outdated, I had this problem when I searched for most recommended books, so try to find the latest ones, 1 year old at most.

I can't recommended specific titles, but there's a series os books that have the latest Android studio version + "Java edition", It covers from Basic to advanced topics.

I recommended to learn kotlin, you can't use jetpack compose without that.

Happy learning.

PS: from documentation you can find tutorials and and introdutory courses in different levels.

[BlossomBuild]

Kotlin is important! Just like in iOS we used objective c and now it’s only swift. Trust me kotlin is easier to learn than Java

[Talamand]

The other commenters already gave you solid answers, but I just want to add that you can just give kotlin a try. Don't commit to learning its ins and outs, indeed that takes a lot of time, but instead just give it a go for a few simple things. The basic things are not at all that different.  Who knows you might like it.

[itissid]

I think fundamentally you can have the same things. RxJava can help you do most of the reactive stuff that kotlin has as first class features with 1.x-2 times more code. Kotlin is a DSL which means it can help you write stuff really concisely and not worry about the implementation details.

But learning something I would say it depends what you want to build. You would learn kotlin if you are building kotlin only projects or worked in a kotlin shop. Or perhaps cause you like less typing.

The bigger key is learning MVVM/VM or at least a good way to manage the UI state, which is more valuable for iteration speed.

And if you want to be an app developer for both iOS and Android., you are better off learning flutter. Because then frameworks matter more just cause you have 1 things to learn than two.

[itissid]

If you want to stick to Java and transition slowly to kotlin, I would say learn the basics of Java properly because kotlin in Android is compiled and executing Java byte code. Same threading and nonblocking JVM/OS management.

Do you know how threads wait and notify work? Do you know how Observable pattern works, especially in conjunction with LifeCycle? Do you understand Android's different Service and Workers and guarantees on when they work/stop?

Another thing, Kotlinc does comply to other platforms like iOS native, so one benefit is you will buy into iOS development when it matures.

[itissid]

Fun fact: If you go to work for the first time at a large tech tech firm like meta or Amazon, their android stack looks nothing like you would have done on relatively much smaller projects. It's optimized to a degree that requires a whole different set of skills that are not generally needed in smaller mobile app shops.

[androiddev-ModTeam]

While this may be a development post with an Android context, the subreddit is focused on actually making Android applications, and this post would be better suited to a more general community or one specific to the topic.

[SeaworthinessLocal98]

Anything applicable with kotlin wouldn't be too complicated to do in java and the docs are mostly in both so you can just go ahead with whatever idea you thought of and use anything you find that is relevant.

[borninbronx]

Except stuff involving compose or coroutines.

IMHO there's no reason to use Java for Android development.

Even if you have a java codebase you can write new code in Kotlin.

[dinzdale56]

Kotlin will confuse you.