[blog] Add react native on meta quest post#4981
Conversation
|
Hi @lukasz-app! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks! |
✅ Deploy Preview for react-native ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
lukasz-app
force-pushed
the
meta-quest-blogpost
branch
from
4d33922 to
0dec7d8
Compare
Simek
left a comment
Simek
left a comment
There was a problem hiding this comment.
Looked at the Markdown content, and post on the PR preview, just left two notes, nothing blocking, so LGTM! 🚀
|
|
||
| Some Android permissions and hardware assumptions common on mobile devices do not apply to VR headsets. Cellular features (e.g. SMS), certain sensors (like GPS), and [restricted permissions](https://developers.meta.com/horizon/documentation/android-apps/unsupported-permissions/) are either unavailable or prohibited. Projects must explicitly account for these differences during setup. | ||
|
|
||
| ### Evaluating library compatibility |
There was a problem hiding this comment.
We might want to mention directory in this section, but first would be nice to add more compatibility flags, since now only 3 packages are marked as supporting Horizon OS:
There was a problem hiding this comment.
That's why I don't want to mention it here, it might blur the picture for new comers to the platform.
| [Reference project with all the setup used in this article](https://github.com/callstackincubator/expo-meta-horizon-os-demo) | ||
|
|
||
| [Callstack Meta Horizon OS showcase app from React Conf](https://github.com/callstack/react-native-horizonos-example) |
There was a problem hiding this comment.
| [Reference project with all the setup used in this article](https://github.com/callstackincubator/expo-meta-horizon-os-demo) | |
| [Callstack Meta Horizon OS showcase app from React Conf](https://github.com/callstack/react-native-horizonos-example) | |
| - [Reference project with all the setup used in this article](https://github.com/callstackincubator/expo-meta-horizon-os-demo) | |
| - [Callstack Meta Horizon OS showcase app from React Conf](https://github.com/callstack/react-native-horizonos-example) |
Nit, this might be a list.
lukasz-app
force-pushed
the
meta-quest-blogpost
branch
from
3b28b09 to
2bd5566
Compare
lukasz-app
force-pushed
the
meta-quest-blogpost
branch
from
2bd5566 to
9d85a1f
Compare
3 participants
This PR adds a blog post covering React Native support for Meta Quest devices.
The post explains how React Native runs on Meta Horizon OS, outlines the development workflow using Expo Go and documents the platform-specific configuration required to build and ship apps on Meta Quest.
It also covers platform differences from mobile Android, including the absence of Google Mobile Services, permission constraints, library compatibility considerations, guidance for writing platform-aware code, UX considerations specific to VR and links to reference projects and additional resources.