Descargar para leer sin conexión
React native
- 2. AGENDA Qué es? Cómo funciona? Historia Porquéusarlo? Performance Quién lo usa? Porqué vamos a usarlo en HOP? Futuro Demo
- 3. QUÉ ES? Que noes? • App web incrustada dentro una webview • App js React Native es un framework open source creado por Facebook para desarrollo de apps mobile nativas utilizando JavaScript, React y JSX
- 4. CÓMO FUNCIONA? React Nativetoma el código JavaScript ( React y JSX ) y utilizando un “puente” invoca APIS en código para generar la aplicacion para cada dispositivo - Objective-C (iOS) o Java (Android)
- 5. HISTORIA 2009 - ApacheCordova 2011 - Xamarin 2013 - Ionic – angularjs 2014 - Swift (IOS) 2015 - React Native 2016 – Kotlin (Android) 2017 - Flutter La principal diferencia entre ReactNative y las apps basadas en Cordova es que en Cordova las apps se ejecutan dentro de una webview, mientras las RectNative apps renderizan utilizando views nativas. Las apps de ReactNative tienen acceso directo a todas la APIs y views que ofrecen los sistemas operativos. De forma que la experiencia de usuario y el rendimiento es el mismo de una aplicación 100% nativa.
- 6. PORQUE USAR REACTNATIVE Rápido desarrollo Utiliza componentes nativos LiveReload Unit testing con Jest Mismo código para apps IOS y Andriod Rápida curva de aprendizaje Componentes reutilizables Se puede utilizar junto con código nativo
- 7. PERFORMANCE Comparing the Performancebetween Native iOS (Swift) and React-Native Una contra de ReactNative es el peso de la app ya compilada
- 8.
- 9. HOP Código React Comparte códigoentre desktop y mobile Versión IOS y versión Android. Equipo de desarrollo reducido Cuenta con una gran comunidad Gran cantidad de paquetes ya desarrollados
- 10.
- 11.
- 12. DEMO Let's see howits works!
- 13.
Notas del editor
- #12 Pros of Flutter Faster code writing that normally takes seconds and helps teams with adding features, fixing bugs, and experimenting faster Developers need to write just one codebase which is used for apps covering both Android and iOS platforms Having a similar app for two platforms means that it requires less time in testing and the Quality Assurance process can be faster. Simple to make your own widgets or customize existing widgets such as material design widgets or Cupertino widgets. Ideal for MVP because you need to build the app in less time Cons of Flutter Flutter is still in beta and has not released the stable version yet. It is also not supported by Continuous Integration (CI) platforms like Travis or Jenkins. Thus, in order to achieve automatic building, app testing, and deployment, your development team needs to use and keep custom content. Flutter is fully supported by Google and there are several useful libraries with functionalities that are ready to implement. However, Flutter is still not at all that rich with respect to native development Pros of Xamarin The framework uses C# language that functions flawlessly over a myriad of platforms (Android, iOS, and Windows) More than 1.4 million developers used Xamarin in the first quarter of 2017, due to its ability to write native UI codebase for mobile app development If you are building an app for multiple platforms (like Android, iOS, etc.) you can share or reuse most of your code in your app for the other platforms Access to native API: You can get platform-specific functionalities in your app Several controls and layouts provided in Xamarin helps with a faster development process Faster app development with NuGet and Xamarin plugins Used by numerous well-known brands, this cross-platform app development framework offers competitiveness in developing outstanding native app interfaces that successfully outperforms the limitations of hybrid apps Cons of Xamarin Xamarin is not free and you not only need to buy the framework but its price. So, this is not at all for startups or budget constraint businesses Limited access to different vital libraries for the creation of an app using this framework User-Interface (UI) development is time-consuming as the core user-interface creation is not mobile Xamarin suffers from low community activity, which is not good for developing a framework.