Product development notes · · Updated:
PayRadar notifications: an engine that recovers after failure
This page holds the development notes of PayRadar’s 17 November 2026 update (version 2.3.0) and keeps the state of that day as a dated record. The current version and scope are on the product page. The Android app delivers its reminders on the device itself. The earlier web push work described below is also a historical record and should not be confused with the current Android notification pipeline.
: version 2.4.0 was published; the details are on the product page.
17 November: the 2.3.0 interface and reminder settings
Version 2.3.0 redesigns the interface with the calmer “Kül” palette, the Geist typeface and three bottom tabs. Payments shows this month’s total and overdue records, Calendar shows due dates by day, and Plan shows what is due before payday, the next 3 months and a yearly estimate. Radar cards derive an ending trial, a price change, instalments about to end and an upcoming yearly payment from the user’s own records.
Reminders are still scheduled on the phone and need no internet connection. According to the note in Settings, notifications start the chosen number of days before a due date; upcoming and overdue payments are listed once a day, after 09:00, in a single notification. The same screen offers a sample notification, a shortcut to Android notification settings and a battery-restriction check.
On 17 November 2026 version 2.3.0-phoenix (20) was published on the Google Play internal testing track and was submitted to Google review for the closed test the same day; on that date closed-test testers received 2.2.2-phoenix (19). The interface changes described in this section belong to the 2.3.0 release of that day; they do not show that notification delivery was tested on a physical phone.
6 November: Android local reminders and the 2.1.5 interface update
A persistent catch-up job that does not depend on an internet connection was added for missed local reminders. Eligible due dates are also checked when the app is reopened. A de-duplication record is kept for each account and day; the issue whereby an earlier unread notification silenced the next alert has been fixed.
The payment overview, separate monthly estimates per currency, Turkish search and the phone/tablet layout were redesigned. Invalid calendar days are rejected; a record changed concurrently is not overwritten with stale form data. The terms of use, the KVKK information notice and the privacy policy are separate sections; adding these texts does not mean that all legal operational obligations have been fulfilled.
48 unit tests and 11 Android emulator scenarios passed. In a separate process-termination check, a notification was created when the persistent catch-up job was started while no app process was running. These results are not a guarantee of natural scheduler delivery timing, of a person hearing the sound, or of success on every physical phone. Android notification permission, power management and force-stop restrictions apply.
The results dated 6 November belong to the 2.1.5-phoenix (12) release candidate of that day; the screen tours prepared for this update are no longer published.
30 October update: a notification engine that recovers after failure
A persistent delivery log was added for background notifications. The same day’s delivery is protected during concurrent operations; if an operation is left incomplete, a time-limited lock is released so it can be retried. For temporary connection and provider errors, up to six attempts are made at increasing intervals. The retry wait time reported by the provider is also taken into account.
The daily check runs every five minutes; eligible due dates are evaluated after 09:00 local time. An expired subscription is now renewed rather than registered again. The diagnostics on the Settings screen show delivery status and whether the daily check engine is running as separate items.
Once the notification has been displayed, the device sends a signed acknowledgement. If the internet connection drops, this acknowledgement is stored on the device and sent again when a connection is available. This record does not prove that a person saw or read the notification or heard a sound; it only indicates that the device has confirmed the notification display operation.
39 logic/Worker tests and 59 browser tests passed. The Worker and the web version went live on 30 October; that the live files matched the release, registration authorisation and the rejection of forged acknowledgements were verified. The first live run of the new scheduler completed without errors at 12:55 Türkiye time. Delivery on a physical Android device is an acceptance test separate from these automated checks.
30 October update: late payments and the day counter
A monthly payment advances by one calendar month, not by a fixed 30 days. When a payment due on 28 October is paid on 30 October, the new due date is 28 November, with 29 days remaining. When a payment due on 28 November is paid on 30 November, 28 days remain until 28 December. A payment advances one period from the old due date; the delay is not added to the new period and other unpaid periods are not skipped.
The review found a separate display bug: if the app was left open overnight, the day counter could show an out-of-date date. The cards and the main overview now refresh at local midnight and when you return to the app. Existing due days tied to the calendar month are preserved.
First problem: the setting on screen was not the setting being sent
When notifications were switched on in the settings screen, the background registration did not use the not-yet-saved preference at some steps. Even though the user saw that they had switched the toggle on, the registration could proceed with the previous stored state.
Background activation was changed to work with the current settings draft. The check was not tied only to the colour of the toggle: the browser subscription and the registration status on the server were also added to the diagnostics flow.
Second problem: the request was rejected before it even reached the network
The request prepared for push delivery was failing in the Cloudflare workerd environment because of the redirect: "error" option. The test that mocked the network request on Node had not revealed this runtime difference.
When the same request was retried in the real workerd runtime, the error was raised before any network activity. The redirect behaviour was changed to "manual". As a result, the request is not automatically redirected to another address, and unsuccessful HTTP responses are also handled separately as errors.
const response = await fetch(endpoint, {
...payload,
redirect: "manual",
});
if (!response.ok) {
// Do not assume delivery; handle the failed response.
}This example shows only the redirect and HTTP status check. It does not contain a real subscription endpoint, authorisation header or key.
Accepted and seen on the phone are different outcomes
The push service accepting the request does not mean that the notification was seen on the phone screen. Operating-system background restrictions, permissions and browser behaviour can affect the final stage.
For this reason, test feedback was limited to the server accepting the request. The connection check shows notification permission, registration status and whether there is an eligible due date as separate pieces of information. A registration renewal flow was also added to make faults easier to understand.
What have we verified, and what have we not yet verified?
In the related pre-release verification, 28 logic/Worker tests and 50 browser tests passed. The request-construction problem on workerd was reproduced and fixed. Live assets, the service worker and the temporary registration status/deletion checks were also reviewed separately. These are checks dated 25 October 2026; they are not an ongoing success rate for every device.
Android 1.1.0 was verified on the Google Play internal testing track. Seeing a real notification appear on a physical phone while the app is closed is an open verification step of this work. This article does not present that test as completed.
27 October update: daily alerts and accurate time information
When the daily reminder used the same tag as the previous day’s unread notification, it could silently replace the existing notification. Daily delivery has also been changed so that it requests a fresh alert. This preference does not override the phone’s notification permissions or its Do Not Disturb setting.
The connection check now separately shows when there is no eligible due date, when it is waiting for 09:00 local time, and when a daily delivery record exists. The Worker and web fixes were released on 27 October; 30 logic tests and the related browser test passed. Verification of visibility on a physical phone is separate from these results.
The implementation decision we took from this work
Mocking the network response in tests is useful, but it is not enough if the runtime rejects the request before it is even sent. With a problem like this, the same request needs to be tested in the environment where the product actually runs.
The second decision is to tell the user which part of the pipeline has been verified, rather than showing a single "working" label. Registration found, eligible due date exists, request accepted and seen on the phone are not interchangeable statements.
Source and product access
If you are assessing the notification or offline scope of a similar product, you can review our approach to web and mobile app development.