VRidge launchLast week we started selling VRidge as premium product. We had to create some quick client and server side hotfixes to keep everything running smoothly. We added some checks for exotic PayPal error codes too. Everything is currently operating normally and we started getting back to regular development schedule.
If you can't use PayPal remember that you can send us an e-mail (email@example.com) to process payment manually through TransferWise. More payment options will come after we fix bugs we promised to fix a while ago (Intel-, MediaTek- and Kirin-chipset phones, etc.).
What's next?We want to continue with frequent updates but every change, even the slightest one, can break something. For example, we can add a lot of optimization in an update that will improve experience for 99% of our users but break stuff for the remaining 1%. It sounds good statistically but this would mean that a lot of users (the last 1%) would have problems they didn't have earlier. We of course would fix those new bugs but this takes time.
Forced updates are not the greatest user experence - that's why we decided to split updates in several branches.
- Beta update branch will be updated few times a month (probably once a week like we used to do in beta phase). Use it if you want to be first to access new features and bug fixes.
- Stable update branch will be updated less often, every few weeks. We don't want untested changes going live for everyone as forced update.
- Previous stable updates will contain stable versions from the past. If somehow beta bugs make it into stable branch you will be able to switch back to previous versions and ignore updates.
This will not always work. For example, VR SDKs, graphics drivers or some other condtions can change in a way preventing backwards compatibility. We're not always in control but we will try our best to give you the most options.
Client update with branch selection should be available next week.
But what about features?If you are signed up for Android beta releases (you can join & leave beta channel here) you will see an update 1.0.1b in few hours. We updated our app to use Google's latest VR SDK instead of Cardboard SDK. This shouldn't break anything and it brings improved tracking and native drift-correction for default tracking algorithm. Also, this is first step in Daydream's direction. We are really excited about Google's plans for VR. Check out the beta update and tell us if you notice any improvements in default tracking algorithm.
If it causes additional crashes let us know so we can fix it before pushing this update into stable channel. :)
We also started working on GearVR version. We are in early stages and we're still assessing the amount of work required to create native GearVR Vridge app. We'll keep you updated!