Groove Jones
Overall Review Rating
4.1 (7 Ratings)
Overview
It is a studio specializing in the production of immersive AR and VR content and winning interactive applications. They have produced award-winning plugs, developed some of the world’s most connected mobile apps and transported people into VR for global brands. They are fearless and our strategy is solid.
Services
- MVP Development
- 3D & Interior Design
- Cross Platform Development
- Digital Strategy Management
- iOS App Development
- Chat Bots & AI Development
- Android App Development
- AI Development
- Mobile App Development
- Drupal
- Motion Graphics
- Web Development
Industries Served
Groove Jones Reviews
Have a look at these client reviews on previously delivered projects.
Nora Al-Otaibi
VP of Engineering - Salam Digital SolutionsComplex project, zero drama. That is how you know the project management is real.
We went with a smaller team than we had originally planned for. I had concerns about whether the capacity would be sufficient given our timeline. Those concerns were unfounded. The team was focused, communication was constant, and the quality at each milestone review was consistent throughout. Smaller does not mean slower when the people are the right ones and this engagement proved that.
Project summary
Our field service scheduling ran on a system that predated smartphones. Technician productivity was suffering and customer satisfaction scores reflected it.
Lars Pfeiffer
VP of Technology - NordTech Logistik GmbHPerformance testing caught a latency issue three weeks before our biggest traffic event
The technical quality is the obvious thing to highlight. The automated test suite is comprehensive, the deployment pipeline is solid, and the documentation is actually useful rather than written to satisfy a checklist. But the metric I keep coming back to is what has NOT happened since go-live. No 2am incident calls. No emergency patches. No post-launch retrospectives about what went wrong. For a system of this complexity, that outcome is exactly what we paid for.
Project summary
Streaming quality issues were generating subscriber churn at a rate that made the technical investment case straightforward to approve.
Julien Moreau
Co-Founder & CTO - TechLyon SASFrame rate consistent across all target devices from day one. Testing confirmed it.
The knowledge transfer at the end of the project was notably good. Too many vendors see handover as a tick-box exercise. This team ran structured sessions, produced documentation our internal team actually references, and spent real time making sure we understood the architecture decisions well enough to maintain and extend the system independently. Six months later we are doing exactly that without needing to go back to them for every question.
Project summary
Our internal team was committed to maintenance and could not absorb a new build of this complexity. An external partner was the only way to hit the timeline.
Rupert Ashford
Director of eCommerce - Hargrove Retail PLCCustom modules that fit our processes rather than forcing us to change them
Our stakeholder group was unusually broad — board sponsors, operational users, compliance leads, and an IT team with strong opinions. I have watched vendors handle that kind of environment badly. This team adjusted how they communicated depending on who they were talking to, managed expectations honestly when things shifted, and delivered something that each group considers a success. Getting everyone to agree on that outcome was not straightforward and they deserve credit for making it happen.
Project summary
Our product thinking was strong. Our execution capacity in this specific domain was limited. We needed deep expertise, not a generalist willing to learn on our time.
Tariq Al-Harbi
Director of Technology - Saudi Cloud HoldingsIT partner that understands our business, not just our ticket queue
Honestly, I came into this engagement with some scepticism. We had a bad experience with a vendor twelve months earlier and I wanted to see evidence of competence, not just hear about it. The discovery documentation was the first signal. The sprint delivery consistency was the second. By go-live I had stopped being sceptical and started planning how to expand the engagement. The production system has been stable from day one and our internal team loves working with the codebase they left us.
Project summary
A new practice area required document management workflows that did not exist in our current system. We needed them in place before the first client matter opened.