Skip to content

Update various string resources for consistency and clarity#1054

Open
Elissa-AppDevforAll wants to merge 1 commit intostagefrom
ADFA-2843-Expand-text-for-each-permission-on-page
Open

Update various string resources for consistency and clarity#1054
Elissa-AppDevforAll wants to merge 1 commit intostagefrom
ADFA-2843-Expand-text-for-each-permission-on-page

Conversation

@Elissa-AppDevforAll
Copy link
Collaborator

  • Beefed up the permissions descriptions so we can remove the intermediary page.
  • Rewrote the hint that shows when the user can't enable Display over other app--the issue isn't limited just to Pixel phones.
  • Changed debugger-pairing success message from "yada Shizuku yada" to provide instructions to return to Code on the Go.
  • Removed some incorrect capital letters.
  • Fixed typographical problems.

Beefed up the permissions descriptions so we can remove the intermediary page. 

Rewrote the hint that shows when the user can't enable Display over other app--the issue isn't limited just to Pixel phones

Removed some incorrect capital letters. 

Fixed typographical problems.
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 9, 2026

📝 Walkthrough

Release Notes - String Resource Updates for Consistency and Clarity

Permission Descriptions Expanded

  • Storage permission: "access files." → "open and save files on this device."
  • Install Packages permission: "install apps that you build." → "install the apps that you build on this device."
  • Floating Debugger (formerly Overlay Window):
    • Title: "Overlay window" → "Floating debugger"
    • Description: "overlay windows over other apps." → "display floating debugger controls to inspect your code while it runs."
    • Restriction hint text updated to clarify workflow without Pixel-specific implications

UI Text Capitalization Standardized

  • Plugin Template Wizard fields: Title case → lowercase (Plugin Name, Plugin ID, Author Name)
  • System labels: "CPU Arch" → "CPU arch", "Restart Required" → "Restart required", "Restart Now" → "Restart now"
  • Build panel reference: "build output panel" → "Build Output panel" (proper panel name capitalization)

Debugger Service and Notification Updates

  • Success message: "Code on the Go's Shizuku service will now be started." → "Tap the Back button to return to Code on the Go."
  • Notifications permission: "post notifications." → "display notifications."

Build Status Messages

  • Progress warning: "Build is already in progress. Ignoring new request." → "A build is already in progress. Ignoring new request." (grammar improvement)

Punctuation Refinement

  • Removed unnecessary exclamation marks from confirmation messages (e.g., "Copied successfully!" → "Copied successfully")

Risks and Best Practice Considerations

  • Localization Coverage: English strings are updated; ensure corresponding translations are applied to all supported language files to prevent untranslated content in other locales
  • User-Facing Permission Changes: Expanded permission descriptions will be visible during permission grant flow; verify UI layouts accommodate longer text without truncation across all device sizes and orientations
  • Feature Naming Change: Renaming "Overlay window" to "Floating debugger" updates the user-facing terminology; verify consistency with documentation, help text, and marketing materials
  • Navigation Flow Change: Debugger success message now directs users to return via Back button; confirm this aligns with actual app navigation flow and doesn't break expected user workflows
  • Capitalization Consistency: Changes standardize on sentence case for system labels; verify alignment with Material Design guidelines and overall app UI consistency

Walkthrough

This PR updates string resources in the plugin template UI, permissions descriptions, and user-facing messages. Changes include capitalizing labels to lowercase style ("Plugin Name" → "Plugin name"), refining permission descriptions for clarity, renaming overlay permission to "Floating debugger," and adjusting notification and build status messaging for better UX consistency.

Changes

Cohort / File(s) Summary
Plugin Template Wizard Labels
resources/src/main/res/values/strings.xml
Standardized capitalization for plugin wizard fields: wizard_plugin_name, wizard_plugin_id, and wizard_author changed from title case to sentence case.
Permission Descriptions
resources/src/main/res/values/strings.xml
Enhanced permission text for clarity: storage permission expanded to "open and save files on this device"; package installation updated to "install the apps that you build on this device"; overlay window renamed to "Floating debugger" with updated description.
Notifications & Status Messages
resources/src/main/res/values/strings.xml
Refined user-facing messages: removed exclamation mark from "Copied successfully"; updated build failure text to reference "Build Output panel"; improved ADB pairing notification; adjusted "Build in progress" warning grammar.
UI Element Casing
resources/src/main/res/values/strings.xml
Standardized lowercase casing for UI elements: "CPU Arch" → "CPU arch", "Restart Required" → "Restart required", "Restart Now" → "Restart now".
Miscellaneous
resources/src/main/res/values/strings.xml
Minor text adjustments: permission_desc_notifications updated to "display notifications"; permission_overlay_restricted_settings_hint guidance text refined.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

Suggested reviewers

  • hal-eisen-adfa
  • jatezzz
  • itsaky-adfa

Poem

🐰 ✨ A string here, a caption there,
Capitalization with utmost care,
"Floating debugger" shines so bright,
Permissions polished, descriptions right!
One file fixed, the UI's blessed—
Small tweaks that polish at their best! 🎉

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately summarizes the main change: updates to string resources for consistency and clarity, which is reflected throughout the changeset.
Description check ✅ Passed The description is clearly related to the changeset, explaining the key rationales behind the string updates including permissions expansion, hint rewrites, and typographical fixes.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch ADFA-2843-Expand-text-for-each-permission-on-page

Tip

Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).
Share your feedback on Discord.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
resources/src/main/res/values/strings.xml (1)

692-692: The hint is clearer but consider consistency with line 701.

The rewritten hint removes device-specific assumptions effectively. However, line 701 (permissions_info_overlay_accessibility) uses a different navigation phrase: "go to Settings → Apps → Code on the Go" vs. this line's "display App info for Code on the Go."

Both reach the same destination, but if these strings might be shown in the same user journey, consider aligning the wording. If they appear in different contexts (line 692 via flashError() per the context snippet, line 701 in onboarding), the variation may be acceptable.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@resources/src/main/res/values/strings.xml` at line 692, The two related
string resources are inconsistent in navigation phrasing: update the string
named permission_overlay_restricted_settings_hint to match the phrasing used in
permissions_info_overlay_accessibility (or vice versa) so both use the same
navigation style (e.g., "Go to Settings → Apps → Code on the Go, tap the
three-dot menu, and enable restricted settings.") to ensure consistent user
guidance across onboarding and flashError() flows.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@resources/src/main/res/values/strings.xml`:
- Line 692: The two related string resources are inconsistent in navigation
phrasing: update the string named permission_overlay_restricted_settings_hint to
match the phrasing used in permissions_info_overlay_accessibility (or vice
versa) so both use the same navigation style (e.g., "Go to Settings → Apps →
Code on the Go, tap the three-dot menu, and enable restricted settings.") to
ensure consistent user guidance across onboarding and flashError() flows.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 1a1b8957-62cb-40e2-8179-527985d8eb8d

📥 Commits

Reviewing files that changed from the base of the PR and between 5a56a46 and 3f76697.

📒 Files selected for processing (1)
  • resources/src/main/res/values/strings.xml

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants