{"id":2717,"date":"2013-03-01T11:29:15","date_gmt":"2013-03-01T19:29:15","guid":{"rendered":"http:\/\/manytricks.com\/blog\/?p=2717"},"modified":"2015-09-06T06:57:26","modified_gmt":"2015-09-06T13:57:26","slug":"how-not-to-compete-in-business","status":"publish","type":"post","link":"https:\/\/manytricks.com\/blog\/?p=2717","title":{"rendered":"How not to compete in business"},"content":{"rendered":"<p class=\"stickynote\">Late in the day on March 1st, we <a href=\"\/blog\/?p=2717&#038;cpage=1#comment-13058\">received an explanation\/apology<\/a> from Dietmar Kerschner.<br \/>As far as we&#8217;re concerned, the personal side of this matter is now closed.<\/p>\n<p>Two days ago, we launched <a href=\"\/namemangler\">Name Mangler 3<\/a>, our first major upgrade to the program in nearly three years. This update was user-driven, based on feedback we&#8217;ve been tracking since Name Mangler 2 came out. We focused on speed, the ability to perform more than one renaming action, and some user interface improvements. We&#8217;re incredibly proud of what we built, and have been thrilled with the initial reaction.<\/p>\n<p>Then yesterday, out of the blue, we received an email claiming we&#8217;d violated the copyright of another renaming application. We spent the afternoon researching the other app, and eventually sent an email response back to the accuser, clearly demonstrating our innocence through screenshots and app release timelines. (Name Mangler has existed in pretty much its current form since its initial debut as File List, way back in 2005.) <\/p>\n<p>We thought that would be the end of it, because it was obvious there was no infringement. Today, though, we discovered that our accuser has gone public (despite not replying to our email) with these tweets:<\/p>\n<p><img decoding=\"async\" src=\"\/blog\/wp-content\/uploads\/2013\/03\/dietmar_tweets.png\" class=\"aligncenter\"><\/p>\n<p>Now that we&#8217;re being called thieves in a public forum, we feel we must respond in public as well: we cannot let Dietmar Kerschner trash our hard-earned reputation with baseless accusations that can&#8217;t withstand even the most basic level of scrutiny. <\/p>\n<p><a href=\"\/namemangler\/history\">A Brief History of Name Mangler<\/a> presents our side of the story. There you&#8217;ll find details on the development of Name Mangler, and that of Renamer(4Mac), the program whose designer has accused us of copyright infringement. Even a quick glance at the page will show that we&#8217;ve copied nothing from Renamer&mdash;if anything, we could claim that their latest release copied our design.<\/p>\n<p>The purpose of this blog post, though, isn&#8217;t to go through a comparison of the two apps. Instead, we&#8217;d like to focus on the impact baseless copyright violation accusations have on both developers and (potentially) end users.<\/p>\n<p><!--more--><\/p>\n<h3>The threat<\/h3>\n<p>This is the threatening email we received from Dietmar Kerschner:<\/p>\n<blockquote><p>To whom it ma concern<\/p>\n<p>I am Dietmar Kerschner, the UI\/UX designer of Renamer 4. You have choosen to steal my UX concept for namemangler 3 which is a breach of copyright which i own.<br \/>\nIt is abvious that you have stolen every part of the concept of Renamer 4, which i have concepted years ago.<br \/>\nI will not accept such copyright abuse.<\/p>\n<p>Please explain the situation and give a statement, otherwise i will have to forward this case to my lawyer.<br \/>\nYou also would risk another abusement case which can be forwarded to incrediblebees laywers. <\/p>\n<p>I recommend to act fast.<\/p>\n<p>Cheers<br \/>\nDietmar Kerschner<\/p><\/blockquote>\n<p>The above is reproduced verbatim, typos and formatting and all. <a href=\"\/blog\/wp-content\/uploads\/2013\/03\/challenge_letter.png\">Here&#8217;s the actual email message<\/a>, in case you think we might be making this up. Trust me, we wish we were.<\/p>\n<h3>Our response<\/h3>\n<p>Needless to say, this email made us extremely angry: we have never stolen a UI concept\/design from anyone, ever, and we work incredibly hard on our user interfaces. There are literally thousands of hours of design work and rework in Name Mangler 3&#8217;s user interface, and all of it was done internally, without ever looking at our competition.<\/p>\n<p>We spend hours sweating the tiniest of details, often having pages-long Messages conversations about a one-pixel alignment decision. We care about this stuff, and we think it shows in the quality of our applications. So to be accused of interface theft hits us deeply, and it hurts, even when such accusations are false.<\/p>\n<p>But what really got us mad was wondering how often this type of thing goes unnoticed and unmentioned, and the receiver of such a letter simply gives in under the threat of legal action.<\/p>\n<h3>Impact on developers<\/h3>\n<p>Between the two of us, we&#8217;ve now spent the better part of a full day on this project, gathering historical data for File List\/Name Mangler (very easy, as we keep everything) and Renamer (much harder, given the name and ownership changes, and the lack of any sort of release notes) and preparing our response to Dietmar.<\/p>\n<p>We&#8217;ve been Googling and taking screenshots and generally wasting time, proving something that we knew to be true going in. We called on friends in the software development business, to make sure we weren&#8217;t overlooking something about our work that could lead to a copyright infringement claim. We reached out to fellow Mac developers, asking for their thoughts on the situation.<\/p>\n<p>All of these things take time, and time is our most precious commodity. This is time that we could&#8217;ve been using to code, to respond to customer inquiries, to visit with family and friends, etc. All that time wasted, because of one threatening letter. And we took the time to respond. Imagine a smaller developer, with a greater fear of legal action. Instead of responding, they may start spending hours changing their app&#8217;s appearance&mdash;all for no reason at all, beyond a threatening letter.<\/p>\n<p>We love the software business, we love developing excellent products, and we love fair competition between developers: end users benefit greatly when two or more companies are building apps that do similar things. But trying to smother the competition with a baseless copyright violation claim? That&#8217;s not how we play, and we don&#8217;t think it&#8217;s how the software business should work.<\/p>\n<h3>Impact on end users<\/h3>\n<p>You may think a developers&#8217; debate over copyright violations has no impact on end users. And if your timeframe is very short, you&#8217;d be right. But in a slightly longer run, time that developers waste on needless tasks takes away from the time they have to spend supporting end users, to write cool new apps, to update old apps, etc.<\/p>\n<p>In addition, every time a copyright violation accuser forces an unwarranted change in an application, they&#8217;re affecting the user experience. If an app is forced away from an ideal layout because someone claims it&#8217;s &#8220;theirs,&#8221; that&#8217;s not good for users.<\/p>\n<p>Threats may also dampen a developer&#8217;s enthusiasm for developing in general; after all, it&#8217;s no fun to spend hours defending your actions under threat of legal action. Irk a developer enough, and they may just decide it&#8217;s not worth the hassle, leading to fewer applications available for end users.<\/p>\n<h3>Wrapping it all up<\/h3>\n<p>Are we arguing that copyright is unimportant, and developers should be free to steal from other apps without any negative effects? Certainly not. Copyright is very important, and violators should be called to the mat for theft.<\/p>\n<p>In this case though, we&#8217;ve demonstrated that not only did we not steal, but that any theft may have very well been the other way around: Renamer 4&#8217;s &#8220;new&#8221; interface bears a striking resemblance to one we&#8217;ve been using since 2005. But honestly, we don&#8217;t care&mdash;we like competing on features, performance, and ease of use instead of with legal threats.<\/p>\n<p>So what happens next in this dispute? We have no idea. In an idealized world, Dietmar realizes that he&#8217;s wrong in his assumptions, and sends us his apologies for making a false accusation. The chances of that happening, though, are close to zero.<\/p>\n<p>What we hope is that through exposing Dietmar and his threatening but groundless copyright violations email, he&#8217;ll think twice before trying such an approach on other developers. This business is hard enough as it is without having to worry about such underhanded tactics.<\/p>\n<p class=\"stickynote\">Late in the day on March 1st, we <a href=\"\/blog\/?p=2717&#038;cpage=1#comment-13058\">received an explanation\/apology<\/a> from Dietmar Kerschner.<br \/>As far as we&#8217;re concerned, the personal side of this matter is now closed.<br \/>Because we view the issue as closed, we&#8217;ve closed the comments.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Late in the day on March 1st, we received an explanation\/apology from Dietmar Kerschner.As far as we&#8217;re concerned, the personal side of this matter is now closed. Two days ago, we launched Name Mangler 3, our first major upgrade to the program in nearly three years. This update was user-driven, based on feedback we&#8217;ve been [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[3,7,4],"tags":[],"coauthors":[21,22],"class_list":["post-2717","post","type-post","status-publish","format-standard","hentry","category-company-news","category-name-mangler","category-products"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/manytricks.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2717","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/manytricks.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/manytricks.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/manytricks.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/manytricks.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2717"}],"version-history":[{"count":49,"href":"https:\/\/manytricks.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2717\/revisions"}],"predecessor-version":[{"id":3486,"href":"https:\/\/manytricks.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2717\/revisions\/3486"}],"wp:attachment":[{"href":"https:\/\/manytricks.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2717"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/manytricks.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2717"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/manytricks.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2717"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/manytricks.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcoauthors&post=2717"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}