ワンクリックで
app-start-readiness-policy
Guidelines for coordinating splash screen dismissal with background data readiness
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Guidelines for coordinating splash screen dismissal with background data readiness
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Guidelines for managing Varisankya releases across Beta and Production tracks.
How to safely record extra payments without advancing the Varisankya subscription next due date.
Instructions for extracting the Play Store upload keystore, Firebase JSON, and passwords from Bitwarden.
Standard operating procedure for concluding an AI agent session and ensuring workspace integrity.
Guidelines for compiling Varisankya from the CLI without Android Studio.
How to correctly handle custom dates for extra subscription payments using MaterialDatePicker.
| name | App Start Readiness Policy |
| description | Guidelines for coordinating splash screen dismissal with background data readiness |
To prevent "Welcome" state flashes and UI jumps, the app must remain on the splash screen until the initial data payload is fully synchronized and processed.
Use the AndroidX SplashScreen API to hold the screen:
splashScreen.setKeepOnScreenCondition {
!isAuthSuccessful || !isDataLoaded
}
isAuthSuccessful: Set after Biometric or Firebase Auth succeeds.isDataLoaded: Set ONLY after the first valid data snapshot is processed (e.g., calculateHeroData finishes).Always implement a 5-second postDelayed fallback in initializeApp to ensure the app never hangs indefinitely due to network or Firestore latency:
mainNestedScrollView.postDelayed({
if (!isDataLoaded) {
isDataLoaded = true
}
}, 5000)
NEVER call background tasks or safety timeouts before your views are fully initialized. This prevents UninitializedPropertyAccessException.
setContentViewfindViewById (All)auth/viewModel InitsafetyTimeout (Last)