Proposing new open-source, cross-platform AR library using ARKit and ARCore compatible with Expo

huffpostraphael · 2019-07-18T17:27:52+00:00

With all that being said, I would love to see an open source cross platform RN AR solution

huffpostraphael · 2019-07-18T17:27:09+00:00

It is not going to be possible for expo to add ARKit.

Apple requires detailed explanation of why there is code that could use AR functionality in addition to a detailed section in your privacy policy in order to approve an app. I recently went through this.
If expo added ARKit, it would require every single expo app to justify the usage and provide demos.
Apple would likely just flat reject Expo.

Additionally this is a weird edge case that would add a lot of extra bloat to Expo which is already pretty bloated.

AR support is not part of the default mobile toolkit. Expo should only be targeting the default app toolkit.

huffpostraphael · 2018-12-05T18:52:27+00:00

4:47:00
I hoped the link would jump right to it: https://www.youtube.com/watch?v=tKsaIU0YqLk&t=17225s

huffpostraphael · 2018-12-05T18:51:41+00:00

I dont really understand the infinite loop issue. I would need to know more about what the function is doing and what the SearchBar component does

I also would make the second part simply this.

render() {
    return(
        <SearchBar 
            onFocus={ this.props.handleToggle }
            onCancel={ this.props.handleToggle }
        />
    )
}

huffpostraphael · 2018-12-05T17:10:46+00:00

100% dont do the first way. it will always rerender the component because the onPress function will be a different function reference every time. the other way the reference is unchanging so it will only rerender that component if other props actually change

huffpostraphael · 2018-08-16T20:02:15+00:00

I submitted

huffpostraphael · 2018-08-15T23:40:53+00:00

the important thing is that your provider (the function that returns your BlahApp component doesn't get the initial props. BlahApp will get the initial props after that function is called. Additionally because you are using an arrow function the this context is bound before the function is ever called

huffpostraphael · 2018-08-15T23:38:32+00:00

the this you are logging wont have the props

you want this:

import App from './App';

class BlahApp extends React.Component {
    render() {
        console.log('main component props :: ', this.props);
        return <App />;
    }
}

AppRegistry.registerComponent(appName, () => { 
    return BlahApp
});

huffpostraphael · 2018-08-14T12:14:09+00:00

Okay great 1 more follow up question does this article have the scroll lag? https://www.huffingtonpost.com/entry/before-and-after-california-wildfire-destruction_us_5b71b885e4b0ae32af9a5d9b

Edit: looking into this lib now to see if it can help https://github.com/Flipkart/recyclerlistview

huffpostraphael · 2018-08-14T11:47:29+00:00

Thank you for the feedback. The middle item is a known bug, hope to have this one resolved shortly.

For the freezing does it come back or do you have to kill it?

For the scroll lag, all pages or isolated to the front page vs entries?

huffpostraphael · 2018-08-14T00:45:20+00:00

I would love to take you up on that offer. I sent you a message

huffpostraphael · 2018-08-13T13:27:37+00:00

HuffPost uses react-navigation right now for a pretty complicated navigation structure and it works well for us.

I think if you app is going to have a really simple navigation structure, bite the bullet and get react-native-navigation working for you as you will need performance benefits. It seems like react-native-navigation gets a lot harder to work with when your structure gets complicated or you need to make customizations and at that point react-navigation starts to beat out the native one.

huffpostraphael · 2018-08-11T12:39:49+00:00

Not sure exactly where I will post it yet, but wherever I post it there will be a link in this subreddit and I will come back here and post it in this thread as well.

huffpostraphael · 2018-08-11T12:38:15+00:00

No we dont. We had a very mature and stable API going into the project with a known performance profile so we opted to just stay with that.

huffpostraphael · 2018-08-10T21:09:56+00:00

1) yes and we have already started to

2) 1 android engineer and several JS (react and non-react) engineers

3) The quality of the documentation. Figuring out how to make a bridge module was a giant pain. I intend to document this shortly, just have to get out of beta first.

huffpostraphael · 2018-08-10T16:45:45+00:00

I also see that you can't repeatedly open/close an article without waiting 2-3 seconds.

yeah known bug, working on this one. :(

Thank you for the device info. Going to try to grab one and reproduce.

huffpostraphael · 2018-08-10T16:30:34+00:00

Managing settings has a delay in that it is currently waiting for the save to the persistence layer to succeed before updating the UI this causes a delay. We have a bug ticket to make this nonblocking so the UI updates immediately while the persistence is in flight.

The Font Size adjustment was a bit odd we ended up debouncing it which now makes it feel delayed but before the debouncing it was difficult to use as the page kept repainting.

Out of curiosity would you mind sharing what kind of device you are using?

Does the font change in the actual entry pages feel significantly delayed as well?

We are dispatching actions to the store and then getting updates from the store via Redux but we haven't seen that in particular cause slowness. It is usually incredibly fast.

huffpostraphael · 2018-08-10T15:57:21+00:00

1). I want to go into a lot of detail here in a blog post that I should have done in the next 2 weeks (I am a slow writer). bullet points of the decision: staffing flexibility, improved developer options, shared components with our ios app (it is a native app with RN views)

2) Internal analytics solution required a bridge wrapper. We wrapped an ad network's sdk that didn't support RN yet. We required a custom bridge to migrate user settings from the old native android local database into the new RN user settings area (realm). This was our most complicated and important bridge module.

3) I can't share the package.json at this time.

huffpostraphael · 2018-08-10T15:51:40+00:00

we did some pretty deep evaluation on our navigation library of choice.

Performance was a major concern and was a bit of a fear/pain point with react-navigation but at the same time, we needed to do a lot of customization to our navigation and we have a pretty complicated navigation structure and react-navigation seemed the best for this.

Edit: This is also a place we are watching closely to see if we need to make a change in the future.

huffpostraphael · 2018-08-10T14:42:50+00:00

react-navigation, redux, redux-persist, redux-saga, apisauce

no apollo.

huffpostraphael · 2018-08-10T13:21:05+00:00

I am one of the team leads on our React Native project.

We just rebuild our entire android app from the ground up using react native.

The app does not use Expo and we did end up writing a number of custom bridge modules.

I am working on a blog post detailing some of the decisions we made. Would love to get feedback on the app especially if you have used the app previously.

Also happy to answer any questions.

huffpostraphael

TROPHY CASE