2017.1 and 2017.2 are officially supported, and we recommend developers update to these versions when convenient. Our support for 2017.3 is currently in beta, and we do not recommend shipping applications using it at this time.
At Oculus Connect 4 we announced Rift Core 2.0, which includes substantial changes to Oculus Home and will replace our Universal Menu with Oculus Dash. We plan to make it available with the 1.21 runtime in early December.
Dash re-implements Universal Menu as a VR compositor layer. Have a look at our Blog announcement and watch the Dash video to get a sense of how it works.
We have added new application lifecycle support to our 1.18 integration in preparation for Dash. When Dash draws a menu overlay, the new Has Input Focus flag will return false, indicating that the application should pause and mute and the tracked controllers and hands be hidden from the scene, as Dash provides its own UI in the foreground. Depending on the application, additional action may also be warranted when input focus is lost (e.g., during a multi-player combat game, you may wish to freeze the player’s avatar and make it temporarily invulnerable to other players).
For more information, see Application Lifecycle Handling. See the Input Focus sample in the Unity Sample Framework for an example of a typical implementation.
Additional information about supporting Dash will be available soon.