When you put it in the app store, maybe you could say "copyright NIKEOW", or something if it bothers you, as that might make someone think about taking your idea and using it. Not sure there is anything legally you can do, but it might make someone PM you and ask before building a clone of your stuff...
When you put it in the app store, maybe you could say "copyright NIKEOW", or something if it bothers you, as that might make someone think about taking your idea and using it. Not sure there is anything legally you can do, but it might make someone PM you and ask before building a clone of your stuff...
putting the copyright wording would not make any difference I think.
I do however wonder what is Garmin's stand on this tho.
While I'm OK w/ the idea being used, it's not good to have the entire thing ripped like that. It's akin to the IOS Flappy Bird app which spanned so many clones.
With Garmin apps it is at least not that easy to copy other peoples work as for example in the Ambit App Zone, where to "source code" for each app is visible for everyone and people just copy it, change a multiplier or so and put it under their name. But what can you do? Maybe an independent user reviews it and mentions its just a copy of the original one?
I'm the person who developed RideData and would like to fully admit the app is a clone, with minor changes. I also acknowledge this fact on the app page. My motivation for making the app is because I wanted to see if I could make my own data field and started out with NIKEOWs as inspiration, as it was very close to what I had in mind. At the time, I wasn't aware of the fact that I could side-load the app on my Fenix and thought the only way to get it on my watch was to put it on Garmin Connect.
I'm more than willing to remove it from Garmin Connect, should you feel that that is necessary..
To elaborate a bit more: I also wanted to have more freedom on what fields would be displayed, e.g. I want to include heart rate zones. Also, I'm planning on making a data field with climbing info.
I think we all want to see competition in the app store because it benefits us all. Developers are pushed to make better apps, and become better developers in the process, and users reap the benefits of higher quality apps.
That said, a direct clone with minimal changes seems a little wrong. There's no value-add, and as developers we should be seeking to add-value to people's lives, not noise.
It's just my 2cents, but, ifanchi, I think you should temporarily pull the app until you can develop it into something a bit different from what's already out there. I definitely don't you think you should give up on it though, I'm sure there's a different spin you can put on it that'll make the app stand on its own.
I think we all want to see competition in the app store because it benefits us all. Developers are pushed to make better apps, and become better developers in the process, and users reap the benefits of higher quality apps.
That said, a direct clone with minimal changes seems a little wrong. There's no value-add, and as developers we should be seeking to add-value to people's lives, not noise.
It's just my 2cents, but, ifanchi, I think you should temporarily pull the app until you can develop it into something a bit different from what's already out there. I definitely don't you think you should give up on it though, I'm sure there's a different spin you can put on it that'll make the app stand on its own.
I've just pulled it off CIQ. Will continue to use for personal use :) Hope to learn more on this forum, so I can implement some features that set the app apart from NIKEOWs. Thanks for the advice.
I just wanted to say that everyone has been very polite, cooperative, and understanding with this. It's nice to see people working constructively together without name calling and bickering. Good show!
Just want to be clear and fair to ifanchi - as stated above in one of my replies - I'm OK w/ the idea usage. What I wasn't too OK w/ was that it was just a copy (exception on the way the timer is done)
As the app progressed, I can see that it is now supporting HR Zone (this is different - which is good) Also - I see the desc stating that it is aimed at doing ClimbData which would be excellent.
As it stands right now - there's not much (IMHO) that can be put into the DataFields already - given the current SDK // API available metrics. But then again - humans always surpises w/ ingenuity.
