lucaquerella

3 ms·

1. 1.▲
   by lucaquerella 10y ago

   It's quite long to explain it here, why don't you take a look at the Node.swift source code, if you have trouble understanding a specific part I'll be happy to help you.
2. 2.▲
   by lucaquerella 10y ago

   It's Void. In that example there is no need for the action to have a payload.
3. 3.▲
   by lucaquerella 10y ago

   I don't blame you for being skeptical. The main advantages we've noticed using this pattern are: 1) every time there is a crash or a problem we can look at the the state and the actions that lead to that situation. This improved o
4. 4.▲
   by lucaquerella 10y ago

   It may be an overkill for super simple apps with just few views. But it works great with a larger codebase, at least for us. We have apps built with it with hundreds of views and it works great, it has halved our development time and helped
5. 5.▲
   by lucaquerella 10y ago

   Yes, absolutely. You can use it to implement a single view or the entire app. Just render a NodeDescription in an existing UIView. EDIT: https://gist.github.com/lucaquerella/74d8bbb5855f26249a27b4a...
6. 6.▲
   by lucaquerella 10y ago

   I'm one of the author of the framework :) please let me know if you like our approach to apps development we internally use it for creating our own apps at Bending Spoons ( http://bendingspoons.com )
7. 7.▲
   Katana: React and Redux in Swift(github.com)

   20 points by lucaquerella 10y ago|0 comments