silkodyssey

SEEKING WORK - Remote Mobile Developer based in the Caribbean (reasonable rate :)) Skills: Native iOS / Android, React Native. I've worked on projects using RxJava, Firebase, MVP architecture.

I also have experience with client side development React / VueJS / Redux and server side development with Node.

email: [email protected]

You write Android apps the same way you'd write them in Java and the Android SDK but with the Ruby language. The quickstart gives you an idea of how to translate some of the Java to Ruby but you'll still need to learn how to build Android apps with Java.

In an absolute sense, maybe but 10x more would be moving in the right direction! :)

I posted a follow-up to this story talking about further explorations based on the feedback I got from your comments.

https://kelvinpompey.me/tempted-to-abandon-react-native-for-...

The first module I tried was react-native-image-picker and yes it returns an object with base64 encoded data. What I do with this data is first, resize the image then display the resized image in an ImageView then upload the resized image to Firebase Storage.

I did just that. I created a native Android project that selected an image from the image picker and displayed it in an image view. I tested it with a few images and it worked. Even the image that crashed the React Native app.

"Given that you believe this is a memory-related problem, perhaps it's because the image is too large to fit into the available memory, and having React Native made it worse. "

This is precisely what I think it is.

That's an interesting idea. The code to select and resize the images are native third-party plugins so in this case I am not sure anything more could be done.

I thought maybe the problem was that the app had to switch to another app to select the image. I reimplemented the code using a pure JavaScript plugin based on React Native's CameraRoll API to avoid switching apps and it still crashed when the image was selected for processing.

I've dabbled with NativeScript a bit. It does seem a bit closer to the underlying platform but from my experience of it, it felt incomplete.

I first tried the Angular version before the final version of Angular was released and I recall occasions where the documentation for NativeScript was behind the actual API. I had to look at the actual code samples to figure out the correct APIs.

The next time I looked at it, I tried the regular JavaScript version and I recall having trouble deciphering the API for the SideBar plugin.

This left me feeling a bit insecure about the product. It looks to have a lot of potential though but it could use a bit more polish and better documentation.

That's a fair point about the opportunity to build some performance-tuning muscle but I imagine to do that would require solid knowledge of both React and Android. Where do I start? I am more inclined to go towards the native Android side first.

Aa a follow up, I just did a test with a native Android app doing the same thing: getting an image through an Intent. With the native Android app, the same image that was crashing the React Native app doesn't cause any problems.