A modern programming language that makes developers happier.

kotlinlang

hey all, i'm curious, given some in this group have been using Orbit for a while now, if you have any established guidelines in your respective places of work of how you use it; for example, for me a couple of principles that come to mind is:
• the only public functions in a view model would be intent blocks
• don't nest intents
... there are more, i don't want to skew what anyone writes though, lol. also fascinated about how those guidelines have changed with time, for instance what impact migrating to compose has had - what gotchas were there, and went better than expected

Hello <@U9D52BJF2>!
At my company we are using it for the first time in a production project along side with full compose and <https://composedestinations.rafaelcosta.xyz/|compose-destinations>.
So far everything is smooth, nothing to complain. Regarding your principles, at least those two we’re following too.

I don’t have any “guidelines” when using MVI+Orbit because this is the first project so by it’s end we’ll review everything and probably create those guidelines.

I can share some pieces of code too and base classes if you are interested. Send me a pvt :wink:

You know I was going to ask this but: it would be great if I could use it too in KMM :eyes: :stuck_out_tongue_winking_eye:. What’s the status of the gradle-plugin or is not a priority?

btw: <https://github.com/rickclephas/KMM-ViewModel>