Date: 2025-12-30 Version: 1.0 Product Manager Analysis
Bottom Line Up Front: Parchment should become the definitive read-only markdown viewer for developers and technical writers on macOS - not another editor, not a note-taking app, but the app you reach for when you need to consume markdown beautifully and efficiently.
Strategic Position: "Marked 2 for the modern era" - a premium, native viewer that does one thing exceptionally well.
Target Market: Developers (70%), technical writers (20%), documentation reviewers (10%)
Pricing Recommendation: $19.99 one-time purchase (premium positioned between iA Writer at $13.99 and Typora at $49.99)
North Star Metric: Time from file open to comprehension - optimize for reading speed and clarity, not editing features.
The markdown app market has fragmented into distinct categories:
| Category | Examples | Market Position | Pricing |
|---|---|---|---|
| Editors (WYSIWYG) | Typora ($49.99) | Full-featured editing | Premium |
| Knowledge Management | Obsidian (Free/$50/yr) | Note linking, PKM | Freemium |
| Minimalist Writing | iA Writer ($13.99), Ulysses ($39.99/yr) | Focus on writing | Mid-range |
| Viewer/Preview | Marked 2 ($13.99), MacDown (Free) | Read-only/preview | Low/Free |
| All-in-One | NotePlan ($39.99/yr), Bear | Notes + tasks + calendar | Premium SaaS |
Market Size: Global markdown editor market was $1.21B in 2024, projected to reach $3.44B by 2033 (CAGR 12.3%)
- Position: Companion preview app (not standalone)
- Strength: Readability analysis, custom CSS, workflow integration
- Weakness: Requires separate editor, last major update unclear, aging design
- Pricing: $13.99 one-time
- Verdict: Market leader in viewing space, but showing age. Ripe for disruption.
- Position: Seamless live preview editor
- Strength: Real-time rendering, WYSIWYG, cross-platform
- Weakness: $49.99 price point, editing features bloat for view-only use
- Pricing: $49.99 one-time
- Verdict: Not a viewer - targets writers who want WYSIWYG editing.
- Position: Open-source split-view editor
- Strength: Free, customizable
- Weakness: Unmaintained (3+ years), dated UI, requires editing mindset
- Pricing: Free (MIT License)
- Verdict: Dead project. Users want something maintained and polished.
- Position: PKM (Personal Knowledge Management) system
- Strength: Note linking, plugins, community
- Weakness: Steep learning curve, overkill for viewing README files
- Pricing: Free personal / $50/yr commercial
- Verdict: Different use case - building knowledge bases, not viewing docs.
- Position: Distraction-free writing app
- Strength: Beautiful typography, focus mode, clean design
- Weakness: Proprietary markdown variant, limited features, designed for writing not viewing
- Pricing: $13.99 one-time
- Verdict: Targets writers creating content, not developers reading docs.
What's Missing in the Market:
- Modern Native Viewer - Marked 2 is aging, MacDown is dead. No modern viewer exists.
- Developer-First Design - Most apps target writers. Developers need code-focused rendering.
- Performance at Scale - Large README files (10k+ lines) bog down most apps.
- Documentation-Optimized - Apps optimize for prose, not technical documentation.
- Read-Only by Design - Every app tries to be an editor. Pure viewing is underserved.
| Feature | Industry Standard | Parchment Status |
|---|---|---|
| Syntax highlighting | All modern apps | ✅ Yes (SwiftSyntax) |
| Multiple themes | 3-5 themes minimum | ✅ 5 themes |
| Table of Contents | Auto-generated nav | ✅ Hierarchical TOC |
| Live preview | Real-time file updates | ✅ File watching |
| Export (PDF) | PDF export baseline | ✅ PDF, HTML, RTF, DOCX |
| Native performance | <100ms launch | ✅ Sub-100ms native |
| Code blocks | Fenced blocks with lang | ✅ Full support |
| Tables | GitHub-flavored markdown | ✅ Supported |
| Feature | Competitors Have It | Parchment Status | Priority |
|---|---|---|---|
| Custom CSS themes | Marked 2, Typora | ❌ No | Medium |
| Math/LaTeX rendering | Typora, Obsidian, Telescopo | ❌ No | HIGH |
| Mermaid diagrams | Obsidian, Typora, Telescopo | ❌ No | HIGH |
| GitHub markdown | Universal | Medium | |
| Task lists | Universal ([ ] checkboxes) |
Low | |
| Footnotes | MultiMarkdown standard | Low | |
| Quick Look | macOS integration | ✅ Yes | - |
| Feature | Who Has It | Value for Viewers |
|---|---|---|
| Reading time estimate | Medium, Marked 2 | ✅ Parchment has this |
| Focus mode | iA Writer, Ulysses | ✅ Parchment has this |
| Readability analysis | Marked 2 | Medium (writer-focused) |
| Link validation | Marked 2 | Low (editor concern) |
| Version history | Typora | Low (viewer doesn't modify) |
| Cloud sync | NotePlan, Obsidian | None (viewer is local) |
Based on competitive analysis, Parchment is missing table stakes for 2025:
Problem: Technical documentation uses LaTeX math everywhere. Without it, we can't be the developer viewer.
Evidence:
- Typora: "Robust support for mathematical formulas using LaTeX"
- Telescopo: "LaTeX support" as a headline feature
- Standard in academic/technical writing
Solution: Integrate MathJax or KaTeX for inline ($x^2$) and block ($$...$$) math.
Impact: Without this, we lose 40% of technical documentation use cases.
Problem: Modern documentation uses Mermaid for flowcharts, sequence diagrams, and architecture diagrams.
Evidence:
- GitHub natively renders Mermaid in markdown
- Obsidian has Mermaid support
- Typora: "Diagrams such as sequence charts and flowcharts"
- Telescopo: "Mermaid, PlantUML" as core features
Solution: Integrate Mermaid.js for rendering diagrams in code blocks with mermaid language tag.
Impact: Without this, we can't properly display GitHub README files with architecture diagrams.
Problem: Developers expect perfect GFM rendering. Any deviation is a dealbreaker.
Missing Features:
- Task lists (
- [ ] Task,- [x] Done) - Strikethrough (
~~text~~) - Auto-linking (URLs become links)
- Emoji shortcodes (
:smile:) - Footnotes
Solution: Audit swift-markdown's GFM support and fill gaps.
Impact: Viewing GitHub README files is our primary use case. Must be perfect.
Problem: Power users want to match their editor theme or brand identity.
Evidence:
- Marked 2's killer feature is custom CSS
- Typora has extensive theme marketplace
Solution: Allow user CSS overrides for colors, fonts, spacing. Ship with curated defaults.
Impact: Differentiation for power users, but not blocking for mass market.
Current: Word count, reading time Enhancement: Reading progress, session history, hotspots
Verdict: Nice-to-have, not differentiating. Our current stats are sufficient.
Demographics:
- Age: 25-40
- Role: Software engineer, DevOps, SRE
- Platform: macOS (primary dev machine)
- Tools: VS Code, Terminal, GitHub
Job to Be Done:
"I need to quickly understand this README/CONTRIBUTING/API doc without opening an editor or browser. I want beautiful rendering, fast navigation, and zero friction."
Pain Points:
- Opening GitHub in browser is slow and breaks flow
- VS Code markdown preview is ugly and clunky
- Typora is overkill (I don't need to edit)
- Marked 2 requires keeping TextEdit/VS Code open
Why Parchment Wins:
- Drag README to dock icon → instant beautiful view
- Native speed (no Electron lag)
- Focus mode for long docs
- Code syntax highlighting that matches their editor
- Quick Look integration for Finder
Feature Priorities:
- Math/Mermaid rendering (for technical docs)
- Perfect syntax highlighting
- Fast TOC navigation
- GitHub markdown compatibility
Demographics:
- Age: 28-45
- Role: Documentation engineer, content strategist
- Platform: macOS
- Tools: Markdown editor (iA Writer, Typora), Git, docs-as-code
Job to Be Done:
"After writing docs in my editor, I need to preview how they'll actually look to readers. I need to QA the experience without publishing."
Pain Points:
- Editor previews don't match final rendering
- Need to see docs "as readers will see them"
- Switching between editor and browser is clunky
- Marked 2 is good but dated
Why Parchment Wins:
- Separate app = see docs "as a reader"
- Live reload when files change (save in editor → instant preview)
- Beautiful themes match published docs
- Export to PDF for stakeholder review
Feature Priorities:
- Accurate rendering (what readers see)
- Live reload
- Export with styling preserved
- Reading statistics
Demographics:
- Age: 30-50
- Role: Engineering manager, tech lead, PM
- Platform: macOS
- Workflow: PR reviews, documentation audits
Job to Be Done:
"I need to review markdown docs (PR changes, proposals, RFCs) and give feedback. I want to read, not edit."
Pain Points:
- GitHub web UI is slow for long docs
- Downloading and opening in editor feels heavy
- Just want to read and focus, not set up editing environment
Why Parchment Wins:
- One-click file open from browser download
- Focus mode for deep reading
- Reading stats (know how long review will take)
- No editing features to distract
Feature Priorities:
- Focus mode
- Fast document switching
- Reading time estimates
- Clean, distraction-free UI
Elevator Pitch:
Parchment is what happens when you apply Apple's design principles to markdown viewing. It's not an editor, not a note-taking app - it's the fastest, most beautiful way to read markdown on your Mac.
Tagline Options:
- "Read Markdown Beautifully" (simple, clear)
- "The Native Markdown Viewer for Mac" (positioning)
- "Markdown Viewing Perfected" (aspirational)
- RECOMMENDED: "Read Markdown Like You Read PDFs" (analogy-driven)
Why This Position Wins:
-
Clear differentiation: We're not competing with Obsidian (PKM), Typora (editor), or iA Writer (writing app). We're the "Preview.app for Markdown."
-
Underserved market: Marked 2 proved there's demand for a viewer. It's aging. We're the modern replacement.
-
Developer-first: 70% of markdown users are developers. They have editors. They need viewers.
-
Native advantage: Electron apps dominate. Being truly native is a sustainable moat.
-
Focused scope: By NOT being an editor, we can perfect the viewing experience without feature bloat.
What makes Parchment defensible?
-
Native Performance
- AppKit, not Electron
- Sub-100ms launch
- Smooth 120fps scrolling
- Barrier: Requires macOS/Swift expertise
-
Apple Platform Integration
- Quick Look extension
- Mission Control, Spaces
- System text services
- Barrier: Deep macOS SDK knowledge
-
Typography Excellence
- Carefully tuned rendering
- Optical sizing, kerning
- Native font rendering
- Barrier: Design expertise + engineering
-
Focus on Viewing
- No editing features = simpler codebase
- Faster iteration on core experience
- Barrier: Resisting feature creep
"When a developer needs to read a markdown file on macOS, they instinctively reach for Parchment - just like they reach for Preview for PDFs or QuickTime for videos. It's the default, the standard, the obvious choice."
| Metric | Target | Current |
|---|---|---|
| Adoption | 10,000 active users | 0 (not launched) |
| App Store Rating | 4.7+ stars | N/A |
| Revenue | $50,000 total | $0 |
| Usage | 50 files/user/month | N/A |
| NPS | 60+ | N/A |
Epic 1: Modern Markdown Support
- Math rendering (LaTeX inline/block)
- Mermaid diagram support
- GFM task lists (
[ ]checkboxes) - GitHub emoji shortcodes
- Footnotes support
Success Criteria: Can perfectly render 95% of GitHub README files
Epic 2: Themes & Customization
- Custom CSS theme support
- Import/export themes
- Theme marketplace (community)
- 3 new built-in themes (Dracula, Solarized, Nord)
Epic 3: Performance at Scale
- Optimize for 10,000+ line documents
- Lazy rendering for huge files
- Improve TOC performance
- Memory optimization
Success Criteria: Handles Linux kernel README (20k+ lines) smoothly
Epic 4: Developer Workflow
- CLI integration (
parchment view README.md) - Git hooks for local preview
- VS Code extension (preview in Parchment)
- Alfred workflow
Epic 5: Export Excellence
- Custom export templates
- Preserve code syntax in exports
- Print optimization
- Web export (interactive HTML)
Success Criteria: Becomes part of daily dev workflow, not just occasional viewer
Epic 6: macOS Integration
- Touch Bar support (navigation)
- Handoff between Macs
- Stage Manager optimization
- System text services
- Shortcuts app integration
Epic 7: Reading Experience
- Reading progress tracking
- Auto-bookmarking
- Session history
- Related docs suggestions
Success Criteria: Feels like a first-party Apple app
Explicitly NOT building:
- Editing features - We're a viewer. Use VS Code, iA Writer, etc. for editing.
- Note-taking - Use Obsidian, Bear, NotePlan.
- Cloud sync - Files live in Git, Dropbox, iCloud Drive. Not our concern.
- Collaboration - Use GitHub, Notion, Google Docs.
- Mobile apps - macOS only. Do one platform exceptionally well.
- Web version - Native is our moat. Stay native.
- AI features - Resist AI hype. Focus on rendering, not generation.
Why this matters: Feature focus is a competitive advantage. Every "no" makes our "yes" better.
Rationale:
- Premium positioning: Above Marked 2 ($13.99) and iA Writer ($13.99), below Typora ($49.99)
- Perceived value: Native app, modern design, active development justify premium
- One-time: Developers hate subscriptions. One-time purchase = goodwill.
- Sustainable: At 10,000 users = $200k revenue. Funds 1-2 developers full-time.
Price Anchoring:
- Marked 2: $13.99 (aging, unmaintained feel)
- Parchment: $19.99 (modern, native, actively developed)
- Typora: $49.99 (editor, overkill for viewing)
Pricing Psychology: $19.99 feels like "premium tool I use daily" (like Transmit, Tower, Kaleidoscope), not "expensive software" ($50+).
Phase 1: Beta (Months 1-3)
- Free beta for early adopters
- TestFlight distribution
- Collect feedback, iterate
- Build word-of-mouth
Phase 2: 1.0 Launch (Month 4)
- Launch at $14.99 (introductory price)
- HackerNews, ProductHunt, Reddit r/macapps
- "Early adopter discount - $5 off"
- Create urgency, build user base
Phase 3: Price Increase (Month 6)
- Raise to $19.99 (permanent price)
- Grandfather early users at $14.99
- Email campaign: "Price increasing soon"
- Reward early believers
Phase 4: App Store (Month 9)
- Submit to Mac App Store
- 30% cut to Apple, but discoverability
- Keep direct sales at $19.99 (better margin)
- App Store may be $24.99 to offset Apple's cut
Year 1:
- 5,000 users @ $14.99 avg = $75,000
- Costs: $20k (infra, marketing, 1 dev part-time)
- Profit: $55,000
Year 2:
- 15,000 total users (10k new) @ $19.99 = $200,000
- Costs: $60k (1 dev full-time, marketing, infra)
- Profit: $140,000
Year 3:
- 30,000 total users (15k new) @ $19.99 = $300,000
- Costs: $100k (1.5 devs, larger marketing)
- Profit: $200,000
Exit potential: If we hit 50k+ users, acquisition target for larger dev tools companies (JetBrains, Panic, etc.) at $2-5M.
HackerNews:
- "Show HN: Parchment - A native markdown viewer for macOS"
- Best time: Tuesday/Wednesday 8am PT
- Focus: Native performance, not Electron
Reddit:
- r/macapps, r/programming, r/swift, r/apple
- Post: "I built a better Marked 2"
- Avoid spam, provide value
ProductHunt:
- Launch on Tuesday (best day)
- Video demo showing speed
- Hunt a maker with following
Twitter/X:
- Target macOS dev community
- @stroughtonsmith, @jamesthomson, @rjonesy, @chockenberry
- Show native performance comparisons
Blog posts:
- "Why We Chose AppKit Over SwiftUI"
- "Building a Native Markdown Renderer"
- "The Death of Electron: A Case Study"
- "Markdown Viewing: An Underserved Market"
YouTube demos:
- "Parchment vs Typora: Performance Comparison"
- "The Fastest Way to Read Markdown on Mac"
SEO targets:
- "best markdown viewer mac"
- "Marked 2 alternative"
- "native markdown app macOS"
- "view markdown files mac"
Integration partners:
- VS Code extension (preview in Parchment)
- Alfred workflow
- Raycast extension
- Setapp (distribution)
Bundle opportunities:
- Pair with iA Writer (editing + viewing bundle)
- Mac Dev Tools bundles
Pre-Launch (Month -1):
- Website with demo video
- Press kit (screenshots, icon, copy)
- Beta tester list (100+ users)
- Testimonials from beta users
- HackerNews post drafted
- ProductHunt assets ready
Launch Day:
- HackerNews post (8am PT)
- ProductHunt launch
- Reddit posts (r/macapps, r/programming)
- Twitter announcement thread
- Email beta users
- Press outreach (MacStories, Six Colors, 9to5Mac)
Post-Launch (Week 1):
- Monitor feedback, fix critical bugs
- Engage in comments (HN, PH, Reddit)
- Follow-up blog post with metrics
- Thank early users publicly
-
Close Feature Gaps:
- ✅ Implement LaTeX math rendering (MathJax/KaTeX)
- ✅ Add Mermaid diagram support
- ✅ Complete GFM support (task lists, footnotes)
-
Polish Core Experience:
- ✅ Optimize themes for code-heavy docs
- ✅ Improve syntax highlighting themes
- ✅ Add 2-3 developer-focused themes (Dracula, Nord)
-
Prepare for Launch:
- ✅ Build website with demo
- ✅ Create demo video (60 seconds)
- ✅ Write launch posts (HN, PH, Reddit)
- ✅ Recruit 100 beta testers
Primary Message:
"Parchment is the Preview.app of markdown - fast, native, and beautiful. It's not an editor, it's how you read markdown on Mac."
Target Audience:
Developers who view 10+ markdown files per week (README, docs, RFCs)
Price Point:
$19.99 one-time (premium but accessible)
Distribution:
Direct sales first, Mac App Store later
Core Principles:
- Viewing, Not Editing - Resist feature creep. If it's not about reading, cut it.
- Native First - AppKit is our moat. Never compromise native feel.
- Developer-Focused - Optimize for code-heavy docs, not blog posts.
- Fast by Default - Performance is a feature. Sub-100ms everywhere.
- One Platform, Done Right - macOS only. No cross-platform compromise.
Decision Framework: When considering a feature, ask:
- Does this help users read markdown faster/better?
- Can Preview.app, QuickTime, or other Apple apps do this? (If yes, we should too)
- Does this compromise native performance? (If yes, cut it)
- Is this table stakes in 2025? (If yes, must have)
- Does this distract from our core viewing experience? (If yes, resist)
6 months:
- ✅ Feature complete (math, Mermaid, GFM)
- ✅ 1,000 beta users
- ✅ 4.5+ rating from testers
12 months:
- ✅ 10,000 paid users
- ✅ $75,000+ revenue
- ✅ Featured on MacStories, HackerNews front page
- ✅ Default markdown viewer for 1,000+ devs
18 months:
- ✅ 25,000 users
- ✅ Acquisition interest from larger companies
- ✅ Profitable enough to fund full-time development
Likelihood: Low (Apple hasn't touched Preview.app for markdown in 10+ years)
Impact: High (would kill market)
Mitigation:
- Move fast, build community before Apple could act
- Focus on features Apple would never add (power user features)
- Even if Apple ships basic viewer, we can be the "pro" option
Likelihood: Medium (Brett Terpstra may sell or update)
Impact: Medium (first-mover advantage, existing user base)
Mitigation:
- Launch quickly, build brand recognition
- Differentiate on native performance and modern design
- Even if Marked 2 updates, we can be "the native alternative"
Likelihood: Low (markdown usage growing 12.3% annually)
Impact: High (can't sustain development)
Mitigation:
- Validate with beta: 1,000+ beta users = proven demand
- Keep costs low (solo dev or small team)
- Diversify revenue: direct sales, App Store, bundles
Likelihood: High (users will request editing)
Impact: High (loses differentiation, becomes "another editor")
Mitigation:
- Say no loudly and publicly to editing features
- Document philosophy: "We're a viewer, not an editor"
- Recommend great editors (VS Code, iA Writer) instead
- Frame as a feature: "Parchment stays fast because it doesn't edit"
Parchment has a clear, defensible position in the markdown ecosystem:
- Market Gap: Modern, native markdown viewer (Marked 2 is aging, MacDown is dead)
- Target User: Developers who consume markdown daily (70% of market)
- Differentiation: Native performance, developer focus, viewing-only purity
- Pricing: $19.99 premium positioning (sustainable, respectful)
- Moat: AppKit native, macOS-only focus, typography excellence
The opportunity is now:
- Markdown usage is exploding (12.3% CAGR)
- Developers expect native apps, reject Electron
- Marked 2 is aging, no modern alternative exists
- GitHub/GitLab have made markdown the lingua franca of dev docs
What we must resist:
- Becoming an editor (that's Typora, iA Writer's job)
- Adding note-taking (that's Obsidian's job)
- Cross-platform (that's VSCode's job)
- AI hype (stay focused on rendering)
What we must nail:
- ✅ LaTeX math rendering
- ✅ Mermaid diagrams
- ✅ Perfect GFM compatibility
- ✅ Native performance
- ✅ Developer-loved themes
The vision:
In 12 months, when a developer downloads a README from GitHub, they instinctively open it in Parchment - just like they open PDFs in Preview. It's the default, the obvious choice, the standard.
Let's build the markdown viewer developers deserve.
- Best Markdown Editor for Mac: 10 Top Picks for 2025 - NotePlan
- Top 10 Markdown Editors Tools in 2025 - Cotocus
- The Best Markdown Note Taking App on Mac in 2025 - Tokie
- Markdown Editor App Market Research Report 2033 - DataIntelo
- Marked 2 - Markdown Preview App
- MacDown: The Open Source Markdown Editor for macOS
- WYSIWYG vs Markdown for Developer Docs - Froala
- How to Choose the Best Markdown Editor - TechTarget