91–100 of 119 posts
I tested out React Native on Android the other day and it was a real disaster. It doesn't compile for all the CPU ABIs (instruction sets) we have, so if you have native libraries for x86 or arm 64 in your app it immediately breaks it completely. You have to remove all your own libraries for unsupported architectures, then modify your build not to include them, then depend on those platform's compatibility features to…
I'm interested in the game example. How is that built exactly? Is the game built in React Native (I presume not) or is React Native just used for UI elements? If so, what is the game built with?
Here's a video of a talk explaining how the game works: https://www.youtube.com/watch?v=2_KV7Ha_gRk
The game runs on Exponent and uses React Native for rendering (as all Exponent apps do). It uses individual `Image` components for each sprite. This gets choppy when you have a lot of sprites so we're experimenting with more performant ways of rendering for games.
I tested out React Native on Android the other day and it was a real disaster. It doesn't compile for all the CPU ABIs (instruction sets) we have, so if you have native libraries for x86 or arm 64 in your app it immediately breaks it completely. You have to remove all your own libraries for unsupported architectures, then modify your build not to include them, then depend on those platform's compatibility features to…
Some of these issues don't apply to Exponent: > if you have native libraries for x86 or arm 64 in your app it immediately breaks it completely We handle all the native code for you, so you'll never hit this. > half the examples and half the dependencies on the web out there crash immediately because they decided you have to import React and Component from "react" instead of "react-native" now We support multiple Reac…
How do you handle that exactly?
I'm interested in the game example. How is that built exactly? Is the game built in React Native (I presume not) or is React Native just used for UI elements? If so, what is the game built with?
Hey! I made floatyplane. The source code is here: https://github.com/exponentjs/floatyplane Here's a video of a talk explaining how the game works: https://www.youtube.com/watch?v=2_KV7Ha_gRk The game runs on Exponent and uses React Native for rendering (as all Exponent apps do). It uses individual `Image` components for each sprite. This gets choppy when you have a lot of sprites so we're experimenting with more per…
This looks really nice. I have a question about React Native though. I was under the impression that React Native meant that you could just take your components from your website and build an app out of it. I'v realized that's not the case. What is the benefit of React Native if you can't share the components?
Components aside, you can share your models and data stores, utilities like Immutable.js and lodash, and other environment-agnostic JavaScript. In addition to code, you can share a lot of knowledge like how to write components, structure an app, use npm, and even just write JavaScript.
This looks really nice. I have a question about React Native though. I was under the impression that React Native meant that you could just take your components from your website and build an app out of it. I'v realized that's not the case. What is the benefit of React Native if you can't share the components?
Give it a try! It's pretty solid.
This looks really nice. I have a question about React Native though. I was under the impression that React Native meant that you could just take your components from your website and build an app out of it. I'v realized that's not the case. What is the benefit of React Native if you can't share the components?
You can share some components, especially more abstract ones. For example, react-redux creates higher-order components that work with both React DOM and React Native. There's also a project called react-native-web that implements React Native's View components using React DOM's primitive components ( https://github.com/necolas/react-native-web ). Components aside, you can share your models and data stores, utilities…
messutied, you're shadowbanned so I can't reply but thank you for your response!
Earlier quoted context omitted.
Some of these issues don't apply to Exponent: > if you have native libraries for x86 or arm 64 in your app it immediately breaks it completely We handle all the native code for you, so you'll never hit this. > half the examples and half the dependencies on the web out there crash immediately because they decided you have to import React and Component from "react" instead of "react-native" now We support multiple Reac…
> We handle all the native code for you, so you'll never hit this. How do you handle that exactly?
I tested out React Native on Android the other day and it was a real disaster. It doesn't compile for all the CPU ABIs (instruction sets) we have, so if you have native libraries for x86 or arm 64 in your app it immediately breaks it completely. You have to remove all your own libraries for unsupported architectures, then modify your build not to include them, then depend on those platform's compatibility features to…
Why is the top comment on every story a negative one? Is nothing good anymore?
If the wheel you reinvented is square, you might run into someone who doesn't quite buy into your pitch of this being the future of technology.