Forum Discussion
[Go] Recommended pipeline to share a private enterprise application for Go users within organization
I'm working with a client who's interested in using the Go as a previsualization device to facilitate communication with their clients. The proposed workflow is:
- We build and package an Oculus Go application in UE4
- Deliver it to the client via FTP or similar method, along with a batch script that they can run to load it onto a Go connected to their PC.
- Do the company's client's Go devices need to be in developer mode to accept the file transfer from the PC? (I believe the answer here is yes, and that we would manage this by adding them to the company's Oculus organization. Am I right about this?)
- Are there any application signing or security issues we should be aware of in doing this? (I know the Go doesn't require an .osig file - anything else that would prevent it from working?)
- Is there anything else I should be aware of in planning this pipeline for them?
1 Reply
Replies have been turned off for this discussion
- Hi imperativity,
Thanks so much for this advice! I wasn't aware that this was an option, but I believe it would be an ideal solution. Certainly much more user-friendly than development mode, adb push, and the forest of items in the Unknown Sources list.
