Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Build mobile applications with proper lifecycle handling, offline support, and platform conventions.
Build mobile applications with proper lifecycle handling, offline support, and platform conventions.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
App can be killed anytime in background—save state before backgrounding Restore state on return—user expects to continue where they left off Handle low memory warnings—release caches, non-essential resources Background tasks have time limits—complete or request extension
Ask in context, not at launch—explain why when requesting Degrade gracefully if denied—app should still work with reduced features Don't ask for unnecessary permissions—users notice and distrust Re-request after demonstrating value—not immediately after denial
Assume network is unreliable—design for offline, sync when possible Cache aggressively—previous content better than loading spinner Queue actions for retry—don't fail on network error Conflict resolution strategy—last write wins or manual merge Show sync status—user should know if data is current
Target 60fps—dropped frames feel janky Main thread for UI only—heavy work on background threads Memory matters more than desktop—constrained devices, aggressive OS killing Battery awareness—reduce location polling, network requests when possible Startup time under 2 seconds—first impression matters
Follow platform conventions—iOS back gesture, Android back button Navigation stack manageable—don't go 10 levels deep Deep link to any screen—shareable, notification taps work Preserve scroll position on return—don't jump to top
Push for time-sensitive external events—new message, delivery update Local for reminders, timers—user-initiated Don't spam—users will disable; quality over quantity Actionable when possible—reply, mark done from notification Group related notifications—less intrusive
Universal Links (iOS) / App Links (Android) for owned domains Handle gracefully when app not installed—fallback to web Parse parameters safely—malicious links exist Test all entry points—not just main launch
Secure storage for tokens, credentials—Keychain, Keystore User data survives reinstall where appropriate—cloud backup Cache is cache—can be cleared; don't store critical data Large files: consider on-demand download—not bundled in app
Keyboard avoidance—content shifts to stay visible Dismiss keyboard appropriately—tap outside, scroll, submit Input accessories for relevant actions—next field, done, toolbar Paste, autofill support—reduce typing on small keyboards
44pt minimum touch target—consistent with platform guidelines System gestures reserved—don't override swipe from edge Gesture discoverability—hint or teach, don't assume knowledge Haptic feedback for significant actions—confirmation, errors
VoiceOver (iOS) / TalkBack (Android) testing—navigate entire app Dynamic type support—text scales with user preference Sufficient contrast—check in accessibility inspector Labels on all interactive elements—not just visible text
Real devices essential—simulators miss performance, sensors, edge cases Multiple OS versions—support at least current minus 2 Different screen sizes—small phones to tablets Network conditions—slow, intermittent, offline
Read rejection reasons before submitting—common pitfalls documented Privacy policy required—explain data collection Login test account for reviewers—if auth required No placeholder content—everything functional in review build Update regularly—abandoned apps get deprioritized
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.