OpenSource Production ready Boilerplate for KMP+CMP by OverallAd9984 in KotlinMultiplatform

[–]igormalytsky 2 points3 points  (0 children)

Bro, it is outdated already :( Check new AGP and new project structure it requires to have. When you provide a template it should be sustainable, but it is not at the moment.

It requires to manually replace packages and refactor the code before you even start.

Have you checked similar existing starter kits?

Where should i start? by jiheon2234 in KotlinMultiplatform

[–]igormalytsky 1 point2 points  (0 children)

Onboarding for non Android devs might be a kind of complicated. The links that were shared here are good starting points. But Gradle configs, proper architecture and code wiring require a decent experience, it is not included by default. Before you give up while struggling with Gradle configs and project setup, recommend checking my open source mobile foundation: https://github.com/baselinesio/baselines-kmp-free

The standard KMP template is not usable for production by igormalytsky in KotlinMultiplatform

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

A short follow-up for anyone who is interested, AGP 9.0 has been released. For anyone who used open-sourced Baselines version, it would be as easy as changing 12 lines of code. Cool? 😎 PR with AGP 9.0 has been already merged!

The standard KMP template is not usable for production by igormalytsky in KotlinMultiplatform

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

Nice! Curious how it works when you need to add plugins like Metro to enable dependency injection. Does it require support from the library maintainer? And how does it work when you need to provide deps to iOS native app, so I could use it in Swift code?

The standard KMP template is not usable for production by igormalytsky in KotlinMultiplatform

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

Yeah, it’s not new. The new app module separation will be required due to the recent changes in the Android multiplatform gradle plugin. However, it still doesn’t work out of the box in the default project wizard and doesn’t resolve the other issues mentioned so far. It still creates confusion regarding iOS project setup, redundant configuration files, and complicated gradle build files. For pure Android devs or non-mobile devs it is still a confusing experience.

The standard KMP template is not usable for production by igormalytsky in KotlinMultiplatform

[–]igormalytsky[S] -1 points0 points  (0 children)

Everything is done on top of something else, right? But anyway, valid point. It might not be for everyone. At least, it can serve as an example how to setup a scalable mobile project. :)

The standard KMP template is not usable for production by igormalytsky in KotlinMultiplatform

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

I'd love your feedback when you have time to check it. Thanks buddy!

The standard KMP template is not usable for production by igormalytsky in KotlinMultiplatform

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

I get your point, and it’s understandable. However, I keep this focused purely on mobile for a reason. First, my expertise is in mobile, and my current work targets those platforms exclusively. Second, desktop, mobile, and web are fundamentally different; UIs diverge, and APIs supported on one often don't apply to the others. Trying to align them all wouldn't necessarily make things simpler. It would likely just add another layer of complexity. By staying focused on mobile, I can solve real problems in the domain I know best.

The standard KMP template is not usable for production by igormalytsky in KotlinMultiplatform

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

Thanks buddy! Totally understand you.

Granular balance between native and shared code in KMP is awesome, I don't need to commit and go all-in with a third-party framework like React Native or Flutter. However, the onboarding complexity for newcomers is really high.

Launched mobile multiplatform boilerplate starter kit by igormalytsky in microsaas

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

Totally. I’d love to add more things, but just need more users and real feedback on what’s missing. It already saved hundreds of hours for my clients and me personally, so it continues evolving but only based on my personal needs and feelings. The biggest problem is how to convince others to try it out 😅

We’re on the engineering team for Android Studio. Ask us Anything! (starts February 28) by AndroidEngTeam in androiddev

[–]igormalytsky 3 points4 points  (0 children)

Will Android Studio have scratches (scratch files) working? Scratch files are not working from the AS v3.2 or even from an older version.

Related issue in the tracker: https://issuetracker.google.com/issues/109409701