Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Question] Future of Flow #271

Closed
arazabishov opened this issue Oct 14, 2017 · 3 comments
Closed

[Question] Future of Flow #271

arazabishov opened this issue Oct 14, 2017 · 3 comments

Comments

@arazabishov
Copy link

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?

@rjrjr
Copy link
Collaborator

rjrjr commented Oct 15, 2017

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.

@rjrjr rjrjr closed this as completed Oct 15, 2017
@arazabishov
Copy link
Author

@rjrjr Thanks a bunch for the link, will waiting for the recording of the talk.

@BraisGabin
Copy link

If someone else arrives here. This is the video: https://www.youtube.com/watch?v=KjoMnsc2lPo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants