ProTalk #1 | Native vs "Native"

Talks ini akan berbicara seputar diskusi mengenai relevansi tools dan SDK yang digunakan dalam pengembangan aplikasi di dunia nyata, mana yang harus digunakan, dan mana yang harus dihindari

Transcript

2. Hello Folks,
3. About Me?
4. Ganesha Danu Enastika Broke College Student by Day and Broke Software Engineer By night iOS Developer COO of Proclub
5. What do I do? Building modern chat application using email technology
6. Context
7. !Native, Native?, “Native” and Native What is it? Should we care? Is it relevant? And our Option?
8. !NATIVE
9. Hybrid is not an Instrument Native Let’s be clear before we continue, even you wrap a web application into a native layer a.k.a. “Hybrid” does not make it native
10. Do not use Hybrid BUT, I think it could be a viable option even though it is not as powerful as the other option, but it provide you with a fast option to develop your app.
11. NATIVE?
12. React Native is a Mistake ;(
13. Let’s make everything into JS One Quick Question...Why?
14. The Problem - Single Thread - Inconsistency in Paradigm - The “Undefined”
15. is it really that BAD?
16. It’s easy to make thing beautiful Base on my experience you could build a View in just hours of work where the other option may need days to work on
17. The Nuts, and Bolts, and also The Bridge
18. Beyond Two Souls Engine Even though it’s look identical the Dev and Prod mode of React Native is being maintain by different engine. So, some library or piece of code may not works on production
19. The Bridge React Native works by connecting your javascript code into a program (The Bridge) that communicate with the native component of your platform
20. “NATIVE”
21. The New Boi in Town
22. The Flutter way Flutter is a whole new SDK and environment to develop a true cross platform native app. And it’s made by google
23. What’s The Deal?! - Beautiful by Default - “True” Native - Modern Development - Real OOP And it’s in V1.0
24. Is it the future?
25. NO
26. NOt yet
27. Here’s why
28. It’s just not mature enough - Dart not really that popular - Pub is inferior than npm - Less learning resource
29. NATIVE
30. Ok, Why should we write in Native?
31. Well, Why not
32. Why not? By writing a real native application with corresponding native programming language, we avoid so much engineering debt
33. JVM Android is not that bad Well, there are 7 billion device that using java, which mean there are a lot of literature resource for each of our engineering problem Plus, now there’s kotlin
34. Swifty Masterrace In the apple side, there is xcode ecosystem and swift, tools so powerful you could build an app in a single night. Not to mention apple community has great support and docs for new dev
35. Which one should we pick, then?
36. That’s your decision
37. Question?
38. Reach me github.com/blinfoldking ganeshadanu@proofn.com linkedin.com/in/ganeshad/
39. Thank You
40. SUBSCRIBE TO PEWDIEPIE