Software Development for Sports Betting Startup
Please find below 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.
I’m the fobelow of a sports betting startup. We’re creating a software solution that will facilitate sports betting. At the instant, it’s just a data fruit, but we’re waiting to see how the legitimate landscape matures almost the question.
Desired goal
What challenge were you trying to address with WeDevelop?
We hired WeDevelop to form an MVP of our sports betting solution to obey as a test of concept. They’re responsible for both the design and outgrowth.
Provided solution
What was the aim of their implicatement?
WeDevelop is creating the MVP of our sports betting software. As with other forms of fast-paced trading, latency is a big hurdle in the betting marketplace owing we don’t want to have a user’s prices staggered behind real-time data. We needed to find a way to streamline the software so that it ran all of the information seamlessly without being clunky and slow.
Their team is focused on optimizing executement by implementing separate technologies to fix that we’re pushing out the data in real time. This implicates using WebSockets, messaging queues, and an appropriate browser that can run all of the information. The technology stack also includes React, GraphQL, PostgreSQL, and Node.js.
What is the team compound?
I mainly work with Abel (Co-Fobelow, WeDevelop) who leads the project. He’s backed by a UX/UI designer, a frontend developer, and almost two backend developers.
How did you come to work with WeDevelop?
My antecedent organisation hired Abel through Upwork, and I liked him a lot. He was hardworking and always genuinely tried to be pronimble almost issue-solving, which is rare for an outsourced developer.
What is the status of this promisement?
The project began in February 2018 and is ongoing. We have a soft deadline to propel our MVP in June 2019.
Results achieved
What evidence can you share that demonstrates the contact of the promisement?
We’re quiet in outgrowth, so it’s too soon to prepare any hard metrics yet. But, so far, I’m 100% satisfied with their executement. They do an excellent job.
How did WeDevelop execute from a project treatment standpoint?
It’s been an enjoyable, fruitive experience. This might sound unconventional, but I’ve asked WeDevelop to fracture down any interaction barriers between us, I wanted them to try to interface with me as if I were a part of their organisation, and Abel has gone to big lengths to make this request practicable. We use a ordinary Slack channel to chat, and I’ve also set up emails for them below my organisation’s estate, which they use excellently frequently. In provisions of the outgrowth process, they use an nimble methodology.
What did you find most forcible almost them?
Beyond appreciating what they’re almost, I like working with Abel and his team owing they’re pronimble. They’re ready to promise with a issue to aspect it out rather than waiting to be told what to do.
Are there any areas they could better?
No, I’m satisfied with their work so far. Although there is a time separation, they’ve put in a good effort to vanquish that.
