(Udacity)

So now its just native code left?

@zemaitis they probably generated the basic app with rn, its not great for anything complex, and then finished the codebase in native.

But now you have to maintain two codebases.

Hope the universe understands that native is the way to go!

Enough with this shit, React Native, Ionic, Phonegap, Flutter, Xamarine ...etc.

@otavio read the comment before, rn by itself is not a viable solution

@gitpush i like how rn does it tho, it transpiles to native code.

@sharktits I believe you can use it along with native code when there is no way to do it just with JavaScript. Many companies are doing it like this.
Writing apps in JavaScript is so much more pleasurable. But each one with your opinion

@otavio yes its such a great idea to do that really. Most companies build the mvp in rn and then finish it up in native.

@sharktits its all just commercial shit, data processing is done in Javascript which is painfully slow compared to native processing

UI is bridged to native and native components are used but go fetch data from an API and hell gates will open on you to tweak performance

I was about to start using rn for a project...

I don't understand... React Native builds into native software. It's all a wrapper. It's supposed to be a different tech than phonegapshit or appshitlerator.

Xamarin uses mono runtime, which of course has an overhead. But React Native shouldn't...???

@rephiscorth refer to @gitpush 's comment

@rephiscorth I made a react native app and helped in another, to fetch data from an API we use the fetch API(which is this: https://developer.mozilla.org/en-US...)

(Source: https://facebook.github.io/react-na...)

To sort, manipulate lists/arrays and handle JSON objects I do exactly the same as I do it on a web page, using map, sort, and x.y.z (for json)

I write JavaScript code to handle data processing

I use flex box, position absolute...etc (css eh?) to put up a clean UI

More of the pain is Android and iOS do not render the same, in terms of, each platform has its own way of rendering, so a perfectly looking UI on iOS has a 70% to be fucked up on Android

Did I mention something about RTL and LTR? a UI positioned using: position: absolute requires special handling when using RTL languages because it doesn't go to the other side of the screen when all other controls has gone there.

and the list goes on forever

@gitpush what's your opinion on flutter then?

@ogtega I'm still learning it, and need to build at least one app to experience part of it's ups and downs

My company's app has a small section written in RN. It's by far the slowest part of the entire app, it takes a ridicoulus amount of time to load and everybody in the team hates to maintain that part of the app.

If everyone hates react so much, does anyone have suggestions for a solo not-in-workforce-yet developer that’s writing a cross platform mobile app?

@A-C-E tbh you better go native, but if your local market relies on cross platform then go with the one they ask for.

But if not, and you still want to go hybrid, go with React Native, yes it is really a pain but it gets the job done for small apps (focus on the word SMALL).

But I still find it better to go native, start with Kotlin for Android,you need to do some native development to be able to easily handle things on hybrid apps.

@gitpush I have quite a bit of native experience with swift but my Android skills are very lacking and the goal of going hybrid was the code sharing so I didn’t have to write the same thing twice and maintain two versions

@gitpush looks like kotlin can compile to native iOS and windows too??? I’m intrigued

@A-C-E seriously? Never checked lol
Try native, you won't regret 😀

@A-C-E Wow. I'm gonna try this kotlin now.

The performamce of ionic is quite bad because the code is interpreted at runtime and the UI is rendered in a webview. React native, titanium and nativescript are also interpreted at runtime but they use native UI elements. Xamarin, Flutter or CodenameOne compile the code into native code. The performance is therfore much better, but the development effort is normally higher.

Everything would be easier if they didn’t limit things to one language, then we could use one single language to compile to something fast and easy to maintain on both platforms!

@-vim- well the language would not be the problem, there are already transpiler. The problem is the binding to the native system functions and UI widgets. There are a lot of them and they all have a different interface / name on each platform.

@gitpush devRant is built on Xamarin 😬

@DarKneT Seriously? I know it is using React Native .-.

@DarKneT its not tho

@gitpush @sharktits welp!, my bad, it's built with titanium not Xamarin

@DarKneT tbh this is the only non native app that I found to be good enough for daily usage lol

React native or titanium apps can be quite fast, but the main problem is, that there are often situations where you need hacky workarounds.

But the most important point is: dont use cordova/ionic for anything else than prototyping. React native, titanium or nativescript might work for production apps depending on the requirements.