How to Look Inside an Android App You Installed

In the reel I took the Duolingo Android app apart to see how it gets so many people to come back every day. Inside there was a folder called churn, a number for how likely you are to return tomorrow, and a notification type the code itself calls passive aggressive.

From the outside, an app's growth design looks like magic or manipulation, depending on your mood. From the inside, it is mostly a list of names, numbers and copy that someone on a team wrote down. This is how to look at that list for any Android app you have installed, with two free tools, and how I read it as a designer. The Duolingo details below are what version 6.100.3 showed in October 2026. Newer versions are already out, so treat them as a snapshot.

What you need

A computer and about an hour. On a Mac, Homebrew installs all three tools:

brew install jadx apkeep
brew install --cask android-platform-tools

jadx turns an Android app back into readable Java and decodes its resources. apkeep, from the EFF, downloads app files. The platform tools give you adb, to talk to your own phone. On Windows or Linux, both GitHub pages list other ways to install.

Step 1. Get the APK

The cleanest way is to copy the app from your own phone, since you already installed it from the store. Turn on Developer options by tapping Build number seven times in About phone, then turn on USB debugging inside Developer options, as the Android developer docs describe. Plug the phone in, approve the computer on the screen, and ask the phone where the app lives:

adb shell pm list packages duolingo
adb shell pm path com.duolingo

You will usually get several paths back. Apps on Google Play ship as a base APK plus configuration APKs, split by things like screen and language. Pull every one of them with adb pull and the path. The base APK holds the code; the rest add resources for your device.

No Android phone? apkeep can download an app by its package name. In the reel I used it with the APKPure mirror:

apkeep -a com.duolingo -d apk-pure .
apkeep -a com.duolingo@6.100.3 -d apk-pure .

The second line fetches a specific version, and apkeep -l -a com.duolingo -d apk-pure lists the ones available. apkeep's own README says the APKPure source should be used only for research. Its default source is Google Play itself, which needs your Google email and a token, and the README warns that Google may close an account for it. I would not use an account I care about.

Whichever way you get it, never install a copy that came from a mirror. You only want to read it.

Step 2. Open it with jadx

For browsing, jadx-gui opens a window where you drop the file in and search everything. For grepping in a terminal, decompile it to a folder:

jadx -d out base.apk

jadx reads APK, XAPK and the split formats too. It will finish with a few errors, and that is normal. Its README says it can't decompile 100% of the code in most cases.

You get two folders. out/resources has the manifest and every resource file. out/sources has the code. Most class names in there will be scrambled into short names like gg7, because apps shrink and rename their code before release. Text survives that: string values, resource names, analytics events and the values inside enums. So you search for words, not classes.

Step 3. Know where to look

After a few apps, the same places always pay off:

  • res/values/strings.xml, and the same file in folders like values-es, holds the copy the app shows. Notification text, widget lines, empty states, and every variant of a reminder sit next to each other with their internal names.
  • AndroidManifest.xml lists permissions, widgets, background receivers and alternate entry points. An app that can change its own icon usually declares each version as an activity-alias here.
  • Notification logic lives in classes and enums with names like NotificationType, TriggerType or channel. Search for notification and read the enum values first.
  • Experiments and remote flags are strings the app sends to or reads from a server. Search for experiment, treatment and control, and expect each company to name them differently.
  • Analytics events show what the team measures. Search for event-like keys such as entry_point or _tap.

grep -rn "streak" out/ is a fine start. Pick words from the app's own screens and follow them.

What Duolingo 6.100.3 showed

Everything below is what the reel covered, in my own words.

  • A package called churn stores a latest and a previous tomorrow probability, each with its record date. In other words, a number for how likely you are to come back tomorrow.
  • A reward check labeled churn_reward includes that number being above 0.5, next to other conditions, before it can give you a free streak freeze.
  • Every app open records where you came from: a notification, the widget or the launcher. It also logs how many answers you got wrong and whether the app crashed since the last time you opened it.
  • The app builds a fingerprint of the network you are on, hashing the gateway and DNS addresses with SHA-256, and counts the days it has seen that network. There is a notification trigger called WIFI, used for practice reminders on a familiar network.
  • A list of display names lets the app rename its own icon, from plain Duolingo to versions like Duolingo ⏰ and Duolingo 🚨 when you have not practiced.
  • One notification type is literally called PASSIVE_AGGRESSIVE, and it can trigger a one-time "unhinged" app icon update, with a crying icon among the resources.
  • The widget has a state called GHOSTING_ME.

Reading it as a designer

Start with the numbers. A threshold of 0.5, a count of days on a network, a delay before a reminder: those are decisions someone argued about. Write them down before you read any copy.

Read the copy as a ladder. Put every variant of one reminder side by side and you can see how the tone escalates, and where the team decided to stop.

Listen to the names. churn, PASSIVE_AGGRESSIVE and GHOSTING_ME tell you how the team talks about you when you are not in the room. That is useful, and a little uncomfortable.

Don't read too much into it. Code that exists can sit behind an experiment that is switched off for you. A value that is logged is only logged, unless you can see the code that uses it. Say what the code says and stop there.

From Duolingo I copied two things into my own apps: measuring who comes back, and knowing when the app failed someone. The network fingerprint I left alone.

What is fine and what is not

Studying an app you installed, for yourself, to learn how it works, and then describing the mechanics in your own words is how a lot of designers and security researchers learn, and it is the part I am comfortable teaching.

Republishing their code or their assets is not fine. Neither is sharing the APK, using what you find to unlock paid features, calling their private APIs, or pulling keys out of the resource files. If a finding only works by taking something, leave it.

Duolingo's terms of service forbid reverse engineering or decompiling its apps, and plenty of other apps say the same. Studying quietly still breaks that contract, and the realistic risk is to your account. It grows the moment you publish. That is why this article describes what I saw instead of reprinting it. I am not a lawyer, and if your work depends on this, ask one where you live.

← All posts