@haposoft/cafekit 0.15.1 → 0.16.0-rc.1

package/src/claude/skills/mobile-development/references/mobile-android.md

@@ -74,8 +74,8 @@ when (uiState) {
 
 ### Why Compose?
 - **Declarative**: Describe UI state, not imperative commands
-- **60% adoption**: In top 1,000 apps (2024)
-- **Less code**: 40% reduction vs Views
+- **Adoption**: Used in many top 1,000 apps
+- **Less code**: Reduction vs Views
 - **Modern**: Built for Kotlin and coroutines
 - **Material 3**: First-class support
 
@@ -310,7 +310,7 @@ class UserViewModel(
 
 **Hilt vs Koin:**
 - **Hilt**: Compile-time, type-safe, Google-backed, complex setup
-- **Koin**: Runtime, simple DSL, 50% faster setup, reflection-based
+- **Koin**: Runtime, simple DSL, faster setup, reflection-based
 
 ## Performance Optimization
 
@@ -335,14 +335,14 @@ android {
 ```
 
 **Impact:**
-- 10-20% app size reduction
-- 20% faster startup
+- Smaller app size
+- Faster startup
 - Harder to reverse engineer
 
 ### Baseline Profiles
 
 **Performance boost:**
-- 10-20% faster startup
+- Faster startup
 - Reduced jank in critical paths
 - AOT compilation of hot code
 
@@ -572,7 +572,7 @@ android {
 ```
 
 **Benefits:**
-- 15-30% smaller downloads
+- Smaller downloads
 - Dynamic feature modules
 - Instant apps support
 

package/src/claude/skills/mobile-development/references/mobile-best-practices.md

@@ -86,8 +86,8 @@ User opens screen
 - Background App Refresh (iOS)
 
 **Targets:**
-- Active use: <5% per hour
-- Background: <1% per hour
+- Active use: minimize foreground energy use
+- Background: minimize background energy use
 
 ## Offline-First Architecture
 
@@ -315,8 +315,8 @@ messaging().onNotificationOpenedApp(remoteMessage => {
 ```
 
 **Impact:**
-- 25% revenue increase with proper personalization
-- 88% opt-in rate with pre-permission modal (vs 40% without)
+- Personalization can increase revenue
+- Pre-permission modal can improve opt-in rate
 
 ## Authentication & Authorization
 
@@ -443,10 +443,10 @@ const token = credentials.password;
 - Expedited: 1-2 hours (emergencies only)
 
 **Rejection Reasons:**
-- Crashes (50%)
-- Privacy violations (25%)
-- Incomplete information (15%)
-- Guideline violations (10%)
+- Crashes
+- Privacy violations
+- Incomplete information
+- Guideline violations
 
 ### Google Play (Android)
 
@@ -460,7 +460,7 @@ const token = credentials.password;
 1. Build signed AAB (Android App Bundle)
 2. Upload to Play Console
 3. Submit to production track
-4. Staged rollout (10% → 50% → 100%)
+4. Staged rollout (pilot → partial → full)
 
 **Review Time:**
 - Average: 1-3 days
@@ -468,22 +468,21 @@ const token = credentials.password;
 
 ### Staged Rollout Strategy
 
-**Week 1:**
-- 10% of users
+**Pilot:**
+- Release to a small audience
 - Monitor crash-free rate
 - Watch for critical bugs
 
-**Week 2:**
-- 50% of users
+**Partial rollout:**
+- Expand audience after pilot
 - Validate performance metrics
 - Check user feedback
 
-**Week 3:**
-- 100% of users
-- Full release if metrics healthy
+**Full rollout:**
+- Release to all users when metrics are healthy
 
 **Rollback Triggers:**
-- Crash-free rate drops >5%
+- Crash-free rate shows a material drop
 - Critical bug discovered
 - Major user complaints
 
@@ -493,12 +492,12 @@ const token = credentials.password;
 
 | Metric | React Native | Flutter |
 |--------|--------------|---------|
-| **Adoption** | 35% | 46% |
-| **Performance** | 80-90% | 85-95% |
-| **App Size** | 40-50MB | 15-20MB |
-| **Dev Speed** | Fast | Very Fast |
-| **Commercial** | 12.57% | 5.24% |
-| **Developers** | 20:1 ratio | 1 ratio |
+| **Adoption** | Established | Established |
+| **Performance** | Near-native when profiled | Near-native when profiled |
+| **App Size** | Moderate | Moderate |
+| **Dev Speed** | Fast | Very fast |
+| **Commercial footprint** | Established | Established |
+| **Developers** | Broad ecosystem | Broad ecosystem |
 | **Best For** | JS teams | Performance |
 
 ### Architecture Comparison

package/src/claude/skills/mobile-development/references/mobile-frameworks.md

@@ -7,8 +7,8 @@ Comprehensive guide to mobile development frameworks: React Native, Flutter, and
 ### React Native
 - **Language**: JavaScript/TypeScript
 - **Stars**: 121,000+ on GitHub
-- **Adoption**: 35% of mobile developers, 67% familiarity
-- **Performance**: 80-90% native performance
+- **Adoption**: Broad adoption and familiarity among mobile developers
+- **Performance**: Near-native performance
 - **Architecture**: Bridge-based (legacy) → New Architecture (JSI, Fabric, Codegen)
 - **Rendering**: Native components
 - **Hot Reload**: Yes
@@ -17,8 +17,8 @@ Comprehensive guide to mobile development frameworks: React Native, Flutter, and
 ### Flutter
 - **Language**: Dart
 - **Stars**: 170,000+ on GitHub (fastest-growing)
-- **Adoption**: 46% of mobile developers
-- **Performance**: 85-95% native performance
+- **Adoption**: Broad adoption among mobile developers
+- **Performance**: Near-native performance
 - **Architecture**: "Everything is a widget"
 - **Rendering**: Custom Impeller rendering engine (eliminates jank)
 - **Hot Reload**: Yes (fastest in industry)
@@ -26,7 +26,7 @@ Comprehensive guide to mobile development frameworks: React Native, Flutter, and
 
 ### Native iOS (Swift/SwiftUI)
 - **Language**: Swift
-- **Performance**: 100% native
+- **Performance**: Native performance
 - **UI Framework**: SwiftUI (declarative) or UIKit (imperative)
 - **Latest**: Swift 6 with compile-time data race detection
 - **Tooling**: Xcode 16, Swift Package Manager
@@ -34,7 +34,7 @@ Comprehensive guide to mobile development frameworks: React Native, Flutter, and
 
 ### Native Android (Kotlin/Jetpack Compose)
 - **Language**: Kotlin
-- **Performance**: 100% native
+- **Performance**: Native performance
 - **UI Framework**: Jetpack Compose (declarative) or Views (imperative)
 - **Latest**: Kotlin 2.1, Compose 1.7
 - **Tooling**: Android Studio Hedgehog+
@@ -51,7 +51,7 @@ Comprehensive guide to mobile development frameworks: React Native, Flutter, and
 - **Turbo Modules**: Lazy-loaded native modules
 
 **Performance Optimizations**
-- **Hermes Engine**: 30-40% faster startup, reduced memory
+- **Hermes Engine**: Faster startup, reduced memory
 - **Native Driver Animations**: Offloaded to UI thread (60 FPS)
 - **FlatList Virtualization**: Renders only visible items
 - **Image Optimization**: FastImage library, progressive loading
@@ -81,14 +81,14 @@ src/
 4. **Context API**: Simple apps, avoid prop drilling
 
 **Navigation**
-- **React Navigation**: Industry standard, 80%+ adoption
+- **React Navigation**: Industry standard
 - Type-safe navigation with TypeScript
 - Deep linking configuration
 - Tab, stack, drawer navigators
 
 **TypeScript Adoption**
-- 85%+ of new React Native projects use TypeScript
-- Type safety prevents 15% of runtime errors
+- TypeScript is common in new React Native projects
+- Type safety helps prevent runtime errors
 - Better IDE support and autocomplete
 
 ### Testing Strategy
@@ -130,7 +130,7 @@ test('login button should be enabled when form is valid', async () => {
 - Rapid prototyping and MVPs
 - Strong community support needed
 - npm ecosystem integration
-- Commercial apps (12.57% market share)
+- Commercial apps
 
 **❌ Not Ideal For:**
 - Heavy graphics/gaming (use native or Unity)
@@ -254,7 +254,7 @@ testWidgets('Counter increments', (WidgetTester test-runner) async {
 - Move semantics for performance
 
 **SwiftUI vs UIKit**
-- **SwiftUI**: Declarative, 40% less code, iOS 13+, modern approach
+- **SwiftUI**: Declarative, less code, iOS 13+, modern approach
 - **UIKit**: Imperative, fine-grained control, legacy support, complex customizations
 - Both work together in same project
 
@@ -318,7 +318,7 @@ struct LoginView: View {
 
 **Jetpack Compose**
 - Declarative UI (like SwiftUI/React)
-- 60% adoption in top 1,000 apps
+- Widely adopted in top 1,000 apps
 - Material Design 3 integration
 - Compose compiler with Kotlin 2.0+
 

package/src/claude/skills/mobile-development/references/mobile-ios.md

@@ -53,7 +53,7 @@ actor UserCache {
 ✅ Declarative UI preferred
 ✅ Fast iteration needed
 ✅ Cross-platform (macOS, watchOS, tvOS)
-✅ 40% less code vs UIKit
+✅ Less code vs UIKit
 
 ### When to Use UIKit
 ✅ Legacy app maintenance

package/src/claude/skills/mobile-development/references/mobile-mindset.md

@@ -5,7 +5,7 @@ Essential thinking patterns and decision-making frameworks for successful mobile
 ## The 10 Commandments of Mobile Development
 
 ### 1. Performance is Foundation, Not Feature
-- **Reality**: 70% users abandon apps >3s load time
+- **Reality**: Users may abandon apps when load time exceeds 3s
 - **Mindset**: Optimize from day one, not "later"
 - **Action**: Set performance budgets before writing code
 
@@ -50,7 +50,7 @@ Essential thinking patterns and decision-making frameworks for successful mobile
 - **Action**: MVVM for small apps, Clean Architecture when complexity demands
 
 ### 10. Continuous Learning is Survival
-- **Reality**: 85% developers use AI tools (2024), frameworks evolve constantly
+- **Reality**: AI tools are widely used by developers (2024), frameworks evolve constantly
 - **Mindset**: Embrace change, allocate learning time
 - **Action**: 1+ hour weekly for new tech/patterns
 
@@ -131,7 +131,7 @@ Essential thinking patterns and decision-making frameworks for successful mobile
 - "It just works" expectation = zero tolerance for crashes
 
 **Fragmentation**: LOW
-- 90%+ on iOS 16+ (2024)
+- Most users on iOS 16+ (2024)
 - Only ~50 device models to test
 - Predictable hardware specs
 
@@ -165,7 +165,7 @@ Essential thinking patterns and decision-making frameworks for successful mobile
 - Handle back button properly
 
 **When to Go Native Android:**
-- Global market focus (72% market share)
+- Global market focus (Android dominates)
 - Emerging markets (Android dominates)
 - Enterprise/B2B (customization needs)
 
@@ -177,7 +177,7 @@ Essential thinking patterns and decision-making frameworks for successful mobile
 |--------|-----------|-----------------|
 | **Launch time** | <2s | Acceptable |
 | **Launch time** | 2-3s | Noticeable delay |
-| **Launch time** | >3s | 70% abandon |
+| **Launch time** | >3s | Users may abandon |
 | **Screen load** | <1s | Instant (cached) |
 | **Screen load** | 1-3s | Acceptable (network) |
 | **Screen load** | >3s | Frustrating |
@@ -259,46 +259,44 @@ Week 2: Polish + Ship
 8. Merge to develop
 
 **CI/CD Impact:**
-- 20% reduction in development time
-- 50% fewer production bugs
-- 3x faster deployment
+- Faster development and deployment with fewer production bugs
 
 ### Common Pitfalls & Avoidance
 
 #### 1. Testing Only on Simulators
 **Problem**: Simulators don't show real performance (battery, memory, network)
 **Solution**: Real device testing mandatory before every release
-**Impact**: 40% of bugs only appear on real devices
+**Impact**: Some bugs only appear on real devices
 
 #### 2. Ignoring Platform Conventions
 **Problem**: Custom navigation confuses users
 **Solution**: Follow iOS HIG and Material Design
-**Impact**: 30% lower engagement with non-standard UIs
+**Impact**: Non-standard UIs can lower engagement
 
 #### 3. No Offline Handling
 **Problem**: Network failures = blank screens, errors
 **Solution**: Offline-first architecture, cached data
-**Impact**: 50% of users experience network issues daily
+**Impact**: Users can experience network issues daily
 
 #### 4. Poor Memory Management
 **Problem**: Memory leaks → crashes, poor performance
 **Solution**: ARC/GC understanding, profile regularly
-**Impact**: Memory issues = #1 crash cause (35%)
+**Impact**: Memory issues are a leading crash cause
 
 #### 5. Hardcoded Credentials
 **Problem**: Security vulnerability, API key exposure
 **Solution**: Environment variables, secure storage
-**Impact**: 23% of apps leak sensitive data (OWASP)
+**Impact**: Apps can leak sensitive data; follow OWASP guidance.
 
 #### 6. No Accessibility
-**Problem**: Excludes 15%+ of users (disability, situational)
+**Problem**: Excludes users with disabilities or situational needs
 **Solution**: VoiceOver/TalkBack testing, semantic labels
 **Impact**: Accessibility = 1.3B global market
 
 #### 7. Premature Optimization
 **Problem**: Wasted time optimizing non-bottlenecks
 **Solution**: Measure first, optimize biggest impact
-**Impact**: 80% of performance issues = 20% of code
+**Impact**: Many performance issues come from a small part of the code
 
 #### 8. Over-Engineering
 **Problem**: Complex architecture for simple apps
@@ -308,7 +306,7 @@ Week 2: Polish + Ship
 #### 9. Skipping Real Device Testing
 **Problem**: Missed battery drain, thermal issues
 **Solution**: Device farm in CI/CD, manual testing
-**Impact**: 25% of performance issues device-specific
+**Impact**: Some performance issues are device-specific
 
 #### 10. Not Respecting Battery
 **Problem**: Background processing drains battery
@@ -460,12 +458,12 @@ if (isLowEndDevice) {
 
 **Example Architecture:**
 ```
-React Native / Flutter (90%)
+React Native / Flutter
 ├─ UI and business logic
 ├─ Standard features
 └─ API integration
 
-Native Modules (10%)
+Native Modules
 ├─ Performance-critical (video processing)
 ├─ Platform-specific (HealthKit, Android Auto)
 └─ Third-party SDKs (payment, analytics)
@@ -535,7 +533,7 @@ v4.0: Extract microservices if justified
 - Discord (React Native, Flutter official)
 - Twitter: Follow framework creators and contributors
 
-**AI Tools (85% adoption in 2024):**
+**AI Tools (widely adopted in 2024):**
 - GitHub Copilot: Code completion, boilerplate
 - ChatGPT/Claude: Architecture questions, debugging
 - Tabnine: Context-aware suggestions