The document discusses PicCollage's journey to adopting reactive programming in their Android applications. It outlines why reactive programming is important, how PicCollage struggled with threading issues originally, and the steps they took to transition to reactive programming. This included first making UI interactions reactive, then implementing reactive threading mechanisms, making their data layer APIs reactive, and finally making controllers reactive as well. The document provides references and recommendations for learning reactive programming.

1. 導入反應式編程的⼼心路路歷程
Android Developer - PicCollage
Prada
Why reactive programing matter, and how PicCollage adaptive it.

2. Why Reactive
Programming matters?
https://www.youtube.com/watch?v=v68ppDlvHqs
1. Deal with Threading right is matters
2. Architecture also need to be reactive.

3. Old World

4. You Code shouldn’t like this

6. Our World is shifting
Blocking -> Non-Blocking
Computer -> User

7. Developer suffering
from Threading

8. I was join PicCollage in 2013
we have over 30 Customized AsyncTask Classes

9. Deferred-Promise Pattern
is Popular
we tried jDeferred and Bolts-Framework
https://github.com/jdeferred/jdeferred
https://github.com/BoltsFramework

10. We went to Android SF
Meetup in 2016
https://tech.pic-collage.com/android-meetup-in-san-fransisco-e1e8dde1554c

11. Implement thread in
RxJava
https://tech.pic-collage.com/android-meetup-in-san-fransisco-e1e8dde1554c

12. https://youtu.be/XLH2v9deew0?t=4m51s
Asynchronous Ideas
1. Explicit execution
2. Easy thread management
3. Easily transformable
4. As few side effect as possible
5. Cancelation

13. Architecture also need
to be reactive

14. Trending : Make Model/
State be reactive

15. Google try to move to
MVVM pattern
https://developer.android.com/topic/libraries/data-binding/index.html

16. Android Architecture
Component
https://developer.android.com/topic/libraries/architecture/index.html

17. Trending : isolated Android
framework dependency

18. Android Dev Hates
Activity/Fragment LifeCycle

19. Your Code might looks like
MyActivity.java
Takes View’s Input
Update Views
Control Logic
Data/Model
MVC⼀一家親

20. Your Code might looks like
MyActivity.java
Takes View’s Input
Update Views
Control Logic
VC⼀一家親
MyContentProvider.java
Data/Model

21. Model-View-Presenter
MyActivity.java
Takes View’s Input
Update Views
MyContentProvider.java
Data
MyPresenter.java
Control Logic
IView.java IPresenter.java

22. Trending : Controller
need to be reactive

23. You might want your
controller looks like

24. In the end, Your code will be
https://www.youtube.com/watch?v=0IKHxjkgop4

25. Adoption steps from
PicCollage
1. UI interaction
2. Threading mechanism
3. Make Data Layer API be reactive
4. Make Controller be reactive

26. UI interaction
https://github.com/JakeWharton/RxBinding

27. Threading mechanism
Before
After

28. Data Layer API be reactive
Note : some case you need to use Subject to achieve this goal
https://github.com/ReactiveX/RxJava/wiki/Subject

29. Controller be reactive

30. Take away
1. Learn from web developers(Flux, Redux, MVI)
2. Review your threading code
3. Reactive Programming has high learning curve
4. Follow our adoption steps

31. Thanks, Question?

32. Reference
Intro to RxJava/ Christina Lee
https://www.youtube.com/watch?v=XLH2v9deew0
Dynamics of change: why reactivity matters/ Andre Staltz
https://www.youtube.com/watch?v=v68ppDlvHqs
Managing State with RxJava/ Jake Wharton
https://www.youtube.com/watch?v=0IKHxjkgop4