What was the scope of their involvement?
Boxfish Studio's collaboration was based in three different fields: firmware, desktop applications, and the web.
For the firmware, they helped us to develop different functionalities using an ARM-Cortex M3 microprocessor. It uses I2C drivers and USB communication. Using the same micro but with different peripheral hardware, they develop a functional test — simulating and analyzing digital and analog signals — after it was integrated in the needle test of the Electronic Manufacturing Services (EMS) production line.
For the desktop applications, the application called "service toolbox" —implemented in Java — is our interface between the bike — an ARM processor — and the user. It has USB and Content Addressable Network (CAN) functionality as well as communication to a cloud server. They have helped us improve our Common Interface (CI), which is built in Java FX, as well as add new features and increase the possibilities of the CAN and USB communication.
They helped in two projects for the web. The main one was a Manufacturing Executing System (MES) that helps keep track of all the pieces during the production line. They helped with the backend using Django as well as the frontend development using React. The second project was the webpage.
What is the team composition?
We started with two people: Augustin (Head & Co-Founder) who worked on the electronics, software, and backend; and Begonia (Heart & Co-Founder), who worked on the frontend and desktop application. They then added a web developer.
How did you come to work with Boxfish Studio?
Some of the team worked for our company in the past; I’ve known them for a long time.
How much have you invested with them?
We’ve spent about $130,000–$140,000.
What is the status of this engagement?
The project started in June 2018. We’re still working together, but we don’t have a project right now as we don't have enough development force in-house. Our last project ended a few months ago.