You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, thanks a bunch for the tremendous work you're guys doing to maintain your open source libraries 馃憤 I was looking into alternatives for Fragments, and apparently Flow seems to be one of the most popular OO choices.
The only concerning part is that project is not actively developed anymore. Do you still believe in design of Flow, or you think that there are better ways / solutions to the problem?
The text was updated successfully, but these errors were encountered:
We're still big believers in Flow and still use it in a lot of our apps. We've been slow to finish the polish for a 1.0 release due being stretched thing and having tiny, tiny little attention spans.
One caveat: for our largest app (nearly 300 individual screens), we're running into some scaling issues, and are changing how we use Flow (https://speakerdeck.com/rjrjr/reactive-workflows, video soon). That said, I still would have no hesitation at all using it for more sanely sized apps.
First of all, thanks a bunch for the tremendous work you're guys doing to maintain your open source libraries 馃憤 I was looking into alternatives for Fragments, and apparently Flow seems to be one of the most popular OO choices.
The only concerning part is that project is not actively developed anymore. Do you still believe in design of Flow, or you think that there are better ways / solutions to the problem?
The text was updated successfully, but these errors were encountered: