this post was submitted on 15 May 2024
31 points (100.0% liked)

Android Development

539 readers
2 users here now

Welcome to the programming.dev Android development community!

The Android robot is reproduced or modified from work created and shared by Google and used according to terms described in the Creative Commons 3.0 Attribution License

founded 1 year ago
MODERATORS
erlingur@programming.dev
will@programming.dev
Ategon@programming.dev
31
Google Officially Supports Kotlin Multiplatform (android-developers.googleblog.com)
submitted 5 months ago by pro_grammer@programming.dev to c/android_dev@programming.dev
11 comments fedilink hide all child comments
top 11 comments
sorted by: hot top controversial new old
[–] DieguiTux8623@feddit.it 4 points 5 months ago* (last edited 5 months ago) (1 children)

I am starting to have mixed feelings about this. It feels like I either have chosen the wrong technology or there is something wrong with me.

Had to drop support to every other platform and only working on the commonMain and androidMain source sets (so what's the point of KMP after all?) and still the app is not on par with purely native counterparts (main pain points: navigation, l10n, image loading/rendering, video players, markdown rendering using Compose multiplatorm, resource access especially for typefaces, using mocks in tests, and the list could go on...).

Maybe Compose multiplatorm is the real culprit but God, have mercy on me please....

[–] DeprecatedCompatV2@programming.dev 2 points 5 months ago (1 children)

Uh-oh heretic spotted. Recant everything you've said or I'll make you justify every line of your manifest to a robot!

[–] DieguiTux8623@feddit.it 1 points 5 months ago (1 children)

I hoped to be burned alive like in the good ol' times.

[–] DeprecatedCompatV2@programming.dev 3 points 5 months ago* (last edited 5 months ago) (2 children)

I hereby sentence you to writing exception handling code in viewmodels with the following requirements:

  • exceptions may be native
  • exceptions must be defined in separate modules for Clean Architecture
  • all calls to native methods must use callbacks for Objective-C compatibility
  • you must launch a separate coroutine when rethrowing some (TBD) exceptions to prevent the exception from being caught by a parent other than the root exception handler (or the calling thread!)
  • you must use ViewModelScope except ~~when writing to SharedPreferences~~
  • you should be using DataStore, heathen
[–] DieguiTux8623@feddit.it 1 points 5 months ago (1 children)

That was painful even to read...

[–] SmartmanApps@programming.dev 3 points 5 months ago (1 children)

throw NotReadingThatException

[–] pop@lemmy.ml 3 points 5 months ago (2 children)

So this is why they dropped multiple flutter devs from the team. RIP Flutter!

[–] DeprecatedCompatV2@programming.dev 2 points 5 months ago

I see this as a positive for Flutter. Android tends to publicly execute its favorite libraries and ignore the ones that actually work properly.

[–] huginn@feddit.it 0 points 5 months ago

I called it in the layoff announcement and people said I was crazy