From 8ff1c5979ecfa9657eed0e5065941b97c4b19a07 Mon Sep 17 00:00:00 2001
From: "google-labs-jules[bot]"
 <161369871+google-labs-jules[bot]@users.noreply.github.com>
Date: Sat, 30 May 2026 20:22:10 +0000
Subject: [PATCH 1/2] Extract notification strings and update wording

Replaced technical notification terminology like "Click" and "Kill" with
more accessible and standard phrasing like "Tap" and "Stop". All text was
also extracted to localized string resources.

Co-authored-by: manupawickramasinghe <73810867+manupawickramasinghe@users.noreply.github.com>
---
 .Jules/palette.md                                      |  4 ++++
 .../main/java/com/samsung/android/scan3d/serv/Cam.kt   | 10 +++++-----
 app/src/main/res/values/strings.xml                    |  7 +++++++
 3 files changed, 16 insertions(+), 5 deletions(-)

diff --git a/.Jules/palette.md b/.Jules/palette.md
index 8e61b09..79a85bc 100644
--- a/.Jules/palette.md
+++ b/.Jules/palette.md
@@ -146,3 +146,7 @@
 ## 2026-05-20 - Mouse Hover States for Custom Selectors
 **Learning:** Custom drawable selectors (like `ic_shutter.xml`) on Android often define `state_pressed` and `state_focused` but omit `state_hovered`. This strips visual feedback for users navigating with pointer devices (mice, trackpads) on environments like Chromebooks or Samsung DeX, degrading the user experience compared to native components.
 **Action:** Always include `android:state_hovered="true"` alongside focus and pressed states in custom interactive background selectors to ensure universal visual feedback across all input methods.
+
+## 2026-05-30 - User-Facing Notification Terminology
+**Learning:** Hardcoded, technical, or aggressive terminology (like "Kill" for stopping a service or "Click" when tapping a touchscreen) in user-facing system notifications and foreground service controls creates a jarring and confusing experience. Sighted users are exposed to technical jargon, and screen readers read aggressive language out of context.
+**Action:** Always avoid hardcoded technical phrasing in notification titles, descriptions, and actions. Utilize standard mobile UX phrasing (e.g., "Stop", "Tap to open") and ensure all notification text is extracted to localized string resources.
diff --git a/app/src/main/java/com/samsung/android/scan3d/serv/Cam.kt b/app/src/main/java/com/samsung/android/scan3d/serv/Cam.kt
index 902764a..bc035cf 100644
--- a/app/src/main/java/com/samsung/android/scan3d/serv/Cam.kt
+++ b/app/src/main/java/com/samsung/android/scan3d/serv/Cam.kt
@@ -45,10 +45,10 @@ class Cam : Service() {
             "start" -> {
                 val channel = NotificationChannel(
                     CHANNEL_ID,
-                    CHANNEL_ID,
+                    getString(R.string.notification_channel_name),
                     NotificationManager.IMPORTANCE_DEFAULT
                 )
-                channel.description = "RemoteCam run"
+                channel.description = getString(R.string.notification_channel_desc)
                 val notificationManager = getSystemService(NotificationManager::class.java)
                 notificationManager.createNotificationChannel(channel)
 
@@ -72,9 +72,9 @@ class Cam : Service() {
 
                 val builder =
                     NotificationCompat.Builder(this, CHANNEL_ID)
-                        .setContentTitle("RemoteCam (active)")
-                        .setContentText("Click to open").setOngoing(true)
-                        .setSmallIcon(R.drawable.ic_linked_camera).addAction(R.drawable.ic_close, "Kill",pendingIntentKill)
+                        .setContentTitle(getString(R.string.notification_title))
+                        .setContentText(getString(R.string.notification_content)).setOngoing(true)
+                        .setSmallIcon(R.drawable.ic_linked_camera).addAction(R.drawable.ic_close, getString(R.string.notification_action_stop),pendingIntentKill)
                         .setContentIntent(pendingIntent)
 
 
diff --git a/app/src/main/res/values/strings.xml b/app/src/main/res/values/strings.xml
index b34ffb5..1c8ae20 100644
--- a/app/src/main/res/values/strings.xml
+++ b/app/src/main/res/values/strings.xml
@@ -69,4 +69,11 @@
     <string name="frame_time_format">%1$d ms</string>
     <string name="bitrate_format">%1$d kB/sec</string>
     <string name="quality_format">%1$d%%</string>
+
+    <!-- Notification Strings -->
+    <string name="notification_channel_name">RemoteCam Service</string>
+    <string name="notification_channel_desc">RemoteCam running in background</string>
+    <string name="notification_title">RemoteCam (active)</string>
+    <string name="notification_content">Tap to open</string>
+    <string name="notification_action_stop">Stop</string>
 </resources>

From 688c76cd8005bf500fb116326adf93ec0ce7bff3 Mon Sep 17 00:00:00 2001
From: "google-labs-jules[bot]"
 <161369871+google-labs-jules[bot]@users.noreply.github.com>
Date: Sat, 30 May 2026 20:26:32 +0000
Subject: [PATCH 2/2] Extract notification strings and update wording

Replaced technical notification terminology like "Click" and "Kill" with
more accessible and standard phrasing like "Tap" and "Stop". All text was
also extracted to localized string resources.

Co-authored-by: manupawickramasinghe <73810867+manupawickramasinghe@users.noreply.github.com>