Was the message delivered?
I follow token registration, provider response and device permission state; an accepted send is not proof of delivery.
Push notification engineering
Push notifications should be measurable, reliable and worth sending.
Find where delivery, permissions, deep links or tracking fail across iOS and Android, then scope the right fix.
Work directly with Daniel, the engineer reviewing or building your app. Scope and schedule are agreed around limited independent availability.
Reality Check · €279
9:41● ◔ ▰
Delivery → action
Traceable
Device tokenTraced
App stateTested
Open eventMeasured
The gap
A sent message is not a completed notification journey.
A notification can be accepted by a provider and still fail the product. Tokens expire, permissions change, payloads behave differently, deep links break and open events disappear between systems.
This is designed forTeams that rely on push for activation, retention or critical journeys and cannot explain delivery gaps or user behaviour after the tap.
The questions that matter
What I look for in this situation.
Did the tap reach the right screen?
I test foreground, background and terminated states with the actual payload and deep link.
Did the notification create value?
I connect opens to in-app actions so the team can distinguish delivery from outcome.
From uncertainty to control
A diagnosis of the notification journey and a prioritised fix plan. Implementation can follow as a scoped sprint.
Trace delivery
Map providers, tokens, payloads and platform-specific behaviour.
Verify the tap
Test foreground, background, terminated and permission states.
Define the repair
Prioritise the change that restores the path to the right screen.
Implement and measure
If agreed as a separate sprint, add the fix and verify delivery evidence and opens.
9:41● ◔ ▰
Delivery → action
Traceable
Device tokenTraced
App stateTested
Open eventMeasured
01 / 04Trace delivery
What the work can cover
Senior attention where the product carries real risk.
- FCM, APNs and Expo Notifications
- Permission and token lifecycle
- Deep-link behaviour by app state
- Analytics and campaign attribution
A defined first engagement
Reality Check €279
A founder with one React Native or Expo codebase and a specific product or release concern.
What we agree to do
One repository and one priority user journey or technical risk.
Work included
- Review the relevant code, configuration and failure evidence
- Reproduce or trace the priority issue where access permits
- One 30-minute findings call
Delivery window
Within 5 business days after access and scope are agreed
What you receive
- Written risk assessment
- Prioritised next-step list with recommended scope
Outside this package
Implementation, a full security audit, penetration testing and review of unrelated app areas.
A written proposal confirms the acceptance criteria, start date and any applicable tax before work begins.
A useful first conversation
Tell me where the app is today.
I will reply personally with an honest view of the most useful next step. If there is a fit, we can schedule a short call.
Selected projects · Europe and remote
Already thinking it through with an AI?
With your permission, a connected AI assistant can send these same details directly and receive the next step.
See how AI contact works ↗