just stumbled onto how vesper uses ballast to handle their kotlin multiplatform architecture. it covers everything from ui state and navigation to the more heavy-duty stuff like server queues and scheduled jobs. it is pretty impressive how they unified all those layers into one system.
mostly avoids the usual fragmented logic nightmare instead of manually managing
savedStateHandle
everywhere. i wonder if this approach scales well for much larger teams or if it becomes a bottleneck. anyone else using ballast for
cross-platform state management yet?
https://hackernoon.com/how-ballast-powers-vespers-kotlin-multiplatform-architecture?source=rss