NYC Android meetup May 2019

How our architecture allows new joiners to start contributing since day one

Transcript

1. How our architecture allows new joiners to start contributing since day one @rmgoncalo
2. How our architecture allows new joiners to start contributing since day one
3. Presentation Domain Data
4. Presentation Domain Data Interactor Repository
5. Presentation Domain Data Interactor Repository
6. Presentation Domain Data Interactor Repository
7. Domain Interactor Repository
8. Domain Interactor Repository interface RetrieveInteractor<in Params, Data> : Interactor { fun retrieveBehaviorStream(params: Params): Observable<Data> } retrieveBehaviorStream(Params) : Observable<Data>
9. Domain Interactor Repository interface SendSingleInteractor<in Params, Result> : Interactor { fun sendSingle(params: Params): Single<Result> } sendSingle(Params) : Single<Result>
10. Domain Interactor Repository requestSingle(Params) : Single<Result> interface RequestSingleInteractor<in Params, Result> : Interactor { fun requestSingle(params: Params): Single<Result> }
11. Domain Interactor Repository sendCompletable(Params) : Completable interface SendCompletableInteractor<in Params> : Interactor { fun sendCompletable(params: Params): Completable }
12. Domain refreshCompletable(Params) : Completable … deleteSingle(Params) : Single<Result> Interactor Repository deleteCompletable(Params) : Completable
13. Presentation Domain Data Interactor Repository
14. Data Repository
15. Data Repository retrieveBehaviorStream(Params) : Observable<Data>
16. Data Repository Store retrieveBehaviorStream(Params) : Observable<Data>
17. Data Repository Store retrieveBehaviorStream(Params) : Observable<Data> ( Data )
18. Data Repository Store retrieveBehaviorStream(Params) : Observable<Data> ( Data ) ( Data )
19. Data Repository Store retrieveBehaviorStream(Params) : Observable<Data> ( ) ( )
20. Data Repository Store retrieveBehaviorStream(Params) : Observable<Data> ( ) ( ) fetchCompletable(Params) : Completable
21. Data Repository Store retrieveBehaviorStream(Params) : Observable<Data> ( ) ( Data ) ( ) fetchCompletable(Params) : Completable
22. Data Repository Store retrieveBehaviorStream(Params) : Observable<Data> ( ) ( ) ( Data ) fetchCompletable(Params) : Completable
23. Data Repository Store retrieveBehaviorStream(Params) : Observable<Data> ( Data ) ( Data ) ( Data )
24. Data Repository Reactive Store
25. Data Repository Reactive Store Memory
26. Data Repository Reactive Store Memory getSingularMaybe() : Maybe<Model>
27. Data Repository Reactive Store Memory putSingular(Model) getSingularMaybe() : Maybe<Model>
28. Data Repository Reactive Store
29. Data Repository Reactive Store getSingularBehaviorStream() : Observable<Option<Model>>
30. Data Repository Reactive Store storeSingular(Model): Completable getSingularBehaviorStream() : Observable<Option<Model>>
31. Presentation Domain Data Interactor Repository
32. Presentation Interactor
33. Presentation Interactor View Model
34. Presentation Interactor View Model Live Data
35. Presentation Interactor View Model Live Data
36. Presentation Interactor View Model Live Data
37. Presentation Interactor View Model Live Data
38. Real case: Pairing
39. What is pairing? Real case: Pairing
40. How do traditional banks usually handle authentication for money transfers?
41. 2FA method: Transaction Authentication Number (TAN) How do traditional banks usually handle authentication for money transfers?
42. How does N26 handle authentication for money transfers?
43. 2FA method: Pairing How does N26 handle authentication for money transfers?
44. 2FA method: Pairing How does N26 handle authentication for money transfers? - generates a pair of public/private keys - used to verify the request was done by the correct user (mobile device) - seamless experience
49. 2 states: Phone and Code
50. Presentation Domain Data interactor .retrieveBehaviorStream() .subscribe { post PhoneOrCode } repository .retrieveBehaviorStream() Observable<S> store .getBehaviorStream() Observable<Option<S>>
51. Presentation Domain Data interactor .retrieveBehaviorStream() .subscribe { post PhoneOrCode } repository .retrieveBehaviorStream() Observable<S> store .getBehaviorStream() Observable<Option<S>>
53. Presentation Domain Data interactor .refreshCompletable() .subscribe() retrieveBehaviorStream() .subscribe { post PhoneOrCode } repository .refreshCompletable() Observable<S> fetchSingle() .flatMapCompletable { store.put() } — store .getBehaviorStream() Observable<Option<S>>
54. Presentation Domain Data interactor .refreshCompletable() .subscribe() retrieveBehaviorStream() .subscribe { post Code } repository .refreshCompletable() Observable<S> fetchSingle() .flatMapCompletable { store.put() } — store .getBehaviorStream() Observable<Option<S>>
56. Presentation Domain Data countdown(d): compareTimestamps() .flatMap{ intervalRange() } Observable<Int> interactor .retrieveBehaviorStream() .flatMap { countdown(d) } .subscribe { Enable or Disable(seconds) } timestamp
57. Presentation Domain Data interactor .retrieveBehaviorStream() .flatMap { countdown(d) } .subscribe { Enable or Disable(seconds) } countdown(d): compareTimestamps() .flatMap{ intervalRange() } Observable<Int> timestamp
59. Presentation Domain Data interactor .sendCompletable(code) .subscribe() { success }, { error } service.sendCompletable Completable generateKeys() .flatMap repository .sendCompletable(k , c) Completable
60. Presentation Domain Data interactor .sendCompletable(code) .subscribe() { success }, { error } generateKeys() .flatMap repository .sendCompletable(k , c) Completable service.sendCompletable Completable
61. Presentation Domain Data
62. How our architecture allows new joiners to start contributing since day one - Implement Interactors according to the actions you’ll need: e.g. RetrievePairingData, SendCompletePairing - Implement Repository to make use of the reactive store to provide data to the interactors e.g. PairingRepository - Implement ViewModel with LiveData that reflects the view state e.g. PairingViewModel
63. How our architecture allows new joiners to start contributing since day one - Clean architecture is a solid standard - Very well defined set of interactors with clear meaning - Easy to unit test (gives you more confidence)
64. More about the architecture Lucia Payo @ Droidcon NY 2017 Lucia Payo @ Droidcon Berlin 2017 https://www.youtube.com/watch?v=16wPp91kyuE https://www.youtube.com/watch?v=foaKMruUBXc
66. Number 26 Jackson Pollock
67. N26 is hiring Senior Android Engineer - US (2019) https://grnh.se/2293a6ff1 Or see Mitch, Rui, or Franc to learn more about opportunities!