jesseruder

Joined 10 years ago

Karma

Submissions

Member since

Sep 26

View on Hacker News

Recent submissions

Comment · 9 years ago

Definitely! http://www.reactnativeexpress.com/ uses it and it works really well for them.

Comment · 9 years ago

We just deployed a change to make the modal overlay more transparent. Hopefully this will make it more obvious that there's an editor underneath the modal.

Comment · 9 years ago

That's a great idea! We need to add an accounts system before we can do that, but I'll add that to our list.

Comment · 9 years ago

If you click save and then re-scan the QR code, that url should work without the webpage open. Let me know if it doesn't work.

Comment · 9 years ago

I think right now it makes sense for us to be separate from React Native. Adding all of these libraries adds QA overhead and if Facebook doesn't use them internally it'd be hard for them to keep them up to date. In addition there are some other features we support that definitely don't make sense in core. For example we embed multiple versions of the React Native runtime in our app so that people can choose when they upgrade and we don't break old projects when we push a new version.

Comment · 9 years ago

Those examples are using this library: https://github.com/necolas/react-native-web. It's really fast but the downside is that you can't use any native APIs, so things like gyroscope and push notifications won't work. Since we have an actual app we're able to support all those APIs.

Comment · 9 years ago

There's this project: https://github.com/necolas/react-native-web that's similar to what you're describing. The downside is that you don't have access to any of the native APIs. Since we have an actually app we're able to support contacts, camera views, geolocation, etc.

Comment · 9 years ago

Oh the first example should be a heart that explodes when you touch it. Sounds like something went wrong loading it. Sorry about that.

Comment · 9 years ago

Well you either need to scan or click the "Preview" button to open up Appetize. We thought it'd be good to push people towards the mobile apps since they have better performance.

Comment · 9 years ago

Those are all really good points. We wanted to push people to download the apps because the performance is so much better than Appetize, but maybe that's not the right tradeoff.

Thanks for letting me know the OpenGL demo is crashing, I'll take a look at that.

edit: It looks like we have a bug with our iOS simulator build. We'll update that but for now Android Appetize works.

Comment · 9 years ago

Ah interesting point. Maybe we could make the overlay slightly more transparent?

Comment · 9 years ago

Thanks! I really like how shadertoy show previews of each shader. Maybe that's something we could add eventually.

Also - you can use OpenGL with this: https://sketch.expo.io/rJiYksBse

Comment · 9 years ago

Here's an example we made using the Animated library: https://sketch.expo.io/HyobXP7oe

And a basic SVG example: https://sketch.expo.io/H1ucC8Xsg

Comment · 9 years ago

Yes a lot of times the issue is that libraries only support certain version of React Native, so for certain sets of libraries there are no versions of React Native compatible with all of them.

Expo has audio (https://docs.expo.io/versions/latest/sdk/audio.html), file system (https://docs.expo.io/versions/latest/sdk/asset.html), and other APIs built in (https://docs.expo.io/versions/latest/sdk/index.html). We don't have sqlite right now but are actively working on it!

The idea is that we provide a lot of nice things out of the box and then if you still need to write native code you can detach (https://docs.expo.io/versions/latest/guides/exponentkit.html) and only write the native code you need while keeping all our other APIs. You can still use `react-native link` after detaching if you want.

Comment · 9 years ago

Hey I work on Expo - this is one of the big pain points we're trying to improve. Since Expo is responsible for the native code in these apps we can do the work of keeping all the libraries up to date. You're just responsible for updating the JS code, which normally has minimal breaking changes. Many people have been able to update versions by only changing their dependencies in package.json.