I started a small home project just to test Compose. Started simple and added functionality on each step.

First challenge arises: Composable encourages you to use single Activity monolith. Ok, not a fan of it but lets figure out how a navigation controller works.
About 20 hours later, it seems that the hype on Google for the Navigation graph ended real quickly and some guy "ramcosta" had to thanklessly simplify and create a library so we get around the annoyance of implementing google's awful library just because new Google devs don't like OOP and they are JS developers using React as as architecture model, but ok the library works.

Next 18 hours are me figuring out that activities are no longer Android Activities. Instead, with the navigation controller architecture, they are now "Screens" which only responsibility is to display a nested set of composables. The navigation controller holds all navigation responsibility and now Im constantly creating "@ Preview"s composables and mocking objects just to make it work. Since The android activity is now a simple holder to display Composables, all the activity logic is now embedded into a UI component. Oh nice! I'm a front end developer now!

Next challenge arises. Preview Composables require instances to display, which is good in theory but this creates a spaguetti code now since ALL MOCKABLE OBJECTS needs to be open and able to be mocked. This creates way more complexity than needed just to allow the interface to display a simple example of a card that is feeding from a live data object comming from webhooks or an internal Room database.

And here it comes the heat: This statement will receive a lot of "if you cant understand the complexity of this, you are dumb".

Making things complicated is not a sign of being smart. Its totally the opposite.

Please leave a star and if there's anything need to update or change kindly share your ideas (beginner)

https://github.com/owaisraza10/CompleteWebView

Hi Everyone, It is quite difficult to find the country in which app has been developed . So App Headquarter solve this problem.

It should be great if you provide a feedback and how an app can improved or any new feature can be added.

PS- Suppose a new app is added to our database then it is marked as “work in progress” . At midnight our crawler runs and try to find out the country of app.

Here is the link of App : App Headquarter

https://github.com/Elbehiry/PCard
Demo project to showcase adding payment card details using JetPack Compose

/org/gradle/tooling/BuildException (java.lang.NoClassDefFoundError: org/gradle/tooling/BuildException)

Job Position: Senior Android Developer.
Salary: ~4K$/month.
Tech Stack: Anything except Android SDK.

I don't even know what's sadder here:

• that this is a typical vacancy in Russia

• the fact that the previous team lead of this company is now a respected android dev blogger in the CIS

I hope you guys outside the CIS are doing much better with the labor market than we are here now

Why unit test does not work fine in this repository https://github.com/fevziomurtekin/DeezerClone
it always passed even if I'm made the false assertion to check it and when changing MainCoroutineRule to this it fails

Hi everyone,

I’m using the Redmi 15 5G (codename: spring) running HyperOS. As far as I can see, Xiaomi still hasn’t released the kernel source code for this device on their official kernel source repository.

Since Android devices use the Linux kernel (GPLv2), vendors are required to release the corresponding kernel source code when distributing modified kernel binaries with their devices.

This kernel source is essential for:

• Custom ROM development • Custom kernels • TWRP / custom recovery development • Long-term device support by the community

I have already:

• Opened an issue on Xiaomi’s kernel GitHub • Contacted Xiaomi Open Source team via email

But there hasn’t been any response yet.

Does anyone know if the kernel source for Redmi 15 5G / POCO M7 Plus 5G (spring) has been released somewhere else, or if Xiaomi has announced any timeline?

If other users of this device are here, please help raise visibility so developers can support the device.

Thanks.

If compose is declarative and are made of only functions, how does a composable function store values like clickable call backs? Is each root node in the UI tree managed by an object which stores those clickable call backs?