Meta CTO Andrew Bosworth has responded to developer considerations over Quest’s Horizon OS efficiency regression and the puzzling Battery Saver change.
In the event you missed it, earlier this week we reported on developer considerations about Meta Horizon OS efficiency regression, in addition to a puzzling change to Battery Saver that capped apps to 45FPS, and different points builders have been dealing with in deploying VR and blended actuality apps on Meta’s platform.
Meta Quest Builders Face Bugs & Efficiency Regressions
Meta’s frequent Horizon OS updates are coming at the price of efficiency points and bugs for Quest builders, with customers typically blaming them.
In an ask-me-anything (AMA) session on his Instagram, Meta’s CTO Andrew Bosworth has acknowledged these considerations, describing it as “nice suggestions” that Meta is “taking significantly” and “spending time on” addressing. He additionally confirms that Meta is rolling a repair out for the Battery Saver challenge.
“We admire the suggestions as at all times, from builders, [and we] take it significantly. It is our accountability, these are our errors, and we’re gonna repair them.”
Nonetheless, Bosworth pushed again on the suggestion that the foundation trigger of those issues is the tempo of updates, saying that Meta simply must have “a stronger set of processes in place for high quality management earlier than issues exit the door”.
Here is Bosworth’s response in full:
“Good dialogue and suggestions from builders, this final week on the steadiness and adjustments that we’re making in our rollouts. Ensuring that these are larger high quality than they’ve been. I believe it is nice suggestions. We’re taking it significantly.
For the Battery Saver challenge, we’re rolling a repair out for that.
And extra typically, I do not suppose it is the case that we’re rolling issues out too shortly. I do suppose it is simply the case that we have gotta have a stronger set of processes in place for high quality management earlier than issues exit the door, which we’re doing.
We’re taking a severe have a look at this. We’re spending time on it. So we admire the suggestions as at all times, from builders, [and we] take it significantly. It is our accountability, these are our errors, and we’re gonna repair them. And we perceive that this isn’t informal. That is individuals’s livelihoods and time spent on the road that issues a ton, and the expertise that buyers have of individuals’s software program.
So yeah, taking that significantly, we’re doing the work. I believe staggering issues helps as a result of staggering issues truly helps us establish regressions sooner. However agree, we might do higher on documentation too.”
