Using React Native, Flutter, Hybrid Web, Unity, Kotlin Multiplatform could be an interesting strategy, but what if we want to stay within traditional native development on both platforms? A syntax of Swift and Kotlin looks pretty similar, especially if you are cooking it with RX. So, what if we will implement a new feature on one platform and then, kinda, copy-paste the code to another one, with minimum modification? How good it will work for us? How should we deal with platform-specific features? Will this strategy make a project too complex? This speech will show the way, how to design your project in order to minimize the headache of implementing the same feature for both mobile platforms. Also, we will talk about gains and losses during implementation on a real project with this design idea. http://uamobile.org/uk/topics/designing-iosandroid-project-without-using-multiplatform-frameworks

1. Designing iOS+Android project without
using multiplatform frameworks
Maksym Ukhanov
Engineer at droppity.co
April 6th, 2019

2. So, what’s the problem?

3. About me
max.ukhanov@gmail.com
fb.com/ukhanoff
https://www.linkedin.com/in/ukhanoff/
Disclaimer: logos and stating are not associated with or sponsored by the trademark owner.

4. RxSwift vs RxKotlin
1. filtered.subscribe(
2. { e ->
3. // onNext
4. Log.d("Rx","Result: " + e)
5. },
6. { ex ->
7. // onError
8. Log.e("Rx", "Error", ex)
9. },
10. {
11. // onComplete
12. Log.d("Rx","Done!")
13. },
14. { disposable ->
15. //onSubscribe
16. Log.d("Rx","Subscribed!")
17. }
18. )
1. _ = filtered.subscribe(
2. onNext: { e in
3. print("Result: ", e)
4. },
5. onError: { err in
6. print(err)
7. },
8. onCompleted: {
9. print("Done!")
10. },
11. onDisposed: {
12. print("Garbage collected!")
13. }
14. )

5. What Architecture to choose?

6. Project structure

7. Interface Comparison

8. RxSwift → RxKotlin
RxKotlin → RxSwift
https://github.com/ReactiveX/RxSwift/issues/1548

9. RxSwift → RxKotlin but RxKotlin → RxSwift
https://github.com/ReactiveX/RxSwift/issues/1548

10. What about tests?
Espresso и XCTest are
completely differs :(

11. What about tests?
Usage of Swift Cuckoo is similar
to Mockito and Hamcrest. Also it’s
similar to Speck from Jetbrains.
WIN!!!

12. Tests IRL

13. What about device specific API
(bluetooth, camera, etc)?

14. Pros and Cons
+ In overall feature on both platforms
will be delivered faster
+ Less code to rewrite
+ Easier to hire developers for native
project than for cross platform*
+ Predictability (comparing to other
multiplatform frameworks)
+ You can always stick to the backup
plan and write it as native
component.
*this is really subjective point :)
- It does not really help with UI
development
- Harder to join (Mid+ devs skills
required)
- Not the easiest/fastest way of
development, especially at the
beginning.

15. So, will it take off? © Oleksandr Yefremov

17. Links
https://blog.testfairy.com/rx-for-the-ultimate-beginner-part-1-swift/
https://blog.testfairy.com/rx-for-the-ultimate-beginner-part-1-kotlin/
https://www.youtube.com/watch?v=Jt-_oVQVZlQ&feature=youtu.be&t=977
https://www.youtube.com/watch?v=Jt-_oVQVZlQ
https://quickbirdstudios.com/blog/app-architecture-our-functional-mvvm-approach-with-rx/
https://github.com/ReactiveX/RxSwift/issues/1548
https://android.jlelse.eu/redux-rxkotlin-rxswift-awesome-native-mobile-apps-introduction-part-1-4ea7fa3be319