Hi folks! Here is a quick question that will help ...

# multiplatform

[akapanina]

Hi folks! Here is a quick question that will help us make Multiplatform better 🙂

Do you use jvm target in your Multiplatform projects? And, if yes, what is it for?
1️⃣ - Yes, for backend
2️⃣ - Yes, for desktop
3️⃣ - Yes, for other purposes
🚫 - Don’t have jvm target in any of my projects

[Kris Wong]

I use JVM for Android

[akapanina]

Why not Android target, btw?

[Sam]

I use jvm for running unit tests.

[Kris Wong]

1. because the new project templates don't include an Android target, and 2. because the android target has additional overhead with less compatiblity.

[Kris Wong]

but that's not to say that I don't use an Android target if I need the Android SDK or resource system

[kpgalligan]

Yeah, similar. We tend to use android target for mobile projects, but have used just jvm in the past and sometimes on library work. It’s possible we’d just use JVM for a project that was more logic than mobile specific. We’d certainly explore that if optimizing build times and complexity.

[louiscad]

I use jvm in library modules that don't need Android APIs, nor Android resources, nor built-in debug/release build type awareness.

[louiscad]

I see no reason to limit code to Android only when you don't use Android APIs/features specifically.

[ribesg]

We have a project with modules for each of our services’ models which are used by backend and mobile frontends (and hopefully in the future in JS frontends) as well as http clients for each service (basically models + ktor clients + endpoints), also used by both backend and mobile frontends (Android & iOS)