https://www.youtube.com/watch?v=Awi4J5-tbW4

safe to say at this point, Kotlin is the default way to go for Android development.

qtguru:
safe to say at this point, Kotlin is the default way to go for Android development.

I have beem writing to you for a long time, please reply.

Only need an advice.

MadarasBlade:


I have beem writing to you for a long time, please reply.

Only need an advice.

I replied hi and you never responded

qtguru:


I replied hi and you never responded

About programming, i just need a precise learning path bro.

Web dev.

So as not to waste time learning things that aren't important.

MadarasBlade:


About programming, i just need a precise learning path bro.

Web dev.

So as not to waste time learning things that aren't important.

hit me personally, I get what you mean, I replied to you from my yandex

qtguru:

https://www.youtube.com/watch?v=Awi4J5-tbW4

Google is focusing more on jetpack compose more than flutter in the summit

MadarasBlade:


I have beem writing to you for a long time, please reply.

Only need an advice.

I can help you if you wish to seek for help

Alphabyte:


Google is focusing more on jetpack compose more than flutter in the summit

I think they have one for flutter too

Alphabyte:


Google is focusing more on jetpack compose more than flutter in the summit

yeah even over Java too

qtguru:


yeah even over Java too

I love the new features in android studio but it will make it eat up space in RAM

Alphabyte:


I love the new features in android studio but it will make it eat up space in RAM

The feature that blew my mind is the DrawScope and rendering of Shader for Components.

qtguru:
safe to say at this point, Kotlin is the default way to go for Android development.

Greetings bro. Pls can i mail you? Need to discuss something with you please?

Mimisboygreat:
Greetings bro. Pls can i mail you? Need to discuss something with you please?

Sure

qtguru:


hit me personally, I get what you mean, I replied to you from my yandex

How can we talk personally
Should I use your mail?

qtguru:

https://www.youtube.com/watch?v=Awi4J5-tbW4

Samples for the summit built with compose and Kotlin

https://github.com/android/compose-samples

https://relay.material.io/

One good thing is if you are good with glide , Retrofit,Room, coil x Kotlin ,coroutines ,MVVM, Firestore ,Dagger in Kotlin you will find it easier in creating apps using compose in kt same logic .

The UI components is easy to create you copy them from material doc , paste and edit them in android no need to store the whole UI components in your brain .

https://developer.android.com/jetpack/compose/layouts/material

qtguru:
safe to say at this point, Kotlin is the default way to go for Android development.

It is the "only" way. Reason I disagreed with your previous post on needing Java.

Surprised at the interest in mobile development. At least, the tags to these things are surprising.

Guess the ADS was captivating.

BRATISLAVA:


It is the "only" way. Reason I disagreed with your previous post on needing Java.

Surprised at the interest in mobile development. At least, the tags to these things are surprising.

Guess the ADS was captivating.

Money that's why. Also, I have some projects in mind for Shopify too and Moodle. Mobile Dev is money, but it's a lot of code and engineering, which I don't mind. What I like about this is that I can reuse my Java Knowledge and still be able into Kotlin and both will compile. Easier said than done.

The likes of Sheriman and AlphaByte will motivate me, or I can hire interns to build the projects. but Mobile dev is lucrative today.

qtguru:


Money that's why. Also, I have some projects in mind for Shopify too and Moodle. Mobile Dev is money, but it's a lot of code and engineering, which I don't mind. What I like about this is that I can reuse my Java Knowledge and still be able into Kotlin and both will compile. Easier said than done.

The likes of Sheriman and AlphaByte will motivate me, or I can hire interns to build the projects. but Mobile dev is lucrative today.

Switching to Kotlin should be bearable for someone familiar with Java—you. As for mobile being a lot of code, I humbly disagree and agree. I'll agree with the engineering though.

I thought mobile development was dead here... At least, going by the posts. But, if you keep up your top 10 fluttering in it, number of posts/interest will be bound to increase.

And then I'll begin to sound like tasty KFC guy.

Meta is migrating its Android codebase from #Java to #Kotlin. Currently, their Android codebase contains over 10 million lines of Kotlin code.

One good thing about compose the models views and controllers are in Kotlin no XML the codebase is reusable and the logic interact with the UI components.

