Personally I don't feel the need to use React if you use kotlin. But there are few cases where React makes sense. Everything that involves a stream of events th

Personally I don't feel the need to use React if you use kotlin. But there are few cases where React makes sense. Everything that involves a stream of events that you need to process and they can fail or you need to retry, them React is your way to go (I don't feel kotlin is ready for this use case yet). For example, if you want to use the BlueTooth API it is so easy to use it with React because of the stream of events. People are using React for Rest requests, and for APIs where you cannot touch them it can be a good idea as it provide ways to join results of requests and other stuff. But if you control the API and it is designed to be simple and with mobile in mind, there shouldn't be uses cases where a simple request give you all you need. It also gives consistency as you treat the same way a click event than a http request. Some people like this but I don't. I personally didn't find a good use case to use it in my app, but you might think diferently. So, I suggest you to try it a little at least an decide by yourself.