Cloud Dev for Motion Capture Startup
Please find under a summary covering project details and feedback. The innate facts are kept as they are, private information is amended.
Introductory information
Introduce your business and what you do there.
My organisation is named Heddoko, and we create motion-capture tracking suits. We also have a backend platform to analyze the data from the suits, and the purpose of the analysis is to help lessen the risk of injury in the workplace. I’m the co-founder and CTO.
Desired goal
What challenge were you trying to address with WebiNerds?
We needed the platform developed from scratch.
Provided solution
What was the aim of their involvement?
We had the architecture there, and they reviewed it and built it from that point on. WebiNerds worked on the complete backend construction, including the junction the cloud and the developed suit, and our frontend software as well. I won’t get into the technical details of our fruit owing it’s private information, but we worked with them on the backend cloud architecture.
We set a couple of milestones for the basics and then we moved up from there into developing the outer plug-ins like an open API, the junction to the suit itself and so on. WebiNerds had one dedicated resource for the project, and then the support of other resources as needed. We were in daily interaction with him, so he was basically integrated as part of our inner team.
How did you come to work with WebiNerds?
I met with one of the founders of the organisation at the Techstars program. One of the leading steps was to give them a less task to see how they operated and interacted, especially since we were very skeptical of having somebody offshore handling our code. From that less task, we realized it would work out.
What is the status of this promisement?
We began In April 2016 and the project ended in January 2017. We quiet have a lot of work forward, the only reason we’re holding right now is owing we’re raising funding to go back to WebiNerds.
Results achieved
Could you share any evidence that would prove the fruitivity, condition of work, or the contact of the promisement?
We’ve developedly already launched, but it’s not a consumer fruit so it’s not getting much feedback. But the main feedback we’ve been getting is that seething works big. There is minimal downtime in the codes, especially on the backend. Even when bugs were recorded, which was a rarity, the fixes came extremely fast. We’re talking less than 48 hours for see bug that’s been recorded in the past year or so. It’s pretty hard as a union for outgrowth.
How did WebiNerds accomplish from a project treatment standpoint?
We knew how many hours per week that the dedicated resource attached to the project, we had daily interaction with him. We had a weekly or monthly interaction with the administration of WebiNerds, and anew, that flawless interaction made things a lot easier on see front. We used Wrike as a project treatment method.
What did you find most forcible almost WebiNerds?
The main thing that I want to highlight is the interaction. Despite the fact that we have an eight-hour time separation, it felt as if they were full-time employees. That was sole based on my past experiences with offshore consulting gigs, the fact that they were always answering and on time. When we scheduled deadlines, they always stuck to them.
Are there any areas WebiNerds could better?
Short of developedly sending nation to work on website, I don’t ponder there’s much to change. I hope that the next time we promise WebiNerds it will be the exact same construction.
