Overall Review Rating
4.3 (5 Ratings)
Overview
Melon is a software development company based in Bulgaria. They are exceptionally good in app development teams that approximately match their clients’ needed technological skillset and experience. They are especially good at developing teams that closely match their clients’ demands technological skillset and experience.
Services
- Mobile App Development
- iPhone App Development
- ERP Development
- Logo Designing
- Game Development
- Cloud Provisioning Services
- Web Development
- Ethereum Blockchain
- CMS Development
- Cross Platform Development
- Android App Development
- iOS App Development
Industries Served
Melon Reviews
Have a look at these client reviews on previously delivered projects.
Fiona MacPherson
Operations Director - Highland Analytics LtdSmooth launch, great reviews, no embarrassing bug reports from users in the first month
What set this team apart in practice was their engineering judgment — specifically, their willingness to tell us when our requirements were wrong and explain what to do instead. Not every vendor does that. The consultative element elevated the final output well beyond what our original brief described. We ended up with something better than what we had asked for, which is not a sentence I expected to be writing in a review.
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.
Tanya Wolfe
Senior Product Manager - Harbor Point ConsultingBlind spots in our operational data are gone. The ROI case wrote itself.
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
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.
Khalid Al-Mansoori
Director of Innovation - Emaar Digital GroupData science team is actually productive now. First time in two years.
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
Our agents were managing data across four disconnected systems. The time they spent on reconciliation was time not spent with clients. The ROI case for consolidation was obvious.
Kenji Watanabe
Senior Engineering Manager - Fuji Software CorpMultiplayer held through the launch spike we had underestimated. No downtime.
The platform has been live for six months and is handling three times the transaction volume we scoped for. That is not because we underestimated — it is because the architecture choices made during discovery were genuinely forward-thinking. Most vendors design for exactly what you tell them. This team designed for what you are likely to need. We are already scoping the next phase and there was no question about who we would use.
Project summary
A licensing agreement required us to demonstrate GxP-compliant data management to a partner's satisfaction. Our existing infrastructure failed that assessment.
Erik Lindqvist
Chief Technology Officer - Nordic Cloud ABQA coverage that finally made Friday deployments a professional activity
The part of this project I had been most worried about was the integration work. Our system landscape is complex, some of the upstream APIs were barely documented, and one of our third-party vendors was notoriously slow to respond. This team documented what the upstream vendors could not, built resilience into the architecture where third-party reliability was uncertain, and delivered integrations that have worked exactly as specified since day one. I genuinely could not have asked for more.
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.