docs: Replace flutter_workmanager with workmanager and remove marketing docs

- Replace all instances of 'flutter_workmanager' with 'workmanager'
- flutter_workmanager package does not exist, correct reference is 'workmanager'
- Remove marketing/strategy documents (ACTION_PLAN, ADOPTION_BARRIERS, etc.)
- Add SPM analysis document for future reference

Changes:
- Updated README, CHANGELOG, and all documentation
- Updated example code and benchmarks
- Removed 7 strategy/marketing documents
- No functional code changes

Author: vietnguyentuan2019

CHANGELOG.md

@@ -480,7 +480,7 @@ Consider sending large data as JSON in request body instead
 
 #### User Guides (3 files)
 - `docs/GETTING_STARTED.md` - 3-minute quick start guide
-- `docs/MIGRATION_GUIDE.md` - Step-by-step migration from flutter_workmanager
+- `docs/MIGRATION_GUIDE.md` - Step-by-step migration from workmanager
 - `docs/README.md` - Updated documentation index
 
 #### Technical Documentation (3 files)
@@ -1143,7 +1143,7 @@ await NativeWorkManager.enqueueChain(
 #### Documentation
 - ✅ **Comprehensive documentation** (~6,000+ lines total):
   - ARCHITECTURE.md - System architecture and design
-  - MIGRATION_GUIDE.md - Migration from flutter_workmanager
+  - MIGRATION_GUIDE.md - Migration from workmanager
   - TROUBLESHOOTING.md - Common issues and solutions
   - Multiple implementation summaries and guides
 
@@ -1155,7 +1155,7 @@ await NativeWorkManager.enqueueChain(
 
 ### Performance
 
-| Metric | flutter_workmanager | Native WorkManager | Improvement |
+| Metric | workmanager | Native WorkManager | Improvement |
 |--------|---------------------|-------------------|-------------|
 | **RAM (Native)** | 50MB | 2-5MB | **90-96% reduction** ⚡ |
 | **Cold Start (Native)** | 500-1000ms | <50ms | **10-18x faster** ⚡ |
@@ -1178,10 +1178,10 @@ await NativeWorkManager.enqueueChain(
 
 ### Migration Guide
 
-From `flutter_workmanager`:
+From `workmanager`:
 
 ```dart
-// Old (flutter_workmanager)
+// Old (workmanager)
 Workmanager().initialize(callbackDispatcher);
 Workmanager().registerOneOffTask("1", "task");
 
@@ -1276,22 +1276,22 @@ See [MIGRATION_GUIDE.md](MIGRATION_GUIDE.md) for complete migration guide.
 ## Performance Benchmarks
 
 ### RAM Usage
-| Scenario | flutter_workmanager | native_workmanager | Improvement |
+| Scenario | workmanager | native_workmanager | Improvement |
 |----------|---------------------|-------------------|-------------|
 | Native Worker (HTTP) | ~50MB | ~2-5MB | 90-96% less |
 | Dart Worker (Cold) | ~50MB | ~30-50MB | 0-40% less |
 | Dart Worker (Warm) | ~50MB | ~5-10MB | 80-90% less |
 
 ### Execution Speed
-| Scenario | flutter_workmanager | native_workmanager | Improvement |
+| Scenario | workmanager | native_workmanager | Improvement |
 |----------|---------------------|-------------------|-------------|
 | Native Worker Cold Start | 500-1000ms | <50ms | 10-20x faster |
 | Dart Worker Cold Start | 500-1000ms | 500-800ms | 1.25-2x faster |
 | Dart Worker Warm Start | 500-1000ms | 100-200ms | 5-10x faster |
 
 ### Battery Efficiency
 - Native workers: **89% better** battery efficiency (minimal FlutterEngine overhead)
-- Dart workers: **Similar** to flutter_workmanager (uses FlutterEngine when needed)
+- Dart workers: **Similar** to workmanager (uses FlutterEngine when needed)
 
 ---
 

README.md

@@ -26,7 +26,7 @@
 
 ## ⚡ Performance Comparison
 
-| Metric | flutter_workmanager | native_workmanager | Improvement |
+| Metric | workmanager | native_workmanager | Improvement |
 |--------|:------------------:|:------------------:|:-----------:|
 | **Memory** | 85 MB | 35 MB | **-50 MB (58%)** |
 | **Startup** | 500ms | <100ms | **5x faster** |
@@ -102,7 +102,7 @@ await NativeWorkManager.enqueue(
 
 ---
 
-## 🔄 Migrating from flutter_workmanager?
+## 🔄 Migrating from workmanager?
 
 **Good news:** ~90% API compatibility, most code stays the same!
 
@@ -115,7 +115,7 @@ await NativeWorkManager.enqueue(
 
 ### Common Migration Pattern
 
-**Before (flutter_workmanager):**
+**Before (workmanager):**
 ```dart
 Workmanager.registerPeriodicTask(
   'myTask',
@@ -180,7 +180,7 @@ NativeWorkManager.enqueue(
 
 ### Feature Comparison
 
-| Feature | native_workmanager | flutter_workmanager | workmanager |
+| Feature | native_workmanager | workmanager | workmanager |
 |---------|:--:|:--:|:--:|
 | Native Workers (zero overhead) | ✅ 11 types | ❌ | ❌ |
 | Task Chains (A→B→C) | ✅ Built-in | ❌ Manual | ❌ Manual |
@@ -320,7 +320,7 @@ A: Yes, but on iOS each task in the chain must complete within 30 seconds. Use n
 **Q: What happens if a task in a chain fails?**
 A: The chain stops. Subsequent tasks are cancelled. You can use retry policies to handle failures.
 
-**Q: Is this compatible with flutter_workmanager?**
+**Q: Is this compatible with workmanager?**
 A: ~90% compatible. Most code works with minor syntax changes. See [migration guide](doc/MIGRATION_GUIDE.md).
 
 **Q: Can I use this for location tracking?**

SPM_ANALYSIS.md

@@ -0,0 +1,127 @@
+# Swift Package Manager (SPM) Support Analysis
+
+## 📊 Current Status
+
+**Pub.dev Score Impact:** 0/0 points (not affecting score YET)
+
+**Warning from pub.dev:**
+> "Package does not support the Swift Package Manager on iOS. This package for iOS or macOS does not support the Swift Package Manager. It will not receive full points in a future version of the scoring model."
+
+---
+
+## 🔍 What is SPM?
+
+**Swift Package Manager** is Apple's official dependency manager for Swift projects. It's an alternative to CocoaPods for managing iOS/macOS dependencies.
+
+### Current Setup (CocoaPods)
+- ✅ Works with `podspec` file
+- ✅ 100% functional for iOS plugin
+- ✅ Used by Flutter plugin system
+- ❌ Does not support pure Swift Package Manager projects
+
+### Future (SPM Support)
+- ✅ Modern Apple-recommended approach
+- ✅ Better Xcode integration
+- ✅ Will be required for full pub.dev score (future)
+- ⚠️ Requires additional configuration
+
+---
+
+## 💡 Should We Fix This Now?
+
+### ❌ **Reasons to DEFER (Recommended)**
+
+1. **No Score Impact Yet**
+   - Currently: 0/0 points
+   - Not affecting our 160/160 score
+   - Timeline unclear ("future version of scoring model")
+
+2. **CocoaPods Works Fine**
+   - 99% of Flutter plugins use CocoaPods
+   - All users can install without issues
+   - Proven, stable ecosystem
+
+3. **Implementation Complexity**
+   - Requires creating `Package.swift`
+   - Need to restructure iOS folder layout
+   - Testing required on multiple Xcode versions
+   - Risk of breaking existing CocoaPods setup
+
+4. **Low User Demand**
+   - Most Flutter developers use CocoaPods
+   - SPM adoption in Flutter ecosystem is still early
+   - No user requests for this feature yet
+
+5. **Time Investment**
+   - Estimated: 4-6 hours implementation + testing
+   - Better spent on features users actually need
+   - Can add when pub.dev actually enforces it
+
+### ✅ **Reasons to FIX NOW**
+
+1. **Future-Proofing**
+   - Get ahead of the requirement
+   - No rush when pub.dev enforces it
+
+2. **Modern Best Practice**
+   - Apple recommends SPM over CocoaPods
+   - Better Xcode integration
+
+3. **Developer Experience**
+   - Some developers prefer SPM
+   - Broader compatibility
+
+---
+
+## 🎯 Recommendation
+
+**DEFER** SPM support for now because:
+
+1. ✅ **Zero score impact** (0/0 points)
+2. ✅ **No user demand** (no issues/requests)
+3. ✅ **Working solution exists** (CocoaPods)
+4. ✅ **Unclear timeline** (when will it be enforced?)
+
+**When to implement:**
+
+- ⏰ When pub.dev announces SPM will affect score (with timeline)
+- 📢 When users request it (GitHub issues)
+- 🎯 During a major version bump (v2.0.0)
+- 🔧 When restructuring iOS plugin architecture
+
+---
+
+## 📋 Implementation Checklist (For Future)
+
+When we decide to add SPM support:
+
+- [ ] Create `Package.swift` manifest
+- [ ] Restructure `ios/` folder for SPM compatibility
+- [ ] Configure binary framework inclusion (KMPWorkManager.xcframework)
+- [ ] Test with pure SPM project (not Flutter)
+- [ ] Test CocoaPods still works (dual support)
+- [ ] Update documentation
+- [ ] Test on Xcode 15+
+
+**Estimated effort:** 4-6 hours
+
+---
+
+## 🏁 Current Priority: DEFER
+
+**Focus instead on:**
+1. ✅ User-requested features
+2. ✅ Bug fixes from real-world usage
+3. ✅ Performance optimizations
+4. ✅ Documentation improvements
+
+**Monitor:**
+- Pub.dev announcements about SPM scoring
+- User requests for SPM support
+- Flutter ecosystem SPM adoption trends
+
+---
+
+**Decision:** Keep monitoring, implement when it becomes necessary or requested.
+
+**Current Score:** 160/160 points ✅ (SPM not affecting this)

benchmark/README.md

@@ -4,7 +4,7 @@ Independent benchmarking tool to verify native_workmanager performance claims.
 
 ## Purpose
 
-This tool allows **anyone** to run benchmarks and verify the performance differences between `native_workmanager` and `flutter_workmanager` on their own devices.
+This tool allows **anyone** to run benchmarks and verify the performance differences between `native_workmanager` and `workmanager` on their own devices.
 
 ## Why This Matters
 
@@ -62,7 +62,7 @@ This will:
 3. Wait 10 seconds for stabilization
 4. Measure PSS (Proportional Set Size) via `dumpsys meminfo`
 5. Kill process
-6. Repeat with flutter_workmanager worker
+6. Repeat with workmanager worker
 7. Compare results
 
 **Expected difference:** ~50MB (flutter_wm spawns Flutter Engine)
@@ -75,7 +75,7 @@ This will:
 1. Clear cache
 2. Start native_workmanager download task
 3. Measure time to completion
-4. Repeat with flutter_workmanager
+4. Repeat with workmanager
 5. Average over 5 runs
 
 **Expected difference:** ~25-35% faster (native OkHttp vs Dart http)
@@ -86,7 +86,7 @@ This will:
 
 **Method:**
 1. Clear logcat
-2. Run 10 tasks with flutter_workmanager
+2. Run 10 tasks with workmanager
 3. Count "Beginning load of flutter" messages
 4. Repeat with native_workmanager
 5. Compare
@@ -108,19 +108,19 @@ Results are saved as JSON in `results/`:
   "benchmarks": {
     "memory": {
       "native_workmanager_mb": 34.5,
-      "flutter_workmanager_mb": 84.2,
+      "workmanager_mb": 84.2,
       "difference_mb": 49.7,
       "difference_percent": 59.0
     },
     "io_performance": {
       "native_workmanager_ms": 8420,
-      "flutter_workmanager_ms": 11350,
+      "workmanager_ms": 11350,
       "difference_ms": 2930,
       "difference_percent": 34.8
     },
     "battery": {
       "native_workmanager_spawns": 0,
-      "flutter_workmanager_spawns": 10,
+      "workmanager_spawns": 10,
       "difference": 10
     }
   },

doc/BENCHMARKS.md

@@ -33,14 +33,14 @@ Detailed methodology and results for native_workmanager performance claims.
 - Flutter: 3.16.5
 - Dart: 3.2.3
 - native_workmanager: 1.0.0
-- flutter_workmanager: 0.5.2
+- workmanager: 0.5.2
 - kmpworkmanager: 2.2.1
 
 ## Benchmark 1: Memory Footprint
 
 ### Hypothesis
 
-`flutter_workmanager` spawns a Flutter Engine (~50MB) for each background task. `native_workmanager` runs pure native code without engine overhead.
+`workmanager` spawns a Flutter Engine (~50MB) for each background task. `native_workmanager` runs pure native code without engine overhead.
 
 **Expected difference:** ~50MB less memory usage
 
@@ -74,7 +74,7 @@ Detailed methodology and results for native_workmanager performance claims.
    adb shell am force-stop dev.brewkits.benchmark
    ```
 
-7. **Repeat steps 2-6 with flutter_workmanager worker**
+7. **Repeat steps 2-6 with workmanager worker**
 
 8. **Run 10 times** and average
 
@@ -123,7 +123,7 @@ PSS is the industry standard for measuring app memory.
 
 ### Hypothesis
 
-Native workers use platform-optimized HTTP clients (OkHttp on Android, URLSession on iOS). flutter_workmanager uses Dart's http package with isolate overhead.
+Native workers use platform-optimized HTTP clients (OkHttp on Android, URLSession on iOS). workmanager uses Dart's http package with isolate overhead.
 
 **Expected difference:** ~25-35% faster I/O
 
@@ -155,7 +155,7 @@ Native workers use platform-optimized HTTP clients (OkHttp on Android, URLSessio
 
 6. **Repeat 5 times** and average
 
-7. **Repeat with flutter_workmanager**
+7. **Repeat with workmanager**
 
 ### Results (Android - Pixel 6, WiFi)
 
@@ -173,7 +173,7 @@ Native workers use platform-optimized HTTP clients (OkHttp on Android, URLSessio
 
 ### Why the Difference?
 
-flutter_workmanager overhead:
+workmanager overhead:
 1. **Dart isolate spawn:** ~50-100ms
 2. **Data marshalling:** Convert bytes between Dart ↔ Platform
 3. **Dart http client:** Less optimized than native OkHttp
@@ -187,7 +187,7 @@ native_workmanager advantages:
 
 ### Hypothesis
 
-Each flutter_workmanager task spawns a Flutter Engine. native_workmanager spawns zero engines.
+Each workmanager task spawns a Flutter Engine. native_workmanager spawns zero engines.
 
 **Expected difference:** 0 vs N spawns
 
@@ -215,14 +215,14 @@ Each flutter_workmanager task spawns a Flutter Engine. native_workmanager spawns
    adb logcat -d | grep "Beginning load of flutter" | wc -l
    ```
 
-4. **Repeat with flutter_workmanager**
+4. **Repeat with workmanager**
 
 ### Results
 
 | Package | Engine Spawns | Battery Impact |
 |---------|---------------|----------------|
 | native_workmanager | **0** | ✅ Minimal |
-| flutter_workmanager | **10** | ❌ High |
+| workmanager | **10** | ❌ High |
 
 **Conclusion:** Each engine spawn costs:
 - ~500ms CPU time
@@ -312,7 +312,7 @@ cd native_workmanager/benchmark
 
 **Battery Test:**
 1. Clear logcat: `adb logcat -c`
-2. Run 10 tasks with flutter_workmanager
+2. Run 10 tasks with workmanager
 3. Count spawns: `adb logcat -d | grep "Beginning load of flutter" | wc -l`
 4. Expected: 10
 5. Repeat with native_workmanager
@@ -343,7 +343,7 @@ We need YOUR help to build credibility!
 
 For background tasks, this is complete overkill.
 
-### Q: Does this mean flutter_workmanager is bad?
+### Q: Does this mean workmanager is bad?
 
 **A:** No! It's great for tasks requiring:
 - Complex Dart business logic