I just started learning about compose and it's just too awesome and beautiful. I remember the boilerplate code we usually write using recyclerview, adapter and view holder to display a list. This is now a breeze with LazyColumn composable with just 3-5 lines of code. This is just one out of many awesome stuff it has.
When building your UI with compose, you're mostly thinking of rows and columns.
I believe it's still growing and needs more improvement. Plus, google is fully supporting it

EbenG:
I just started learning about compose and it's just too awesome and beautiful. I remember the boilerplate code we usually write using recyclerview, adapter and view holder to display a list. This is now a breeze with LazyColumn composable with just 3-5 lines of code. This is just one out of many awesome stuff it has.
When building your UI with compose, you're mostly thinking of rows and columns.
I believe it's still growing and needs more improvement. Plus, google is fully supporting it

Have you built a fully fledged UI designed production app yet with Compose though? I don't mean to sound like a kill-joy but less code doesn't always mean it's better. For you to know the full power of a toolkit, you need to build a full fledged application & deploy it to production. If you're implementing MVVM or MVI with clean architecture, you're going to be writing a lot of boilerplate code on Android anyway, so that one is normal.

I would have more positive feedback when i have explored it to a large extent. I need to find all the Sweet spots myself. Another issue is stability, you have to stay on a specific Compose version and remain on it else each time you update, you might start getting compile time errors because things change really quick.

tosinhtml:


Have you built a fully fledged UI designed production app yet with Compose though? I don't mean to sound like a kill-joy but less code doesn't always mean it's better. For you to know the full power of a toolkit, you need to build a full fledged application & deploy it to production. If you're implementing MVVM or MVI with clean architecture, you're going to be writing a lot of boilerplate code on Android anyway, so that one is normal.

I would have more positive feedback when i have explored it to a large extent. I need to find all the Sweet spots myself. Another issue is stability, you have to stay on a specific Compose version and remain on it else each time you update, you might start getting compile time errors because things change really quick.

Oh Okay,
I haven't really built a fully-fledged UI-designed production-ready app yet. But, I have seen and read the opinion of other senior developers who have tried it; Compose is stable and production ready. Companies have started adopting it in their products screen by screen, component by component.

I'll assume you talk this way probably because you haven't tried other Mobile UI frameworks like Flutter, Swift UI, and React. The focus and benefits of Compose aren't really about writing less code but of course, it's one of the benefits. The thing is the shift in paradigm from an Inheritance style which the classic XML is designed with to a declarative approach. In the classic XML, we have a View class(which represents a rectangular area on the screen and is responsible for drawing and event handling). The TextView class is a subclass of the View class, which means that TextView inherits all the properties and functionality from the View class, plus adds specific logic for displaying text to the user. The exact hierarchy goes with a Button and an EditText and other ViewGroups. It goes down like a tree structure. Of course, it helps everyone reuse the ability for example for an EditText to have the ability to display stuff. The drawback is that we are limited to building complex UIs. With Compose, we can reuse Composables very easily and it's very intuitive. You can do lots of customization and behavior for your UI very easily. The point about Compose is simply about Composition in object-oriented programming(OOP). You can read more about it.

Like, this style of designing UI is overdue in Native Android. Flutter, Swift UI, and React are already doing well with this approach to building UI.
The only thing I love well about building UI with XML is the WYSIWYG editor which is great. I think it's suitable and helpful for beginners.
That said, you can still use Compose and XML together In your project.

Check this out: Thinking in Compose https://developer.android.com/jetpack/compose/mental-model

EbenG:


Oh Okay,
I haven't really built a fully-fledged UI-designed production-ready app yet. But, I have seen and read the opinion of other senior developers who have tried it; Compose is stable and production ready. Companies have started adopting it in their products screen by screen, component by component.

I'll assume you talk this way probably because you haven't tried other Mobile UI frameworks like Flutter, Swift UI, and React. The focus and benefits of Compose aren't really about writing less code but of course, it's one of the benefits. The thing is the shift in paradigm from an Inheritance style which the classic XML is designed with to a declarative approach. In the classic XML, we have a View class(which represents a rectangular area on the screen and is responsible for drawing and event handling). The TextView class is a subclass of the View class, which means that TextView inherits all the properties and functionality from the View class, plus adds specific logic for displaying text to the user. The exact hierarchy goes with a Button and an EditText and other ViewGroups. It goes down like a tree structure. Of course, it helps everyone reuse the ability for example for an EditText to have the ability to display stuff. The drawback is that we are limited to building complex UIs. With Compose, we can reuse Composables very easily and it's very intuitive. You can do lots of customization and behavior for your UI very easily. The point about Compose is simply about Composition in object-oriented programming(OOP). You can read more about it.

