A push permission is a promise about future interruptions. You earn it when the user already knows the object you will mention: an outfit waiting, a choice parked, a chapter unlocked, a transfer window. You waste it when the first frame of the app is Apple’s sheet. At Croncode we treat push as a week-two tool, not as a launch trophy. Retention: week two. Trust onboarding: trust onboarding.

Earn push permission after the user finishes a job and understands the next object you will mention. A first-launch system sheet is a trained No.

When should the pre-permission screen appear?

After the first job completes once. The screen names one example notification in the user’s language. It offers Not now that does not nag every cold start. Localization: onboarding localization. Accessibility: the buttons need names. Accessibility.

Examples, not volumes: YourStyle might mention a saved look. Numira a parked choice. Spylie a chapter they asked to resume. Luviport a window they booked. Catalog: what Croncode builds.

Which notification types are honest?

Seasonal blasts need a calendar and a mute: seasonal content. Analytics should not become a retargeting file: analytics.

How do you keep the promise after they tap Allow?

1. Write a cap per week in the product, not only in a hope.
2. Deep link to the object, not to a marketing tab.
3. Honor system settings and an in-app mute.
4. Do not use push to paper over a crash. Crashes.

Paywalls should not arrive as push after a failure: honest paywalls. Empty home should not beg via push: empty states.

What belongs in the brief and the privacy label?

Whether you send, what the purpose string says, and which SDK if any. Store owner: account ownership. Quote: what to send. Security of push keys: security questions. We will not ship a silent push stack you cannot name. Will not build.

People: Goktug Unver, Yusufhan Sokur, Ozgur Ismet Ozkan. Shipping: how we ship.

What mistakes train deletes?

• Asking on frame one: they have no reason.
• A pre-permission screen that lies about frequency: reviews will say so. Reviews.
• English-only alerts in a Turkish listing: localize meaning.
• Using push instead of fixing week two: fix the job.

Hire: hire. Custom: custom software. Contact: contact. Journal: /en/journel/. Home: /en/. Design QA should include the pre-permission screen: design QA.

How should support talk about notifications?

Tell users where to mute in iOS Settings and in the app. Do not pretend you can override a system No. Support: support email. Founder-led weeks should read the first complaints: founder support. Sprint demo: show Not now, then Allow, then a sample notification on a device. Sprint demo.

Thirty-day content plans can include one earned reminder, not a daily magazine: thirty-day plan. If marketing wants a launch blast, use email or the site, not a permission you have not earned. A blast on day one trains a system No and a one-star. The store will keep that star longer than the campaign.

Write the example notification in both languages before you ship the pre-permission screen. If you cannot write one honest example, you are not ready to ask. Wait. The system sheet will still be there after the first job. It will not be there after a trained No.

Frequently asked questions

Is a pre-permission screen required?

It is not an Apple law. It is how you avoid burning the system sheet. If you skip it, still wait until after the first job.

Can I ask again later?

You can educate and send them to Settings. You cannot spawn the system sheet forever. Do not trap them in a loop.

Do transactional messages need the same care?

They still need a purpose string and a mute for marketing. A booking update is not a license for a weekly vibe.

What if my product is only useful with reminders?

Then the first job must prove that. Ask after the proof. A reminder-only app that cannot work without push is a fragile job. Write it in the brief.

Will Croncode guarantee an opt-in rate?

No. We will write the moment and the example. We will not invent a percentage.