native-update 1.4.9 → 3.1.0

package/docs/social-media-marketing/README.md

@@ -0,0 +1,81 @@
+# Native Update — Social Media Marketing
+
+Long-form posts, WhatsApp messages, and WhatsApp status copy for promoting the **Native Update** Capacitor plugin (`native-update` on NPM) and the surrounding ecosystem (Laravel + Nova SaaS backend, CLI, native Android/iOS, React marketing/dashboard site, 3 example apps).
+
+All content is **truthful** — only features that ship today are mentioned. No fabricated stats, no "best-in-class" puffery, no keyword stuffing. Every piece has a clear CTA.
+
+---
+
+## How this folder works
+
+| File pattern | Purpose | Items per file | Size per item |
+|---|---|---|---|
+| `posts-batch-NN.md` | Posts for LinkedIn / Facebook (LinkedIn caps at 3,000 chars) | 10 | **2700–2900 chars (~490–510 words)** |
+| `whatsapp-messages-batch-NN.md` | WhatsApp group / DM messages | 30 | **400–600 chars (~60–80 words)** |
+| `whatsapp-status-batch-NN.md` | WhatsApp status messages | 30 | **240–400 chars (~40–60 words)** |
+
+**Char limits are HARD limits.** LinkedIn rejects > 3,000-char posts. WhatsApp messages over ~600 chars get scrolled-past in groups. Status over ~400 chars gets visually cramped. Stay inside the windows.
+
+### "USED" marker convention
+
+Once a post / message / status has been shared, **prepend `USED — ` to its heading**. Example:
+
+```
+## Post 03 — OTA in 60 seconds   →   ## USED — Post 03 — OTA in 60 seconds
+```
+
+This lets the next session see at a glance which content has been consumed and avoid duplicates.
+
+### When to generate the next batch
+
+The next session of this prompt should:
+
+1. Read this README first
+2. Scan `posts-batch-*.md`, `whatsapp-messages-batch-*.md`, `whatsapp-status-batch-*.md`
+3. **Only generate a new posts file** if every post in the latest posts batch is marked `USED`
+4. **Only generate a new WhatsApp messages file** if every message in the latest messages batch is marked `USED`
+5. Same rule for status files
+6. Per session: max 5 new posts files + max 2 new WhatsApp message files + max 2 new status files. Ask the user before each new file.
+
+### Hashtag policy
+
+- Max 7 hashtags per post; **5 (2 generic + 3 specific) is the SEO sweet spot** — that's the default
+- Generic pool (always available): `#Aoneahsan` `#AhsanMahmood` `#Zaions` `#BestOpenSourceCommunityProject` `#TopFree` `#SaaSApp`
+- Per-post, pick 2 generic + 3 post-specific hashtags
+- Never keyword-stuff. Princeton GEO study (KDD 2024) shows it actively reduces AI-citation share by ~10%.
+
+### Honesty rules (IRON-SOLID — do not break)
+
+- Only describe features that exist in the live codebase as of the file's date
+- Native Update v3.0.0 backend = **Laravel HTTP only** (Firestore was removed in v3 — never claim Firestore support)
+- License is **MIT** — say so plainly
+- The plugin works on **iOS + Android via Capacitor**, NOT React Native
+- "OTA updates" mean **non-native JS/HTML/CSS bundle replacements** — they do not push native code changes
+- App Store / Play Store policies still apply — say so when relevant
+- No fabricated stars, downloads, or testimonials
+
+---
+
+## Run history
+
+| Date | Files generated | Notes |
+|---|---|---|
+| 2026-05-06 | `posts-batch-01.md` | First run. 10 long-form posts covering: problem framing → plugin intro → OTA deep-dive → store-update checks → in-app review → Laravel/Nova backend → CLI → example apps → v3.0.0 BREAKING story → getting-started CTA. Source of truth: `NATIVE-UPDATE_portfolio-info_2026-05-06.md`. |
+| 2026-05-06 | `whatsapp-messages-batch-01.md` | Same session. 30 short messages (~250–350 words each): feature pitches, comparisons, architecture explainers, build-in-public notes, honest-limit framing, integration walkthroughs. |
+| 2026-05-07 | `whatsapp-status-batch-01.md` | 30 status messages, originally ~120–180 words each. |
+| 2026-05-07 | All 3 files **rewritten** to NEW char limits: posts 2700–2900, messages 400–600, statuses 240–400. README + CLAUDE.md + AGENTS.md rule updated to reflect HARD char limits. Verified all 70 items in-spec. |
+| 2026-05-07 | `posts-batch-02.md` | 10 fresh long-form posts on different angles from batch 01: founder note, Capgo/Live-Updates comparison, security model, common OTA mistakes, multi-app setup, Nova admin tour, v3 migration retrospective, performance, telemetry, roadmap. Series tag: `#NativeUpdateInside`. All 10 verified at 2700–2900 chars. |
+
+---
+
+## Source of truth for facts
+
+Always cross-check claims against:
+
+- `/home/ahsan/Documents/01-code/projects/native-update/NATIVE-UPDATE_portfolio-info_2026-05-06.md` — current portfolio file
+- `/home/ahsan/Documents/01-code/projects/native-update/CLAUDE.md` — features + status + version
+- `/home/ahsan/Documents/01-code/projects/native-update/Readme.md` — public README
+- Live NPM page: https://www.npmjs.com/package/native-update
+- Live homepage: https://nativeupdate.aoneahsan.com
+
+If a fact is not in any of those, **do not write it**.