Firmware and mobile app tuning 2
it's time for another update.
Let's begin with the topic of shipping. Many of you are asking for a solid date of the shipments.
There is still too much to do so we still cannot commit to a specific shipments date but we can already announce date of October 29th, which is when the final watch assembly should start.
We can feel you might have wanted to hear an earlier date, so to explain, there are two main reasons why it's October 29th:
1) Due to the fact that we had to change the whole FPC unit, we missed earlier assembly window. Now the factory is working on a different project so October 29th is the closes possible time slot. But it's ours.
2) This should give us enough time to work on solid stable version of firmware and mobile application.
Many of you have been asking why it takes this much time to code firmware and application. We want to ensure you that we have been working on both the whole time of Sequent project being live. Because we exchanged FPC, which is one of the core watch components, inevitably we had to do some main changes to firmware and application as well. We are talking about a smart watch which means very complex system and big load of work. We would like to give you some examples to demonstrate the volume of work:
• FPC exchange caused certain core modifications to watch firmware.
• As we have been working on Firmware, Hardware, iOS, and Android somewhat independently, last 2 weeks have been focused on tuning everything to work together. From working out the communication protocols between the dual processors on board (ultra-low power core IC for time and accelerometer + a powerful processor that enables our low energy wireless, HR, and GPS into the smallest module combined on the market) to working out auto-setting time via GPS, RTC calibration with the phone through the app, and time zone calibration.
• One more example, let's imagine the architecture as a layer cake. Each layer building on top of the previous one. So if we go from the bottom it is Bluetooth communication modules, data reader/writer module, core OS API integration parts, HealthKit and Fit, Secure Storage and many many more…
• Generally speaking, changing the lower layers of cake means all other parts on top need to be changed, too. Then application needs to be distributed to our testers, we have to ensure all test watch devices are updated to latest firmware, too and with that we are collecting results from the field tests.
• In any software development, the last 10 % of work takes at least 50 % of time.
We hope you can see now why we say it is a massive work. Because it is a massive work. And it takes time. There is one key point thought. Our firmware and application teams are working extremely hard and are doing incredibly great job, as opposed to big corporations they are progressing very fast, collecting feedback from sample watches, evaluating results and making updates where needed.
With this in mind we are very confident to say that it is very realistic to reach October 29th for final production.
To sum up, we are working day and night (no exaggerating at all) and we are getting close to the finish line of October 29th. And soon, all together, we will get there.
Thank you all for your support,
have a great weekend,