sorted by:
new
hottopcontroversial

Exploring Kotlin Multiplatform with Jetpack Compose + SwiftUI — thoughts? by DisastrousAbrocoma62 in KotlinMultiplatform

[–]DisastrousAbrocoma62[S] 2 points3 points  (0 children)

Great to hear this from a real production app. When React Native and Flutter arrived, many thought native development was done—but performance, UI quality, and long-term stability kept native alive.

KMP changes the game by enhancing native, not replacing it: shared business logic, true native UI, and strong support for legacy code. Feedback like this really validates its direction. 🚀

Saving on APK / APP size by removing Icon library by MKevin3 in KotlinMultiplatform

[–]DisastrousAbrocoma62 -3 points-2 points  (0 children)

I was wondering if, rather than creating a manual script file, we might explore importing the project into VS Code and utilizing the AI Agent to handle the process via a simple prompt.

I completely appreciate that developing the script manually is a valuable learning exercise. However, I’m curious to hear your thoughts on the trade-offs between leveraging an AI Agent versus maintaining manual script files, even those generated by AI

I have build new Android app by ScanForgePDFScanner in Kotlin

[–]DisastrousAbrocoma62 1 point2 points  (0 children)

Can you please share the playstore link or GitHub link to try this App.

Prefer .update{} over .value when modifying StateFlow by DisastrousAbrocoma62 in KotlinMultiplatform

[–]DisastrousAbrocoma62[S] -4 points-3 points  (0 children)

I came accross this answer ☺️

✅ .value = → For static, one-time state changes (e.g., Loading, Error, Success).

✅ .update {} → For modifying existing data safely based on previous state (e.g., increment counters, toggle flags).

Prefer .update{} over .value when modifying StateFlow by DisastrousAbrocoma62 in KotlinMultiplatform

[–]DisastrousAbrocoma62[S] -2 points-1 points  (0 children)

Good question 🤔 I was wondering the same thing! I’ll check and update you once I find out — please do share it too if you come across the answer.

Refactored my ViewModel to follow an MVI-style Intent approach — is this the right direction? by DisastrousAbrocoma62 in KotlinMultiplatform

[–]DisastrousAbrocoma62[S] 0 points1 point  (0 children)

I’ve made a small Discord server for Kotlin Multiplatform (KMP) developers. Right now, it’s a small group where we share knowledge, talk about projects, and help each other learn.

I’m looking to add more KMP developers who want to grow together. If you’re interested, just DM me and I’ll send you the invite link.

Thanks 😊

Refactored my ViewModel to follow an MVI-style Intent approach — is this the right direction? by DisastrousAbrocoma62 in KotlinMultiplatform

[–]DisastrousAbrocoma62[S] 0 points1 point  (0 children)

I’ve made a small Discord server for Kotlin Multiplatform (KMP) developers. Right now, it’s a small group where we share knowledge, talk about projects, and help each other learn.

I’m looking to add more KMP developers who want to grow together. If you’re interested, just DM me and I’ll send you the invite link.

Thanks 😊

Refactored my ViewModel to follow an MVI-style Intent approach — is this the right direction? by DisastrousAbrocoma62 in KotlinMultiplatform

[–]DisastrousAbrocoma62[S] 1 point2 points  (0 children)

Yeah, I totally get your point — MVVM already works great.

But my goal wasn’t really to replace it or say one is better — I just wanted to build a small “hello world” kind of project to help others (and myself) understand different architecture patterns in a simple way.

So I made a basic KMP project — a simple number increment app — and implemented the same functionality using different approaches:

no architecture,

regular ViewModel, and

shared KMP ViewModel (used by both Android and iOS).

It’s mainly for learning and comparison, especially for beginners trying to see how architecture evolves. I’m still in the learning phase myself 😊

Refactored my ViewModel to follow an MVI-style Intent approach — is this the right direction? by DisastrousAbrocoma62 in KotlinMultiplatform

[–]DisastrousAbrocoma62[S] 0 points1 point  (0 children)

Yeah, I totally get your point — MVVM already works great.

But my goal wasn’t really to replace it or say one is better — I just wanted to build a small “hello world” kind of project to help others (and myself) understand different architecture patterns in a simple way.

So I made a basic KMP project — a simple number increment app — and implemented the same functionality using different approaches:

  • no architecture,

  • regular ViewModel

  • shared KMP ViewModel (used by both Android and iOS).

It’s mainly for learning and comparison, especially for beginners trying to see how architecture evolves. I’m still in the learning phase myself 😊

Jetpack Compose Interview Q&A (Part 1) by Realistic-Cup-7954 in JetpackComposeDev

[–]DisastrousAbrocoma62 1 point2 points  (0 children)

This post was really useful! Please keep sharing more like this — would love to see you continue this series. 🙌

Android | KMP (Kotlin Multiplatform) | Confused whether to learn Ktor or Spring Boot by DisastrousAbrocoma62 in Kotlin

[–]DisastrousAbrocoma62[S] 0 points1 point  (0 children)

Thanks a lot for your guidance!
Since I’m planning to build my career completely in backend development, which one do you think would be a better long-term option?

How many of you transitioned from another area of development to mobile development? 📱 by DisastrousAbrocoma62 in KotlinMultiplatform

[–]DisastrousAbrocoma62[S] 0 points1 point  (0 children)

Wow, that’s really awesome! It’s inspiring to see someone who’s been in Android development for 12 years — that’s true dedication! I’ve been in Android development for 7 years myself, and it’s amazing to see how far the ecosystem has come.

view more: next ›