Retaining Users in Week Two
Week two is the first week the novelty is gone. The widget is not new. The permission sheet already happened. The user either has a reason to open the app for a job, or they do not. Retention work starts there. It does not start with a chart that celebrates day-one opens. This is how we talk about it at Croncode when we ship consumer iOS apps from Istanbul.
Week two retention is a second completed job, not a streak badge. If day one was a tour and day eight has nothing to finish, the user was never retained.
What is the job in week two?
Write the second job in one sentence. For a closet product it might be “build another outfit from clothes I already logged.” For a decision tool it might be “reopen a choice I parked.” For a narrative case it might be “return to the thread I left.” For a transfer product it might be “book the next planned journey.” Those are the four public jobs we already ship: YourStyle, Numira, Spylie, Luviport.
If you cannot name the second job, you shipped a demo. Onboarding that builds trust is a different essay: onboarding that converts skeptics. Week two assumes they already gave you a first chance.
Which product surfaces keep the second job visible?
- Home that shows the unfinished object, not a marketing hero.
- Empty states that teach the next action. See empty states that teach.
- A notification you earned, not a blast. See push that earns permission.
- Support mail that answers in human language. See support email.
Do not add a fifth tab to look alive. Feature discipline: feature creep. Catalog: what Croncode builds.
When do reminders help, and when do they train deletes?
| Reminder | Keep | Cut |
|---|---|---|
| Object waiting (outfit, case, booking) | Yes, one line | If the object is gone |
| Seasonal content that changes the job | Yes, dated | If it is filler |
| Generic “we miss you” | No | Always |
| Paywall after silence | No | Until the job is useful |
Seasonal work has its own page: seasonal content. Paywalls that stay honest: paywalls that do not lie. Personalization that watches the user: creep line.
How should a studio measure week two without theater?
Count users who completed the second job, not users who opened the app for two seconds. Name the build. Name the window as days 8 to 14 after first open, and write that definition so marketing cannot move it. We do not publish fake retention percentages for Croncode apps. You should not buy a vendor slide that lacks a definition either.
Analytics choice matters because a surveillance stack will tempt you to “re-engage” people who left for a reason. Tooling: analytics without surveillance. Founder support in the first cohort: founder-led support.
What mistakes look like growth?
- A long onboarding that steals the first job: they never had a week one.
- A streak that punishes rest: consumer tools are not gym dares unless that is the product.
- English-only week-two copy in a Turkish market: localize meaning, not only strings. See localizing onboarding.
- Pushing Android instead of fixing the second job: sequence: Android after iOS.
People: Goktug Unver, Yusufhan Sokur. Shipping: Istanbul shipping. Hire: hire the studio. Contact: contact. Journal: /en/journel/.
What should you put in the week-two brief?
Send the first job, the second job, and the message you will not send. Add who answers support in the first thirty users. Quote shape: quote packet. If you are still choosing a vendor: choose an iOS studio. Custom systems: custom software.
A thirty-day content plan can support week two without turning the app into a magazine. Plan: thirty-day content plan. Trust UI: trust patterns. Reviews will tell you if week two failed. Read them as a team: App Store reviews.
Frequently asked questions
Is day-seven retention the same as week two?
No. Day seven is still close to install novelty. Week two is the first quiet week. Define both if you report both.
Do I need a loyalty program?
You need a second job. Points are optional and often noisy. Do not buy a program to hide an empty home screen.
Should I email everyone who went quiet?
Email people who left an object unfinished, with a way to finish it. Mass “we miss you” trains deletes.
What if week two is a story chapter, not a tool?
Then the second job is the next chapter they can finish. A cliffhanger without a loadable save is a leak, not a hook.
Does Croncode guarantee a retention number?
No. We will write the second job and the kill rule. We will not invent a percentage for a pitch deck.
