Frequently Asked Questions¶
Why do we need another architecture?¶
We ask this question too! So we wrote a longer answer for it: “Why Workflow?”.
How do I get involved and/or contribute?¶
- Workflow is open source!
- See our CONTRIBUTING doc to get started.
- Stay tuned! We’re considering hosting a public Slack channel for open source contributors.
Isn’t this basically React/Elm?¶
||State is called
||Elm applications have a
||Since workflows are not tied to any particular UI view layer, they can have an arbitrary rendering type. The
|Injected Dependencies||React allows parent components to pass “props” down to their children.||N/A||In Swift,
|Event Handling||DOM event listeners are hooked up to functions on the
How is this different than MvRx?¶
Besides being very Android and Rx specific, MvRx solves view modeling problems only per screen. Workflow was mainly inspired by the need to manage and compose navigation in apps with dozens or hundreds of screens.
This seems clever. Can I stick with a traditional development approach?¶
Of course! Workflow was designed to make complex application architecture predictable and safe for large development teams. We’re confident that it brings benefits even to smaller projects, but there is never only one right way to build software. We recommend to follow good practices and use an architecture that makes sense for your project.