Like, this style of designing UI is overdue in Native Android. Flutter, Swift UI, and React are already doing well with this approach to building UI.
The only thing I love well about building UI with XML is the WYSIWYG editor which is great. I think it's suitable and helpful for beginners.
That said, you can still use Compose and XML together In your project.

Check this out: Thinking in Compose https://developer.android.com/jetpack/compose/mental-model

I know everything you're talking about regarding declarative approach & Android devs will have no choice in the future but to adopt Compose because that is direction Mobile Engineering is going in general, but Compose specifically being stable and production ready is what I am not quite sure of. I know some few companies using it in production and they are still having to deal with some issues as early adopters.

For example, I used Kotlin Multiplatform from Jetbrains personally and also use it in my company, therefore I can suggest the best usecase for it when asked to recommend, not just because company X or person Y says it's awesome, because they always hype everything, same way they were hyping out React Native but when you actually implement it for big projects, you'd find that the performance was problematic. We wanted to also use Compose earlier this year in my company and after going through the drawbacks, we decided it was not yet time.

My point is, it needs a lot of improvement. It is not yet as awesome as Google engineers make it seem. At least not yet.

If you really want to get proper feedback of Developers regarding a tool, ask on @AndroidDevs Reddit.

tosinhtml:


I know everything you're talking about regarding declarative approach & Android devs will have no choice in the future but to adopt Compose because that is direction Mobile Engineering is going in general, but Compose specifically being stable and production ready is what I am not quite sure of. I know some few companies using it in production and they are still having to deal with some issues as early adopters.

For example, I used Kotlin Multiplatform from Jetbrains personally and also use it in my company, therefore I can suggest the best usecase for it when asked to recommend, not just because company X or person Y says it's awesome, because they always hype everything, same way they were hyping out React Native but when you actually implement it for big projects, you'd find that the performance was problematic. We wanted to also use Compose earlier this year in my company and after going through the drawbacks, we decided it was not yet time.

My point is, it needs a lot of improvement. It is not yet as awesome as Google engineers make it seem. At least not yet.

If you really want to get proper feedback of Developers regarding a tool, ask on @AndroidDevs Reddit.

Yes, I get your point. It's true. "It needs a lot of improvement".

Let's connect. If you don't mind if I send a dm

EbenG:


Yes, I get your point. It's true. "It needs a lot of improvement".

Let's connect. If you don't mind if I send a dm

Sure, I sent you a DM.

tosinhtml:


Sure, I sent you a DM.

.
Thanks. Replied

Kotlin is the new son of Google for Android development and it is ready to stay and evolving for years

qtguru:


The likes of Sheriman and AlphaByte will motivate me, or I can hire interns to build the projects. but Mobile dev is lucrative today.

Boss, I really need help. I have a good PC and internet connection but I just don't know what's wrong. I'm unable to learn something.

I will consider myself good with computers (If I can put much interest I solely believe I'll be very good at it) but I just cant seem to learn a tech skill and I really need to because I believe my future is something related to that.

First I started with HTML and CSS and then to JS but slowly I was getting uninterested, (The goal was blockchain development though.)

Although I'm still an undergraduate managing school with trying to learn this tech skills but
Now I wish to start afresh I was thinking of going straight to python then maybe if I become good with it then dive into cyber security or any field related to that. What do you think Sir? word of advice, criticism or anything will be appreciated based on your level of experience.

Thanks in anticipation Sir

The Cyber Express is a cyber security news media company that focuses on providing the latest news and information about various topics in the field of cybersecurity. With an emphasis on breaking news and real-time updates, they aim to keep the public informed about the latest developments in cybersecurity. The topics they cover a range from the latest cyber-attacks and data breaches to the use of ransomware and hacking tools, as well as information about the latest cybersecurity tools and technologies. By providing in-depth coverage of the cybersecurity industry, The Cyber Express serves as a valuable resource for individuals and organizations interested in staying informed about the latest threats and trends in the world of cybersecurity.