UI refresh, account flow improvements, and sync optimization

[Ex057]

Summary

• Refreshed Home/Account/Settings UI layout and navigation flow
• Added Edit Account screen and improved account management routing
• Improved dark theme readability on data entry screens and removed blue top bars where requested
• Added dataset prefetching and limited initial background sync scope
• Fixed “Not synced” label persistence after successful sync

Key changes

• New Edit Account screen with add/delete account options
• Home tab cards and search placement updates
• Background prefetching for datasets + lazy prefetch on selection
• Sync status handling improvements and draft cleanup after sync
• Theme and color refinements for dark mode

Files touched (high‑level)

• App navigation and screens:
  app/src/main/java/com/ash/simpledataentry/navigation/AppNavigation.kt
app/src/main/java/com/ash/simpledataentry/presentation/MainActivity.kt
app/src/main/java/com/ash/simpledataentry/presentation/datasets/DatasetsScreen.kt
app/src/main/java/com/ash/simpledataentry/presentation/settings/SettingsScreen.kt
app/src/main/java/com/ash/simpledataentry/presentation/settings/EditAccountScreen.kt
app/src/main/java/com/ash/simpledataentry/presentation/dataEntry/CreateNewEntryScreen.kt
app/src/main/java/com/ash/simpledataentry/presentation/datasetInstances/DatasetInstancesScreen.kt

• ViewModels and sync:
  app/src/main/java/com/ash/simpledataentry/presentation/datasets/DatasetsViewModel.kt
app/src/main/java/com/ash/simpledataentry/presentation/datasetInstances/DatasetInstancesViewModel.kt
app/src/main/java/com/ash/simpledataentry/data/sync/BackgroundDataPrefetcher.kt

• Theme + resources:
  app/src/main/java/com/ash/simpledataentry/ui/theme/Theme.kt
app/src/main/java/com/ash/simpledataentry/ui/theme/Color.kt
app/src/main/res/values/colors.xml
app/src/main/res/values/themes.xml
app/src/main/res/values-night/*

• Assets:
  app/src/main/res/drawable/login_logo.png
  launcher icon resources

Testing

• Built locally with ./gradlew :app:assembleRelease

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
-	-	Username Password	8c3bf16	app/src/main/java/com/ash/simpledataentry/presentation/login/LoginScreen.kt	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}