Zump Property

What a great idea showing boundaries , however upon review of several of my properties , they are inaccurate and should not be relied upon as totally inaccurate and could cause boundary disputes. This was feedback, with the response being, we got this data from land registry, but I’ve checked with land registry and the app is inaccurate , good idea showing boundaries but you need to remove a feature unless 100% otherwise this could open a hornets next of disputes if relied upon.

A lot of effort has gone into this great idea and it looks like you take UX really seriously. It feels like your engineering is at alpha stage in the background and you’re moving too quickly releasing something that promises lots and can’t cope. For instance scroll around the map and use the ‘search here’ function the app gets stuck in ‘working on it’ mode. If you close the app and open again you get a black screen because the backend is then unresponsive. The scary thing is if you open on any device without having logged in it’s also unresponsive, which means a user can kill Zump for all other users, just by using a feature. I think you need to shift the balance of spend of your funds away from UX and marketing and over to engineering or else you’ll leave early users frustrated, like me. I can’t believe the reviews on here are genuine either.

Genuinely think this is really clever. Used it a lot over the last few weeks to find places that you can’t get else where.