🎨 Palette: Improve notification phrasing#117
Conversation
Hardcoded, technical, or aggressive terminology (e.g., using a raw "CHANNEL_ID" for the channel name, or words like "Kill" and "Click" for actions) in user-facing system notifications creates an abrasive and confusing experience. Notification channels and content are exposed directly to users in the Android system settings and status bar, so they must be descriptive and localized. This commit extracts foreground service notification and channel text (titles, descriptions, actions) into localized string resources (`strings.xml`) and updates standard mobile UX phrasing (e.g., "Stop" instead of "Kill", "Tap" instead of "Click") to ensure clear, polite, and universally understood interactions. Co-authored-by: manupawickramasinghe <73810867+manupawickramasinghe@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
Hardcoded, technical, or aggressive terminology (e.g., using a raw "CHANNEL_ID" for the channel name, or words like "Kill" and "Click" for actions) in user-facing system notifications creates an abrasive and confusing experience. Notification channels and content are exposed directly to users in the Android system settings and status bar, so they must be descriptive and localized. This commit extracts foreground service notification and channel text (titles, descriptions, actions) into localized string resources (`strings.xml`) and updates standard mobile UX phrasing (e.g., "Stop" instead of "Kill", "Tap" instead of "Click") to ensure clear, polite, and universally understood interactions. Co-authored-by: manupawickramasinghe <73810867+manupawickramasinghe@users.noreply.github.com>
💡 What
Extracts hardcoded string and technical labels from foreground service notification and channel creation into string resources with user-friendly language.
🎯 Why
Technical or aggressive terminology (e.g., using a raw "CHANNEL_ID" for the channel name, or words like "Kill" and "Click" for actions) in user-facing system notifications creates an abrasive and confusing experience. Notification channels and content are exposed directly to users in the Android system settings and status bar, so they must be descriptive and localized. Utilizing standard mobile UX phrasing (e.g., "Stop" instead of "Kill", "Tap" instead of "Click") ensures clear, polite, and universally understood interactions.
📸 Before/After
Before:
Notification channel name:
REMOTE_CAMNotification action:
KillNotification body:
Click to openAfter:
Notification channel name:
Camera ServiceNotification action:
STOPNotification body:
Tap to open controls♿ Accessibility
Ensures descriptive text for notification elements and channel settings, which are essential for users with screen readers when managing device notifications.
PR created automatically by Jules for task 6461660860201781863 started by @manupawickramasinghe