undefined | Better HN

0 pointsIshKebab1y ago0 comments

I've never done any iOS dev but I always assumed it was partly because the Android GUI toolkit (views, fragments etc.) is just SO awful that it just isn't feasible to make nice UIs. Certainly in the apps I've made there's absolutely no way I would invest time into animations, custom widgets, etc.

Hopefully Flutter will fix that because the difference in usability is night and day. It's just a shame the Dart ecosystem is so dead.

0 comments

kernal1y ago

Your concept of Android development looks to be stuck in the 4.4 days. Jetpack Compose and its declarative UI is how modern Android apps are developed.

https://github.com/android/compose-samples

>Hopefully Flutter will fix that because the difference in usability is night and day. It's just a shame the Dart ecosystem is so dead.

I don't see how the difference is night and day when they both use declarative UI's. Whether you use Jetpack Compose/Kotlin or Flutter/Dart is really up to your objectives. As for your claim that the Dart ecosystem is dead - I really don't get that, since Flutter/Dart is the #1 cross-platform development environment.

IshKebabOP1y ago

> Jetpack Compose and its declarative UI is how modern Android apps are developed.

[citation needed]. I looked into Jetpack Compose a year or two ago and it was way too immature then to use in production. I guess maybe that's improved a bit but we're talking about existing apps here. They don't magically move to Jetpack Compose. Someone has to update them. How much would you bet that MotionCam Pro uses Jetpack Compose?

kernal1y ago

>Jetpack Compose is Android’s recommended modern toolkit for building native UI. It simplifies and accelerates UI development on Android. Quickly bring your app to life with less code, powerful tools, and intuitive Kotlin APIs.

https://developer.android.com/develop/ui/compose

Calling Jetpack Compose immature is amusing considering all of the apps that have been built with it. Additionally, it's been one of the primary pillars of Google I/O for the past 5 years.

>I guess maybe that's improved a bit but we're talking about existing apps here. They don't magically move to Jetpack Compose.

You don't need to. With Jetpack Compose there's no need to completely rewrite your entire UI. If you want to convert an old UI to Jetpack Compose you can gradually update parts of it and have both co-exist.

>How much would you bet that MotionCam Pro uses Jetpack Compose?

Judging from the UI I don't see any Jetpack Compose UI elements.

j / k navigate · click thread line to collapse

0 comments

kernal1y ago

Your concept of Android development looks to be stuck in the 4.4 days. Jetpack Compose and its declarative UI is how modern Android apps are developed.

https://github.com/android/compose-samples

>Hopefully Flutter will fix that because the difference in usability is night and day. It's just a shame the Dart ecosystem is so dead.

IshKebabOP1y ago

> Jetpack Compose and its declarative UI is how modern Android apps are developed.

kernal1y ago

https://developer.android.com/develop/ui/compose

Calling Jetpack Compose immature is amusing considering all of the apps that have been built with it. Additionally, it's been one of the primary pillars of Google I/O for the past 5 years.

>I guess maybe that's improved a bit but we're talking about existing apps here. They don't magically move to Jetpack Compose.

>How much would you bet that MotionCam Pro uses Jetpack Compose?

Judging from the UI I don't see any Jetpack Compose UI elements.

j / k navigate · click thread line to collapse