Ballast Roadmap

The core Ballast functionality is now stable since 1.0.0 and will be maintained through Semantic Versioning and enforced with Kotlin Binary Compatibility Validator. The API of additional features will also be maintained, but there's still a lot of functionality that could be added.

The following are some ideas of what could be done with Ballast and its Interceptor API, though nothing on this list is an actual hard commitment to being developed. If you see an idea on this like you want, by all means, go build it yourself! I will gladly accept any contribution as a PR, or if you would rather develop the feature in a separate repo I will happily link to that repo from the Ballast documentation.

• Finite State Machine DSL: Ballast is basically an FSM already, and it would be nice to build a dedicated DSL like Tinder/StateMachine on top of Ballast so it could be used on any Kotlin target
• Refactor Repository module: The Repository Module has some good ideas about how to use the MVI for managing the repository an other layers of your application, extending the MVI pattern beyond just the UI. But the current implementation needs to be refined and streamlined.
• Pluggable Event-handling strategies (at most once, at least once, exactly once, atomic, etc.)