Divante
Overall Review Rating
4.7 (8 Ratings)
Overview
Divante is a great mobile app development company. They have many years of experience and know-how in the mobile, digital & interactive industry; an inherent sense of the marketplace. They are an award-winning digital interactive company based in Munich. Truly they offer full solutions, from concept to development.
Services
- Ionic App Development
- DevOps & Cloud
- Mobile App Development
- MVP Development
- Cross Platform Development
- Android App Development
- Web Development
- Cloud Provisioning Services
- iOS App Development
- Node.js Development
- E-commerce Development
- Machine Learning
Industries Served
Divante Reviews
Have a look at these client reviews on previously delivered projects.
Danielle Westbrook
Chief Digital Officer - BlueSky Retail HoldingsFirst ERP implementation in our company's history that did not require emergency remediation
Three months post-launch our key metrics are all moving in the right direction — user adoption ahead of target, support volume down, time-on-task reduced for our core workflows. The product team has started planning features that were never viable on the previous platform. That is the real proof of the investment: it opened up possibilities rather than just replacing what was there before.
Project summary
Accessibility compliance requirements had changed. Our current platforms failed the new benchmarks and our legal team had given us a clear timeline to address that.
Kenji Watanabe
Senior Engineering Manager - Fuji Software CorpSales visibility we had requested for three years, delivered in fourteen weeks
What I appreciated most was that they were honest when things were not going to plan. There was one point mid-project where a dependency was going to affect our timeline and they told us three weeks before it would have become critical. That gave us time to adjust. Vendors who manage upward proactively are rare. This one did it consistently throughout the engagement.
Project summary
The business case had been approved but the internal resource to execute it had not materialised. External delivery was the pragmatic solution.
Sabrina Vollmer
Chief Innovation Officer - Rheintal Digital AGUser research surfaced friction points we had stopped noticing. Eye-opening.
Three months post-launch our key metrics are all moving in the right direction — user adoption ahead of target, support volume down, time-on-task reduced for our core workflows. The product team has started planning features that were never viable on the previous platform. That is the real proof of the investment: it opened up possibilities rather than just replacing what was there before.
Project summary
B2B customer churn was concentrated in accounts that rated our self-service portal poorly. A redesign was necessary before the next wave of contract renewals.
Radosław Kowalczyk
Head of Development - Wisła Software Sp zooThe outcome we needed, on the timeline we needed it, by people we would use again
Three months post-launch our key metrics are all moving in the right direction — user adoption ahead of target, support volume down, time-on-task reduced for our core workflows. The product team has started planning features that were never viable on the previous platform. That is the real proof of the investment: it opened up possibilities rather than just replacing what was there before.
Project summary
A failed engagement the previous year had made us more rigorous about vendor selection. We took the time to find a partner we actually trusted before we committed.
Kelsey Drummond
Director of Digital Health - Crestline Health PartnersERP went live on the agreed date. Those of you who have been through ERP projects understand.
We have worked with a few agencies over the years and the comparison is honestly not close. What stood out from the start was that they spent serious time understanding the problem before they proposed anything. Once development started, every sprint review was clean — no hidden surprises, no slipped milestones. The production system has been running for four months without a single critical issue. Our internal developers reviewed the codebase at handover and were genuinely complimentary about the quality. That does not happen often.
Project summary
Open banking changes required us to rebuild our API layer properly — compliant by design, not patched together. We needed specialist engineers, not generalists.