Petr Šíma: Principy funkcionálně reaktivního programovaní na mobilních platformách
•
0 likes•1,136 views
The document discusses functional reactive programming (FRP). It begins by explaining the differences between imperative programming using mutable state and functional programming using immutable values and pure functions. It then defines FRP as combining functional programming techniques like map, filter and reduce with implicit handling of asynchronous data over time. The rest of the document provides examples of FRP libraries for different platforms like RxJava for Android and RxSwift for iOS, and discusses related concepts like hot and cold signals, disposables and reactive app architecture patterns.
More Related Content
Viewers also liked
Similar to Petr Šíma: Principy funkcionálně reaktivního programovaní na mobilních platformách
Similar to Petr Šíma: Principy funkcionálně reaktivního programovaní na mobilních platformách (20)
More from mdevtalk
More from mdevtalk (20)
Petr Šíma: Principy funkcionálně reaktivního programovaní na mobilních platformách
- 2. PETR SIMA Senior iOS Developer, Ackee
- 4. It's functional. It's reactive. You want to start using it today. Functional reactive programming 4
- 5. 1.5 years of experience with FRP both iOS and Android more to come at future mDevTalks FRP at Ackee 5
- 7. map, reduce, filter, flatMap If a pure function is called with the same arguments, the same result will be returned. declarative, "Pull-based", eliminates side effects, avoids changing-state and mutable data Functional programming 7
- 8. = reactive programming (asynchronous dataflow programming) using the building blocks of functional programming (e.g. map, reduce, filter) If a pure function is called with the same arguments, the same result will be returned. implicit parameter - time FRP 8
- 9. Demo 9
- 10. composable, reusable unidirectional dataflow easy to reason about code More buzzwords ab ab 10
- 11. composable, reusable unidirectional dataflow easy to reason about code More buzzwords Input ---> ---> Output 11
- 12. composable, reusable unidirectional dataflow easy to reason about code More buzzwords 12
- 13. composable, reusable unidirectional dataflow easy to reason about code More buzzwords Input ---> ---> Output 13
- 14. composable, reusable unidirectional dataflow easy to reason about code More buzzwords Input ---> ---> Output 14
- 15. Railway oriented programming Error handling 15
- 16. Reactive code consists of elementary operations. Don't be "too dry". DRY principle? 16
- 17. Android RxJava Where to start? iOS RxSwift Reactive Cocoa 17
- 18. 18
- 19. 19
- 20. Android RxJava Where to start? iOS RxSwift Reactive Cocoa Window Rx.N 20
- 21. Android RxJava Where to start? iOS RxSwift Reactive Cocoa Windows Phone Rx.NET (RxExtensions) 21
- 22. Architecture of a reactive application ... ... ab ab 22
- 23. Architecture of a reactive application Massive View Controller MVP MVVM 23
- 24. Architecture of a reactive application MVC Model View Presenter MVVM 24
- 25. Architecture of a reactive application MVC MVP Model View ViewModel 25
- 26. Demo 26
- 27. RxSwift, RxJava, ... Observable Hot and cold signals Reactive Cocoa Signal SignalProducer 27
- 28. A hot signal is active regardless of observers. "Signals are streams that are already in progress, e.g. notifications, user input, etc." A cold signal starts work when subscribed to. "Cold signals represent operations or tasks, e.g. network requests." Cold signals are lazy. Hot and cold signals 28
- 29. Signals are hot. SignalProducers are cold. SignalProducer.start() creates a Signal. Hot and cold signals 29
- 30. a mechanism for memory management and cancellation disposable.dispose() interrupts a signal usually don't have to be used directly in Reactive Cocoa Disposables 30