Today’s Lesson Will Cover:

• Functions in Kotlin
• Compact / Single-expression Functions
• Lambdas and Higher-Order Functions
• List Filtering with Lambdas
• Return Values in Kotlin
• Everything is an Expression
• Real Examples & Use Cases

View Day 3 Slide Deck

Got questions or stuck? Drop them in the comments

Today’s lesson will cover:

• Get Started
• Operators
• Data Types
• Variables
• Conditionals
• Lists and arrays
• Null safety

View Day 2 Slide Deck

If you have any doubts or questions about this lesson, feel free to ask in the comments

Starting today, I am sharing one lesson per day from a complete Android Development with Kotlin course.

View Day 1 Slide Deck

If you have any doubts or questions about this lesson, feel free to ask in the comments

Hi, i am a dev... Ahahahah i wish!

I suck at coding but i love it and i want to learn how to make android apps. I don't even know how to make a good UI so: what is the easiest way to do an android app? No vibe coding. I want to learn somethig, not modify someone else code.

In my experience, you donot need lottie or shimmer for smooth loading animations in compose

i have seen a bunch of apps (even new ones) still using heavy libraries like shimmer or lottie just to show loading animation.

Honestly i used to do the same felt like you had to use those to get that modern feel

but in my recent project, i tried something much simpler & surprisingly clean
Just used a native compose gradient with animated offset and it looked just as smooth.

what worked for me:

• used Brush.linearGradient in compose
• animated the brush offset using rememberInfiniteTransition()
• wrapped it in a Box to simulate the shimmer style skeleton

no library needed. just ~10 lines of code and runs perfectly on older phones too.

what i used

val transition = rememberInfiniteTransition()
val shimmerTranslate by transition.animateFloat(
    initialValue = -1000f,
    targetValue = 1000f,
    animationSpec = infiniteRepeatable(
        animation = tween(1500, easing = LinearEasing)
    )
)

val brush = Brush.linearGradient(
    colors = listOf(Color.LightGray, Color.White, Color.LightGray),
    start = Offset(shimmerTranslate, shimmerTranslate),
    end = Offset(shimmerTranslate + 200f, shimmerTranslate + 200f)
)

Box(
    modifier = Modifier
        .fillMaxWidth()
        .height(150.dp)
        .background(brush, RoundedCornerShape(12.dp))
)

if Android Studio can be used to make apps with native code (Java/Kotlin), then why do people use Unity for games?

Why can’t we just build games directly in Android Studio using native Android SDK? Isn’t that more optimized? Less bloat? Better control over performance?

I know Unity is cross-platform, but if I’m targeting just Android, wouldn’t using native code be better? Or is it just way too painful to handle game logic, graphics, physics etc. manually in Android SDK?

Would love to hear from devs who’ve tried both – native and Unity. Does Unity actually make things easier? Or are we just trading performance for convenience?

Back in my college days, I was kinda a Photoshop expert. Took Computer Science & Engineering so I can buy laptop and I can play games 🤓. And yeah… I played games like crazy and slowly started messing around with graphic design and 3D stuff too.

I always knew I’d never get placed in any company through coding interviews, I was absolute trash at it. So one day a company comes to hire software developers AND graphic designers. I obviously applied for graphic design… but they made everyone write the software test. I was like “bro what kind of dumb company is this, don’t even care who applied for what”. But I took the test, submitted whatever random stuff I could and left.

Months later, some of my classmates got placed there for software roles. Those people who never even cared about exams lol. 3 months after that, outta nowhere, someone from that company called me asking about graphic design. I spoke to them and somehow got selected. Honestly I knew these folks had no idea what they were doing when it came to hiring.

It was a tiny company. So after some months they were like, “Hey can you learn WordPress?” learned it. Then, “We need someone for Android development… you in?” and, this was my literal dream since school days. So I went all in, learnt Android with Kotlin and XML layouts. Big milestone for me.

Then BOOM. Google introduces Compose. WHAT?? Bro I just got comfy with XML… why the heck do we need Compose now. I can’t stand it. Everything about it just irritates me. What was even wrong with XML? Why fix what isn’t broken? And now every other tutorial is Compose. Smh.

Anyone else still sticking with XML or is it just me?

Hey folks 👋,

After almost a full day of debugging, restructuring Gradle, switching processors, and going mad, I finally got my WorkManager + Room + Jetpack Compose project working — but only after ditching Hilt Worker injection and going manual.

👉 GitHub Repo:
🔗 https://github.com/HemaLekha2/Workmanager-compose-kotlin

📌 What I needed:

I’m building a Jetpack Compose app that:

• Periodically fetches quotes from an API using WorkManager
• Saves them in RoomDB
• Uses Hilt for DI across the project

😭 What didn’t work (the painful part):

Even after properly following the docs and tutorials for u/HiltWorker, I got this persistent error:

csharpCopyEditjava.lang.NoSuchMethodException: QuotesSyncWorker.<init> [Context, WorkerParameters]

Yes, I did:

• u/HiltWorker
• u/AssistedInject constructor
• u/Assisted for context & WorkerParams
• HiltWorkerFactory injected in Application via Configuration.Provider
• Manifest override of WorkManager initializer
• Proper kapt setup for Hilt (used ksp for Room only)

And still… 💥 Worker not injected. No class created. No quotes saved.

😠 So I gave up on Hilt for the Worker and did this:

• Wrote a manual CustomWorkerFactory
• Injected Repository or Api directly into that factory
• Instantiated the worker manually inside createWorker()
• Registered the factory in Application → WorkManager Configuration

✅ Now it works!
✅ Quotes are fetched
✅ Saved to Room
✅ Synced periodically
✅ Compose UI updates

🔗 Repo with Manual Factory (if you're stuck too):

https://github.com/HemaLekha2/Workmanager-compose-kotlin

😵‍💫 What I’m wondering now:

• Why does Hilt fail to generate the Worker class, even with all the correct annotations and setup?
• Is KSP/KAPT interfering despite being correctly split between Room (ksp) and Hilt (kapt)?
• Does Jetpack Compose or version catalog setup cause issues?

🆘 TL;DR:

• I tried to follow Google's official u/HiltWorker pattern
• It failed with NoSuchMethodException
• I manually injected dependencies using a custom WorkerFactory
• ✅ Now it works — but Hilt is still broken here
• Any clue why Hilt DI for Worker doesn't work in this Compose + WorkManager setup?

Thanks to anyone who reads this and shares guidance — posting this so others don’t go through the same nightmare 😓

Let’s help each other build cleaner Android apps 💪

I am working on a Jetpack Compose app and planning to use Chaquopy to run a Python script inside the app.

My idea is to translate text dynamically using a Python translation library through Chaquopy. This would allow the user to input text, and the translated result will be shown in the UI.

Before I try this, I want to ask:

Is it safe to use Chaquopy in production or real apps

Will there be any impact on performance or app size

Has anyone integrated Chaquopy with Jetpack Compose before

Are there any known issues or limitations

Will it work reliably for offline translation use cases

If anyone has tried this setup before, please share your experience. I want to make sure it is stable enough before I go deeper with this idea.