Add a new feature that uses new data, and encrypt that data. Not an insurmountable obstacle, but it will put you ahead of him in the comparisons on the app store as long as you can stay ahead.
But he can do the same thing to you.
In the end, the users win. That's the beauty of a platform that has critical mass in numbers of developers competing to make good apps. Sucks for you (us) unless you look at it as a fun challenge.
Comments
Good idea — well.. good advice for next time, anyway.
Add a new feature that uses new data, and encrypt that data. Not an insurmountable obstacle, but it will put you ahead of him in the comparisons on the app store as long as you can stay ahead.
But he can do the same thing to you.
In the end, the users win. That's the beauty of a platform that has critical mass in numbers of developers competing to make good apps. Sucks for you (us) unless you look at it as a fun challenge.
put false values in it yourself, if you notice them in the other app then he copied your database
Amusingly, (old-school, paper) mapmakers would do this, partly to defend against these problems.