Global Citizen is the app behind a movement. You take actions on poverty, climate and equity — sign a petition, watch a briefing, answer a quiz — and those actions accumulate into campaign pressure, and sometimes into a ticket to the festival. It has been on both stores since 2016 and is used worldwide.
Client work. Clutch Developer does mobile engineering on this app as part of the team at L+R in New York. The app belongs to the Global Poverty Project.
What the app does
The core loop is deliberately small. Open the app, see today's actions, do one. Each action is a different content type — a petition, a video, a quiz, a share — and each has to feel like it takes under a minute.
- Today's Actions — a daily, editorially-curated feed rather than an algorithmic one.
- Campaigns grouped by cause, so a user can go deep on one issue instead of grazing.
- Rewards — actions earn entries to festival ticket draws, which is what converts a casual signature into a returning user.
- Live moments around the festivals themselves, when the app stops being a habit tracker and becomes an event companion.
The hard part
The traffic shape. Most consumer apps have a daily rhythm you can plan capacity around. A campaigning app has a flat baseline interrupted by enormous, scheduled spikes — a festival in Central Park, a broadcast moment, a celebrity post. Everyone arrives inside the same few minutes, many of them installing for the first time, all of them hitting the same content.
That changes what "correct" means on the client. Cold start has to be fast on a first install over stadium wifi. Content has to be swappable without shipping a release, because campaign copy changes the day of. Deep links from an email, a QR code or a social post have to land on the right screen even when the app was installed thirty seconds ago. And when something upstream is slow, the app has to degrade into something usable rather than a spinner — a first-time user who sees a blank screen during the one moment they cared does not come back.
What that demands
- Native on both platforms, because the spikes land on whatever device the crowd is holding.
- Server-driven content, so an editor can change the day's actions without an app release.
- Deep links that survive a cold install and route correctly on first launch.
- Localization, because a global movement is not an English-language movement.
- Graceful degradation everywhere — every screen needs an honest empty and error state.
If you are building something with the same shape — a long quiet baseline and a scheduled moment you cannot afford to fumble — the engineering worth paying for is not peak throughput. It is what happens on the slow path.