"No sense" in the context of the function we wanted to achieve. Perhaps it was worded a bit too harshly.

If you take a look into the implementation of flowInLifecycle, you will see that is uses repeatOnLifecycle under the hood. For the use-case we had in the article, the extension function flowWithLifecycle, which is based on Flow, was just more handy to use.

If you don't want to use it, you can stick to repeatOnLifecycle and adapt the shown code snippets to your needs. The outcome will be the same.