You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
react-native-inat-camera is our own custom camera library with native camera implementations. It works pretty well in iOS, but has some pretty serious performance problems on Android. We made it because at the time there wasn't a good React Native camera library that could use the kinds of ML models we use. Since then react-native-vision-camera has added support for custom frame processors, which is exactly the kind of hook we need to do custom classification with that camera. That library supports more recent camera SDKs on Android and might provide a better camera experience. FWIW, @budowski has made a proof-of-concept showing that we can use that technique to use our model with react-native-vision-camera.
The task here is to replace react-native-inat-camera in Seek with react-native-vision-camera with a custom frame processor, and determine if the experience on Android is superior to our custom camera, and the experience on iOS is no different (or better). So kind of R&D that will hopefully make it into the product. Yaron has done the most work on this so if he's not the one to work on this issue, whoever is should check in with him to get his proof-of-concept code.
The text was updated successfully, but these errors were encountered:
react-native-inat-camera
is our own custom camera library with native camera implementations. It works pretty well in iOS, but has some pretty serious performance problems on Android. We made it because at the time there wasn't a good React Native camera library that could use the kinds of ML models we use. Since then react-native-vision-camera has added support for custom frame processors, which is exactly the kind of hook we need to do custom classification with that camera. That library supports more recent camera SDKs on Android and might provide a better camera experience. FWIW, @budowski has made a proof-of-concept showing that we can use that technique to use our model with react-native-vision-camera.The task here is to replace react-native-inat-camera in Seek with react-native-vision-camera with a custom frame processor, and determine if the experience on Android is superior to our custom camera, and the experience on iOS is no different (or better). So kind of R&D that will hopefully make it into the product. Yaron has done the most work on this so if he's not the one to work on this issue, whoever is should check in with him to get his proof-of-concept code.
The text was updated successfully, but these errors were encountered: