Hey, you can do it! How to contribute to the client projects. 

Self introduction JD Security Computer Science Android iOS Mobile Security Server 

What makes you think it's difficult? 

I think.. ● To layout UI ● To support multiple device (multiple Screen Resolution) ● To interact many users ○ System ○ User 

Yeah, but… Is that really the reason? 

Hmm, We are gonna help you. 

No content

Let’s break the huddles step by step! 

Do you know? Clean Architecture Domain Driven Design 

We have multi-module architecture. The server team has the microservices.. link link awesome slide: awesome doc: 

If you wanna add some functions to the config service Write the code 

If you wanna add a feature 

How do we handle async tasks? fetchAds(param, object : FetchAdsListener { override fun onSuccess(ads: List) { fetContents(param, object : FetchContentsListener { override fun onSuccess(contents: List) { ... } ... } } ... }) Observable .zip(fetchAds(param), fetchContents(param)) { ads, contents -> // do something } fetchAds(param) .flatMap { it.toObservable() } .filter { it.type == TypeVideo } .map { it.transformToCampaign() } .subscribeOn(Schedulers.io()) .observeOn(AndroidSchedulers.mainThread()) .subscribe(...) Study ReactiveX 

We'll do it, you don't. class GetVideoAdCampaignUseCase constructor(...) { operator fun invoke(param: GetVideoAdCampaignUseCaseParam) : Observable = fetchAds(param) .flatMap { it.toObservable() } .filter { it.type == TypeVideo } .map { it.transformToCampaign() } } fun callGetVideoAdCampaignUseCase() { val param = GetVideoAdCampaignUseCaseParam(...) val disposable = GetVideoAdCampaignUseCase(param) .subscribeOn(Schedulers.io()) .observeOn(AndroidSchedulers.mainThread()) .subscribe(...) disposables.add(disposable) } 

How can I fetch the data from other data sources? interface DataSource { fun fetchAds(param: Param) : Observable> } // Delegate to CLAVENGERS class RemoteDataSource constructor( private val serviceApi: ServiceApi // Generated by Retrofit ) : DataSource { override fun fetchAds(param: Param) : Observable> { ... } } class RemoteDataSource constructor( private val serviceApi: ServiceApi // Generated by Swagger ) : DataSource { override fun fetchAds(param: Param) : Observable> { ... } } https://github.com/Buzzvil/buzzapis 

Before you implement the class ● CMD + SHIFT + T ● Write down the test. 

It's not that different from the server, is it? 

So, How about the user interface? Delegate to 

MVC, MVP, MVVM, MVI, (RIBs) ... I strongly recommend MVP. Because it is super easy. interface Contract { interface View { fun renderLoadingStateView() fun renderLoadedStateView(...) fun renderErrorStateView() } interface Presenter { fun requestLoad() } } class PresenterImpl : Contract.Presenter { override fun requestLoad() { modelLoader.load() .doOnSubscribe { view.renderLoadingStateView()} .subscribe({ model -> view.renderLoadedStateView(model) }, { e -> view.renderErrorStateView() }) } } 

Now, you've done almost everything. So, really delegate it to 

Wait… How do I contribute to the iOS? 

iOS is equivalent to AOS. But.. You should learn Objective-C. #import @import ReactiveObjC; #import #import #import #import @protocol BuzzConfigServiceApi - (RACSignal *)getListConfigsWithRequest:(BuzzApiListConfigsRequest *)request; @end 

So, I will break the huddle to help you as soon as possible 

The future Business Logic I will focus on how to share to same business logic on each platform. 

I’m going to use Multi-platform framework. ● Does that mean using React-Native, Flutter, Ionic, Xamarin? ○ NO! ○ They try to solve almost every task with the same code. ○ However, some features, rendering, and IO operations are prone to unexpected exceptions. ○ Most importantly, there is no code base and we have to work from scratch. ● So, I’m going to use Kotlin Multi Platform. ○ Easy to migrate (AOS already has) ○ I love kotlin. ○ => I will restrict the code base with the same idea as RIBs. 

https://github.com/uber/RIBs ● Business logic drives the app, not the view tree. Unlike with MV*/VIPER, a RIB does not have to have a view. This means that the app hierarchy is driven by the business logic, not the view tree. ● Independent business logic and view trees. RIBs decouple how the business logic scopes are structured from view hierarchies. This allows the application to have a deep business logic tree, isolating business logic nodes, while maintaining a shallow view hierarchy making layouts, animations and transitions easy. 

Please join us even before that day comes. Are you ready? 

We will be watching you 👀 

Thank you for listening. 

Q & A