I know this isn’t what you wanted to hear, but knowing the recommended methods will shine through in the final product. Almost every developer who has done Gear VR development will immediately notice things like the gaze cursor being a set distance from the head instead of it being projected on the surface you’re looking at like it should be.
Developers will appreciate the attention to detail and users will have no idea, but they won’t be sick and won’t have headaches or eyestrain. The last thing you want is a user to leave your experience with simulator sickness.
So let these documents guide your development process and if you decide to stray away from the path set before you by Oculus, make sure you understand why it’s not recommended to do it that way and try to minimize any negative effects.
A bearer instrument is a document that entitles the holder of the document rights of ownership or title to the underlying property, such as shares or bonds. Bearer instruments differ from normal registered instruments, in that no record is kept of who owns the underlying property, or of the transactions involving transfer of ownership. Whoever physically holds the bearer document is assumed to be the owner of the property. This is useful for investors and corporate officers who wish to retain anonymity, but ownership (or legal entitlement) is extremely difficult to establish in event of loss or theft.
A public address is embedded inside the output “script” so that it can only be spent using the private key corresponding to that public address. If we consider this output to be a database row, what we have is a database with per-row permissions which are based on public key cryptography. Furthermore, every transaction presents a publicly auditable proof that its creator(s) had the right to delete/modify its prior rows. This (I believe) is a genuine novelty in database technology.