Thanks for the update and clarification.
It's really cool that you took the time to layout your progress in detail.
Regarding Andy's well-meant post. I think it's quite tricky to name a fixed timeframe for an upcoming update.
It gets peoples hopes and expectations up, which can backlash if they aren't met.
Fingers crossed for the firmware upgrade – update to work as intended when it's released.
Best,
Tim
Oliver wrote: ↑November 27th, 2018, 6:28 pmHaha, nooo! not no mans sky! ;-)
We're really sorry about this issue, and also the lack of communication about it.
We could have communicated a little more, but it would have mainly been "we're working on it", which of course is not very helpful.
The thing is that the firmware is fixed (as far as we know), but we need to roll out this firmware to you as well.
A) for this one fix for a smallish group of people
B) for other fixes, feature updates, etc for everyone
We've planned for this from the start, and everything basically works. But if we've learned one thing from the last few weeks, with plenty of forum entries and hundreds if not thousands of support emails, is that what works perfectly here in the office, does not necessarily work so well with every customer.
on iOS a little less so than Android, mainly because according to the Google Play Store, our app is compatible with 7631 different Android devices, no wonder some behave differently than the 4 we're developing on and a couple more that we test on.
So, before we roll out this firmware update to everyone, we want to do more testing of the update process which can cause bigger problems.
Now the problem we have is twofold:
1) We had lots of issues to fix in the apps (again more so on android than iOS), and during fixing it turned out that it makes sense to refactor important parts of the app, rather than applying one patch after the other. So both iOS and Android app development teams have been working on this in the last couple of weeks. So on top of figuring out that we need more time than anticipated to finish implementing and testing the firmware update process, our developers have less time than expected.
2) Before Unleashing the Firmware update on everyone (which requires even more stability and even more testing) we're looking into possibilities to roll out the firmware just to those affected by this mean Canon bug.
This requires so many more changes than you'd think - from changes in firmware, to Bluetooth communication, obviously the apps too, and last but not least, the distribution of the apps to the customer.
For both of these points, we had nothing to say until decisions were made, and these decisions could not yet be made, until today.
Our internal meetings today brought some clarity:
1) Our App developers will prioritize finalizing the Firmware update process starting tomorrow, and we plan to have this ready by the beginning of next week.
2) We will start a Beta-program, or something similar, where we can invite some selected users to test new Apps and Firmware, without having to roll out the updates to every customer. We'll start with the users of Canon cameras that currently cannot even use their Unelasheds, since you have little to loose at the moment, so if the firmware update doesn't fix your issue or brings along a new bug, ... well ... you probably wouldn't notice, or at least it wouldn't make things worse than before.
While we're looking into setting up the beta program on the iOS AppStore and the Google Play Store, we'd like to invite those of you who are affected by this Canon Bug to send us their Details, if you'd like to join.
We need:
- email address - the one you used to register on the AppStore/Play Store
- iOS or Android + Version
please send that to beta@foolography.com
- Camera Model(s)
Of course at the same time we're working on getting the firmware update working perfectly in the normal app for everyone, it will just take a little longer.
Thanks and sorry again for this issue!
