How does reverse engineering an app work, and where does AI come in?

November 16, 2026 4 answers
Asked by _g91+marblewidget.4

When someone recreates an app or one of its features, how do they figure out how it works? Are they inspecting network traffic and decompiling code, or can AI do much of that work for them?

Answers

c.918+lanternfox

First, copying what an app does is not necessarily the same as figuring out how it was built. You can watch a feature, try different inputs, record the outputs and build something that behaves similarly. The new version might have completely different internals.

Reverse engineering can go deeper. Depending on the target, that might mean examining a compiled program, tracing its execution, looking at file formats or inspecting traffic between components. The method depends on the question you are trying to answer.

_g91+marblewidget.4:

So a convincing recreation doesn't necessarily mean anyone recovered the original source code?

_v46~tethercoil.8:

Exactly. Matching visible behavior and recovering an implementation are different goals.

Reply to this answer
_c74~signalfeather.5

For a web app, browser developer tools are a useful starting point. You can inspect the page, the JavaScript delivered to the browser, and requests and responses as you use a feature. That can reveal data formats and which calls the client makes, but it doesn't give you the server's source code.

For a compiled app, a disassembler or decompiler can help you explore the binary. A decompiler produces an approximation of higher level code, not necessarily the original source. You can combine that with debugging, file inspection and traffic analysis to test ideas about what the program is doing.

b.904~parcelchisel:

And a network capture is only one view. It won't necessarily explain what the server does with a request after it receives it.

Reply to this answer
Veslora.6m

AI is more like an assistant than a magic extractor. You can give it a small piece of decompiled code, a data sample or a description of observed behavior and ask for possible explanations. It can also help draft a test or a prototype that reproduces a feature.

Then check the result against the actual program. Models can confidently invent details, misunderstand code or miss edge cases. They can't infer hidden server logic reliably just because the interface looks familiar.

Reply to this answer
9k~hingeparcel_305

For practice, pick an open source application and a small feature. Try to describe its behavior first, then compare your understanding with the source and build a simple version of your own. That gives you a way to check your guesses without starting with a huge opaque application.

Do pay attention to the license and applicable laws. Access to code doesn't automatically mean you can copy it, and reverse engineering isn't automatically legal in every situation.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions