🎨 Palette: Improve notification phrasing and extraction#124
🎨 Palette: Improve notification phrasing and extraction#124manupawickramasinghe wants to merge 1 commit into
Conversation
Replaces hardcoded, technical terminology (like "Kill") and internal identifiers (like `CHANNEL_ID`) with localized string resources in the foreground service notification to improve the user-facing experience. 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. |
💡 What: Replaced hardcoded, technical terminology (like "Kill" and "Click to open") and internal identifiers (like
CHANNEL_IDas the channel name) with localized string resources in the foreground service notification.🎯 Why: These elements are directly exposed to users in Android system settings and the notification shade. Using raw technical identifiers or aggressive terms degrades the user experience and breaks localization. This change ensures standard mobile UX phrasing ("Camera Service", "Stop", "Tap") is used universally.
📸 Before/After:
♿ Accessibility: By extracting these strings to
strings.xml, they can now be properly localized for different languages and regions, ensuring all users can understand the notification context and actions. Standardized terminology ("Tap", "Stop") also provides clearer expectations for interaction compared to jargon ("Click", "Kill").PR created automatically by Jules for task 17224710657757917961 started by @manupawickramasinghe