4 ms·
Have you considered encrypting your database, so that only your app can make sense of it? That's what a friend of mine used to do, and it indeed stopped some s
by Luyt 17y ago
Have you considered encrypting your database, so that only your app can make sense of it? That's what a friend of mine used to do, and it indeed stopped some superficial copying.
- Padraig 17y agoGood idea — well.. good advice for next time, anyway.
- nudded 17y agoput false values in it yourself, if you notice them in the other app then he copied your database
- angelbob 17y agoAmusingly, (old-school, paper) mapmakers would do this, partly to defend against these problems.
- natch 17y agoAdd 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.
- rbanffy 17y agoA better solution would be hosting it online and then caching it on the client. With the added benefit of bring able to tell when someone else accesses your content by failing to supply a special request header. I would start by trying to talk to him. If that didn't work, I would call his school and make them aware of their student's shady doings. Then I would go to Apple and point out Apple is helping this guy to infringe on your copyright (the database is comprised of public data, but your work compiling it is non-trivial). If the data were kept on-line and cached in the client, you could, as a final step of escalation, render his app useless. Or worse: make it supply wrong routes.