Start with a customer task
Android recommends requesting access when the relevant feature needs it; Apple recommends explaining notification requests through their context. Apply those principles to an imaginary Budapest bakery preparing a pickup app. Customers need to choose a branch, order bread and understand when collection is possible.
The bakery could offer a nearby-branch shortcut beside a manual branch list. After an order is accepted, it could offer an alert when preparation finishes. These are two different benefits. Write a separate explanation for each, using the same language as the surrounding shopping journey.
Make declining a workable choice
For this bakery, declining location should leave the branch list available, with addresses and opening hours. Declining notifications should leave an order screen showing the collection arrangement. Neither decision should erase the basket or send a customer back through registration.
Ask the development team to demonstrate both routes during a review. A polished permission explanation is insufficient if the next screen is blank. Give support staff the same walkthrough: they need to explain where customers can find their order without assuming an alert appeared.
Keep the first release proportionate
A manually selected branch may be enough for a bakery with two locations. Automatic suggestions add convenience, but also implementation work and extra situations to maintain. Decide whether that shortcut solves a frequent problem before buying map integrations or adding it to the launch deadline.
For this example, finding a pickup branch does not justify retaining a customer's movement history. Specify whether location is processed on the device or sent to a server, what is retained, and why. An order-ready alert also should not silently become a promotional subscription. Define those product preferences separately in the brief.
Make the promise match operations
The bakery must decide who marks an order ready and what happens if staff forget. A notification feature cannot repair an unclear kitchen process. Agree on the order status customers should trust and keep the collection instructions available inside the app.
Avoid copy that promises every alert will be seen. Apple documents changeable notification settings; Android documents handling revoked permissions. Have the team explain the actual behaviour on each supported platform. A shared visual design should not conceal differences in the system dialogs or available settings.
Use a short acceptance checklist
Before release, review the flow on the phones and languages you intend to support. Assign an owner to each failure and keep a short recording of the corrected journey for the next release.
- Start with a fresh installation and check both allow and decline choices.
- Change permissions in device settings, return, and check the branch and order screens.
- Confirm that manual selection and order details remain easy to find.
- Check that translated explanations describe the same benefit and fallback.
- Simulate an order becoming ready and verify the customer and staff views.