Short Overview
We need a tight, actionable, SEO-friendly docs guide that teaches Unity developers and QA how to capture Unity logs from mobile devices (Android & iOS) using Jahro (https://jahro.io) Snapshots. Keep it short, useful, and written in Jahro voice (clear, confident, slightly cheeky but not gimmicky).
Deliverables: markdown docs (ready for the site)
Who we’re writing for (ICP)
Primary audience:
Unity engineers (junior → senior; 1–5 yrs experience) working on mobile games.
Manual QA engineers testing mobile game builds.
Game designers and PMs who need reproducible bug reports.
Small-studio tech/product leads who want better dev/QA collaboration.
Tone: short, direct, technical where needed, but friendly — like a senior dev explaining how to stop wasting time on logs. Write simple English for bilingual readers.
Topic — general overview
Goal: explain what Snapshots are, why they matter for capturing Unity logs from mobile devices, and exactly how to use them (step-by-step). This guide should fulfil https://jahro.io/docs/snapshots documentation, but gonna be a separate Guide.
Target length: 1500–2500 words (comprehensive but scannable).
SEO requirements
Primary keyword targets:
Unity logs from mobile
Unity debug log
Unity logs Android
Unity logs iOS
Secondary (use where relevant)
unity adb logcat, unity Xcode console, mobile debug Unity, device logs,
Deliverables must include:
Suggested URL slug (e.g. /docs/snapshots-unity-logs-mobile-android-ios)
Meta title (≤ 60 chars) and meta description (120–155 chars)
Sidebar title - up to 30 characters
H1 (page title) and 3 alternative hero headlines (short)
Natural use of keywords — avoid stuffing. Aim for 1–2 occurrences of the primary keyword in title/intro + organic occurrences in headings/body.
SEO format rules:
Meta description length 120–155 chars.
Use H2/H3 headings that include keywords where natural.
Provide 3–5 suggested internal link targets (Watcher, Commands).
References & research
Required research sources:
Unity docs on device logging (Android & iOS).
Relevant StackOverflow, Unity Forum, and Reddit threads about device log problems and adb/Xcode friction.
PostHog-style long-form guides as a reference for tone/structure: https://posthog.com/tutorials/nextjs-cookie-banner
https://posthog.com/tutorials/embedded-analytics
https://posthog.com/blog/ai-community-answers
https://posthog.com/product-engineers/ab-testing-mistakes
Tone of voice & writing rules
Follow Jahro voice:
Short, direct sentences. One idea per sentence.
Use “you”, not “we” where possible.
Avoid fluff and marketing hype. Show value with concrete outcomes.
Use light charm where appropriate( allowed “debugging sucks”).
Follow AIDA / PAS where helpful: open with problem, show quick solution, then steps and proof.
100–3–1 rule: reader should get the point within 3 seconds / 1 screen.
Goals — why we’re publishing this
SEO: rank for “Unity logs from mobile devices” and related queries.
Product adoption: drive new and existing users to try Snapshots and complete first snapshot within 7 days.
Content for marketing: email blast, onboarding, forum/Reddit/Quora answers, and social posts.
Criteria of success (measurable / acceptance)
The guide is accepted when all of these are met:
✅ Delivered in Markdown with frontmatter.
✅ Meta title ≤60 chars; meta description 120–155 chars.
✅ URL slug suggested and H1 present.
✅ Primary keywords appear in title/intro and at least twice in the body (naturally).
✅ Includes step-by-step “Capture your first Snapshot” that a QA engineer can follow (no missing steps).
✅ Readability checks: short paragraphs, bullets, and H2/H3 structure.
✅ Tone follows Jahro voice (we’ll review).
✅ No plagiarism; everything original or properly quoted & cited.
