Found 23 matches for pattern "Developer" across 2 workspace directories:
---
File: service-book/TESTING_SETUP.md
L143: Running screenshot tests in `src/test` ensures snapshots are generated directly onto the host filesystem, providing a reliable and frictionless developer experience.
L165: We use Robolectric to run Android-dependent tests (including UI and integration tests) on the JVM for faster execution and better developer experience.
---
File: service-book/app/lint-baseline.xml
L28:         message="Limit vector icons sizes to 200×200 to keep icon drawing fast; see https://developer.android.com/studio/write/vector-asset-studio#when for more"
L39:         message="Limit vector icons sizes to 200×200 to keep icon drawing fast; see https://developer.android.com/studio/write/vector-asset-studio#when for more"
L50:         message="Limit vector icons sizes to 200×200 to keep icon drawing fast; see https://developer.android.com/studio/write/vector-asset-studio#when for more"
---
File: service-book/app/src/main/java/com/yorvana/ui/settings/SettingsScreen.kt
L549:             // ── Developer ──────────────────────────────────────────────────
L551:                 SectionHeader(stringResource(R.string.settings_developer_title))
---
File: service-book/app/src/main/res/values/strings.xml
L216:     <!-- Settings Developer Panel -->
L217:     <string name="settings_developer_title">Developer</string>
---
File: service-book/docs/adr.md
L319: - Developers must run `./gradlew verifyRoborazziDebug` to check for visual changes and `./gradlew recordRoborazziDebug` to update golden images when UI changes are intentional.
---
File: service-book/docs/plan-integration-tests-restructure.md
L47:    - **Local caveat:** After this change, running `verifyWithCoverage` locally will use whichever `.ec` file is checked out in LFS. If it is stale or missing, coverage from GMD tests will be absent or inaccurate. Developers who need fresh GMD coverage locally should run `generateGmdCoverage` first.
---
File: service-book/docs/plan-paywall.md
L18: - A debug-only developer panel in Settings overrides billing state at runtime to allow testing free/paid/upgrade paths on a debug APK without round-tripping through Google Play.
L30: | 5 | UI components + screen integration | `ReadOnlyWarningBanner`, `UpgradeDialog`, `PaywallScaffold`. All 7 paywalled screens swapped to `PaywallScaffold`. Settings Premium section + debug developer panel. |
L419: **Goal:** End user can see the banner, the upgrade dialog, and the Settings premium section. All paywalled screens use the shared `PaywallScaffold`. The debug developer panel is available in debug builds.
L464: | `ui/settings/SettingsScreen.kt` | Premium section + debug developer panel (Step 5.5). |
L501: **Developer panel** (gated by `if (BuildConfig.DEBUG)`):
L503: [ Developer ]
L523: | `SettingsScreenshotTest.kt` | Premium-active, premium-free, developer panel hidden in non-debug |
L534: - Manual: build `installDebug`; toggle developer panel; observe banner appears across all paywalled screens. (This is a sanity check — full on-device validation is Phase 7.)
L645: Open Settings → Developer panel.
L683: 2. Settings → Developer → *Real (use Play)* (no override).
L750: | `ui/settings/SettingsScreen.kt` | 5 | Premium section + debug developer panel |
---
File: service-book/docs/privacy-policy.md
L11: - **Igors Vinogradovs** (individual developer, acting as data controller)
---