The world of magic apps is still relatively small. Developers know one another, creators follow each other’s releases, and similar ideas can quickly lead to tension.

A recurring belief within this community is that publishing an app first gives its creator permanent ownership of the underlying method. According to this reasoning, once a magician releases an application based on a particular principle, nobody else should be allowed to create anything similar without first obtaining permission.

But releasing an app before someone else does not automatically give you ownership of an entire method, concept or category of effects.

Being first may deserve recognition. It may establish commercial or historical precedence. It may even prove that a particular product existed on a certain date. However, it does not necessarily create an exclusive legal right over the general idea behind that product.

An idea is not automatically protected

Imagine that a magician releases an app that secretly reveals information entered by a spectator.

Several years later, another developer creates a different application that achieves a comparable result. The second developer writes new code, creates a different interface, uses a different technical process and presents the effect through an entirely different routine.

The original creator can truthfully say:

“My application was released first.”

What they cannot automatically conclude is:

“Therefore, I own every possible method of secretly obtaining information from a spectator’s phone.”

Under French and European intellectual-property principles, copyright protects the concrete expression of a creation, not an abstract idea or general concept. The French National Institute of Industrial Property, or INPI, explicitly distinguishes ideas from the specific form in which those ideas are expressed.

European rules concerning computer programs make the same distinction. The expression of a program may be protected, but the ideas and principles underlying its elements—including those underlying its interfaces—are not protected by software copyright.

In practical terms, someone may own the original code, artwork, text and other protected elements of an application without owning the broad idea of producing a particular magical effect with a smartphone.

Publishing first is not the same as holding a patent

Another common misunderstanding is that releasing an app somehow creates an informal patent.

It does not.

A product does not become patented merely because it is available on the App Store, Google Play or a magician’s website. A patent requires an actual application and must satisfy specific legal requirements.

In France, for example, a patentable invention must be new, involve an inventive step and be capable of industrial application.

Software-related inventions present additional complications. Software as such is primarily protected through copyright, although certain computer-implemented inventions may potentially qualify for patent protection when they meet the relevant technical and legal requirements.

This means that a creator cannot simply declare:

“I released this type of magic app first, so nobody else can ever use a similar principle.”

Without a valid patent, contract, licence, confidentiality agreement or another identifiable legal right, commercial precedence alone does not necessarily create a monopoly over a general method.

The precise legal position can vary between countries and individual cases, but publication alone should never be confused with automatic ownership of every related idea.

What can actually be protected?

None of this means that copying another creator’s work is acceptable.

There is a major difference between independently using a general principle and directly reproducing someone else’s product.

An app’s original source code may be protected by copyright. Its graphics, written material, photographs, videos, sound effects, tutorials and other original content may also receive protection. Software and various creative assets can benefit from copyright from the moment they are created, subject to the applicable legal conditions.

The name and logo of an application may also be protected as trademarks. Copying a distinctive identity in a way that creates confusion is very different from independently developing another product based on a comparable general idea.

There may also be contractual obligations. A developer who receives confidential information through a partnership, private demonstration, development agreement or non-disclosure agreement cannot necessarily use that information freely.

Therefore, several elements must be separated:

  • The general magical effect
  • The abstract principle or idea
  • The precise secret method
  • The source code
  • The interface and visual presentation
  • The name and branding
  • The script, instructions and performance material
  • Confidential information received through a private relationship

These elements do not all receive the same type or level of protection.

Using the same broad concept is not necessarily the same as copying the same implementation.

Magic methods existed before smartphones

Digital magic did not begin with the iPhone.

Long before smartphones existed, magicians were already using forces, secret inputs, peeks, coded communication, mathematical principles, multiple outs, indexes and hidden information systems.

A modern app may adapt one of these ideas to a digital environment. It may make an old principle more convenient, more deceptive or easier to perform. It may combine several existing concepts in an intelligent new way.

However, adapting a principle to a smartphone does not always mean inventing the entire principle from nothing.

For example, obtaining secret information from a spectator is not a category that belongs to one person. Predicting a word, revealing a drawing, forcing a choice or secretly controlling an outcome are broad magical objectives that existed long before mobile applications.

A developer may create an original and brilliant implementation of one of these effects. That originality deserves recognition. But it does not necessarily give that developer ownership of every future application producing a similar result.

Independent creation is possible

Similar products do not always result from copying.

Two creators may independently arrive at comparable solutions, especially when they are trying to solve the same problem with the same type of device.

Smartphones have cameras, microphones, notifications, web browsers, sensors, wireless connections, accessibility features and touchscreens. When several developers explore these capabilities for magic, some overlap is inevitable.

The number of practical ways to accomplish a particular effect may also be limited. If several people are trying to reveal a secretly entered word, they may naturally explore similar categories of solutions.

A resemblance between two apps is therefore not, by itself, proof of theft.

Before making an accusation, it is important to examine the details:

Was the source code copied?

Was the interface reproduced almost identically?

Were the same graphics, texts or instructions used?

Was confidential information taken from a private demonstration?

Was the second creator genuinely aware of the first product?

Is the precise method identical, or do the apps merely produce a similar effect?

Does a patent, contract, licence or other enforceable right actually exist?

Without examining these questions, claiming that someone has “stolen a method” may be premature and unfair.

Law and professional courtesy are not the same thing

This is where the discussion becomes more subtle.

Even when a creator does not have an exclusive legal right over a general method, contacting them may still be the respectful thing to do.

If you know that another magician released a closely related product before yours, introducing yourself and explaining your project can prevent misunderstandings. It can create an opportunity to compare the two products, acknowledge previous work or even establish a collaboration.

That is professional courtesy.

But courtesy should not automatically be interpreted as an admission of ownership.

Contacting another creator does not necessarily mean asking for permission to exist. It may simply mean showing respect, behaving transparently and avoiding unnecessary conflict.

The distinction is important:

Recognition is not ownership.
Courtesy is not permission.
Being first is not the same as holding exclusive rights.

Courtesy must also work in both directions.

A new developer should respect the work of earlier creators. At the same time, an established creator should not use their reputation or seniority to claim ownership over an entire family of effects.

Respecting pioneers without freezing innovation

Being first still matters.

A magician who introduces an original use of smartphone technology may deserve to be recognised as a pioneer. That creator may have opened a new category, influenced future products and demonstrated that a particular concept could work in performance.

Acknowledging that contribution is fair.

However, recognising someone as a pioneer does not mean granting them permanent control over everything that follows.

Innovation rarely develops in complete isolation. New products often improve existing principles, combine familiar ideas or approach known problems from a different direction.

This is true in technology, design, filmmaking, music and magic.

Several apps may offer note-taking, photo editing, navigation or messaging without one developer owning the entire category. In the same way, several magic apps may use a phone to force information, reveal a thought, transmit a secret or create a prediction.

What matters is how each product is built and what it contributes.

Does it offer a genuinely different method?

Does it improve reliability?

Does it create a more natural performance?

Does it use technology in a new way?

Does it introduce a different presentation?

Does it solve a problem that existing apps do not solve?

Competition does not always damage creativity. Sometimes, it pushes every creator to build something better.

Accusations can damage reputations

The magic-app community is small, which means public accusations can have serious consequences.

Calling someone a thief can damage their reputation with customers, developers and other magicians. Such claims should not be made casually simply because two products appear to share a general concept.

Real copying should be challenged. Creators should be able to defend their code, branding, original content and contractual rights.

But developers should also be protected from exaggerated claims made by people attempting to privatise an abstract idea.

The fact that someone released an app in 2015 does not automatically mean that every remotely similar app released afterward is a copy.

Evidence matters. Details matter. The difference between an idea and its implementation matters.

A healthier culture for magic-app creators

A healthy creative community should protect original work without preventing independent innovation.

Developers should avoid copying another app’s code, graphics, written instructions, routines, branding or distinctive presentation. They should honour contracts and respect genuinely confidential information.

Creators should also give credit where credit is legitimately due. When a previous product directly influenced a new project, acknowledging that influence can be both honest and elegant.

At the same time, nobody should be able to claim indefinite ownership of a broad magical effect merely by saying:

“I did something similar first.”

A release date may establish chronology. It does not automatically establish invention, legal protection or exclusive ownership.

The best approach is built on balance:

Respect the original implementation.

Recognise genuine pioneers.

Do not directly copy protected work.

Communicate when two projects are especially close.

But do not confuse politeness with a legal obligation, and do not confuse precedence with ownership.

Magic has always evolved through experimentation, interpretation and reinvention. Digital magic should be allowed to evolve in the same way.

The future of magic apps will not be strengthened by fear, territorial behaviour or unsupported accusations. It will be strengthened by original development, fair competition, transparent communication and mutual respect.

This article discusses general principles and should not be considered legal advice. The applicable rights may vary depending on the country, the product and the specific circumstances.