Hi everyone, Daniel here from XY. Since we started mass shipping XY about 3 weeks ago, roughly 80% of awards have been fulfilled with mostly multipacks including Jade remaining. We have heard from many of you via emails, in-app feedbacks and comments here -- some of the responses were happy, some were angry, but almost all were extremely encouraging, patient and helpful. We really appreciate it. Please keep them coming (feedbacks submitted via in-app mechanisms have been particularly helpful for debugging).
Today I want to talk to you about the top issues from the feedback we've gotten so far:
Buzzer Doesn't Work on some iPhone 6 Plus / 6
Should be resolved in the v1.3 of the XY iOS app -- already submitted the App Store and is currently awaiting approval. It's available right now to our beta users via Apple Testflight. Please contact us at firstname.lastname@example.org if you'd like to be part of this awesome group.
Beacon Not Visible in Nearyby List / Already Claimed
About a week ago, with the help of a few resourceful backers, we discovered a major fu... flaw in our manufacturing process. In some cases, the same beacon identifier (which should always be unique) were assigned to multiple beacons. At the moment, we still don't have a very clear picture how this occurred. It's apparent from the data logs that QC team at our factory did periodically reset the ID allocation program (bad!) but we don't really understand why... yet.
What is clear is the effect on the user experience. Backers who have received one of these beacons with duplicate IDs will simply not see the beacon in their NEARBY list, or see it as already "CLAIMED" in v1.3 of the iOS & Android app. At the moment, this is affecting roughly 7% of new beacon registrations.
Luckily, there is a solution. We designed the XY beacons for extensibility and in-field support -- the beacon firmware can be updated over-the-air via the XY app. (Most of our competitors do not.) We have a working firmware that fixes this issue and adds support for adjustable broadcast intervals, which can extend the already great battery life on these beacons. We are testing the new firmware and the update process internally. We expect to make this available to backers in our beta channels starting next week with general availability the week after.
If you think you are affected by this bug, please send us a note via the in-app feedback. We should have a resolution for you soon. Thanks for your patience. More updates on this soon.
The Casing is Difficult to Open
This is a known problem. We had to make some choices between the soft-touch of the casing material, water-resistance, and easy of opening the case. We may have put too much emphesis on the former two at the cost of the later. I apologize for any frustration this may have caused, and we will make adjustments to the manufacturing process for future batches.
I do want to stress that it is possible to open the beacon without damaging the case. Per suggestions from a few of you, we have made a tutorial video:
Range Issues / Out of Range Alerts at Short Distances
We are still investigating this problem. The current theory is a few beacons may, for whatever reason, have very long broadcast intervals that will trigger the out-of-range alert on iOS devices. If this is the case, the adjustable broadcast frequency in the new firmware should help... but frankly we don't know enough at this point to say for certain. More updates to follow.
That's all for now. As always, please keep the feedback coming and thank you for your support.