-
-
Notifications
You must be signed in to change notification settings - Fork 25
[codex] Improve marketing page positioning #658
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
riderx
wants to merge
3
commits into
main
Choose a base branch
from
codex/marketing-pages-copy
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,116 @@ | ||
| # Product Marketing Context | ||
|
|
||
| *Last updated: 2026-05-10* | ||
|
|
||
| ## Product Overview | ||
| **One-liner:** Capgo helps Capacitor teams ship live app updates, fixes, and assets without waiting for app store review. | ||
| **What it does:** Capgo provides an open-source updater, cloud delivery, channels, rollbacks, analytics, device logs, and native build support for Capacitor apps. Teams use it to move web-layer changes fast while keeping native changes on the normal App Store and Google Play review path. | ||
| **Product category:** Capacitor live updates, OTA updates, CodePush alternative, Appflow alternative. | ||
| **Product type:** SaaS developer platform with open-source client/plugin. | ||
| **Business model:** Usage-based subscriptions with free trial, paid plans, credits/overages, enterprise options, and optional premium support. | ||
|
|
||
| ## Target Audience | ||
| **Target companies:** Indie apps, startups, agencies, and mobile teams running production Capacitor apps. | ||
| **Decision-makers:** Founder-developers, mobile leads, engineering managers, CTOs, and technical founders. | ||
| **Primary use case:** Ship urgent JavaScript, CSS, copy, and asset fixes without waiting days for store approval. | ||
| **Jobs to be done:** | ||
| - Recover quickly from production bugs and bad releases. | ||
| - Roll out updates safely by channel, audience, and version. | ||
| - Replace aging or shutting-down live update platforms without rebuilding the release pipeline. | ||
| **Use cases:** | ||
| - Emergency bug fixes. | ||
| - Staged rollouts and rollbacks. | ||
| - Appflow migration. | ||
| - Plugin and native build workflows. | ||
|
|
||
| ## Personas | ||
|
|
||
| | Persona | Cares about | Challenge | Value we promise | | ||
| |---------|-------------|-----------|------------------| | ||
| | Solo developer | Speed, low cost, simple setup | App store delays slow fixes and learning | Start free, ship first update quickly, pay only when it proves value | | ||
| | Mobile lead | Release safety, observability, team workflow | Bad deploys create support load and uncertainty | Channels, device logs, analytics, rollback, and predictable usage limits | | ||
| | CTO / founder | Business continuity, cost, vendor risk | Proprietary tools can shut down or become too expensive | Open-source updater, sustainable pricing, transparent infrastructure, migration path | | ||
| | Enterprise buyer | Compliance, support, SLAs, procurement | Live updates must fit governance and uptime expectations | SSO, custom domain, SOC 2 path, SLA, direct support, enterprise terms | | ||
|
|
||
| ## Problems & Pain Points | ||
| **Core problem:** Production mobile fixes often wait on app store review even when the broken code is web-layer JavaScript, CSS, copy, or assets. | ||
| **Why alternatives fall short:** | ||
| - Store-only releases are too slow for urgent fixes. | ||
| - All-in-one platforms can be expensive, rigid, or discontinued. | ||
| - DIY live update systems add maintenance and compliance risk. | ||
| **What it costs them:** Lost revenue, bad reviews, support volume, delayed campaigns, engineering context switching, and reduced trust in release velocity. | ||
| **Emotional tension:** Teams fear being stuck with a bad release in users' hands and no fast, controlled way to recover. | ||
|
|
||
| ## Competitive Landscape | ||
| **Direct:** Ionic Appflow, CodePush-style live update platforms, Capawesome live updates. | ||
| **Secondary:** Custom OTA infrastructure, CI/CD-only workflows, native-only release pipelines. | ||
| **Indirect:** Waiting for store review, manual support workarounds, delaying risky releases. | ||
|
|
||
| ## Differentiation | ||
| **Key differentiators:** | ||
| - Built specifically for Capacitor. | ||
| - Open-source updater and transparent backend ecosystem. | ||
| - Channels, rollbacks, analytics, device logs, and native build support. | ||
| - Sustainable pricing from indie through enterprise. | ||
| - Appflow migration positioning and human support. | ||
| **How we do it differently:** Capgo focuses on update delivery and release control rather than forcing teams into an all-in-one CI/CD suite. | ||
| **Why that's better:** Teams keep their existing build pipeline while adding a faster recovery path for web-layer changes. | ||
| **Why customers choose us:** Fast setup, lower cost than enterprise suites, open-source trust, Appflow continuity, and real production observability. | ||
|
|
||
| ## Objections | ||
|
|
||
| | Objection | Response | | ||
| |-----------|----------| | ||
| | Is this store compliant? | Native changes still go through store review; Capgo is positioned for web-layer updates, assets, configuration, and controlled rollouts. | | ||
| | What if usage grows unexpectedly? | Plans expose MAU, bandwidth, storage, build time, and credit-based overages so teams can scale by real usage. | | ||
| | Can we trust a smaller vendor? | Capgo emphasizes open source, transparent infrastructure, bootstrapped sustainability, public status, and human support. | | ||
|
|
||
|
coderabbitai[bot] marked this conversation as resolved.
|
||
| **Anti-persona:** Teams that need to bypass store rules for native-code changes or want a full proprietary CI/CD suite to replace their entire release process. | ||
|
|
||
| ## Switching Dynamics | ||
| **Push:** Store review delays, Appflow shutdown concerns, high platform cost, poor observability, brittle manual recovery. | ||
| **Pull:** Fast fixes, controlled rollout, rollback, open-source trust, lower entry price, migration help. | ||
| **Habit:** Existing CI/CD setup, store-only release muscle memory, fear of changing production update flow. | ||
| **Anxiety:** Compliance, migration complexity, unexpected usage bills, vendor longevity, support quality. | ||
|
|
||
| ## Customer Language | ||
| **How they describe the problem:** | ||
| - "We cannot wait days for app review when production is broken." | ||
| - "We need to ship a fix without forcing a full app release." | ||
| - "We need an Appflow alternative that will not disappear." | ||
| **How they describe us:** | ||
| - "Live updates for Capacitor." | ||
| - "CodePush for Capacitor." | ||
| - "A way to patch the app safely after release." | ||
| **Words to use:** live updates, OTA updates, production fix, rollback, channels, device logs, Appflow alternative, open source, store-compliant, no credit card. | ||
| **Words to avoid:** bypass, hack, unlimited everything, guaranteed approval. | ||
| **Glossary:** | ||
| | Term | Meaning | | ||
| |------|---------| | ||
| | Live update | A web-layer update delivered to an installed app without a store release | | ||
| | Channel | A rollout target such as production, beta, staging, or a customer segment | | ||
| | Rollback | Reverting users to a previous known-good bundle | | ||
| | MAU | Monthly active users used for plan sizing | | ||
|
|
||
| ## Brand Voice | ||
| **Tone:** Direct, practical, developer-friendly, transparent. | ||
| **Style:** Plain-language technical marketing with concrete proof and minimal hype. | ||
| **Personality:** Fast, honest, capable, pragmatic, community-minded. | ||
|
|
||
| ## Proof Points | ||
| **Metrics:** Public pages cite large-scale update volume, apps served, global infrastructure, uptime, and recognizable customer logos. | ||
| **Customers:** Public logo cloud and pricing page examples include apps such as Nana, Snowqueen, Shelf, Suez, and Janitor. | ||
| **Testimonials:** Existing testimonial sections highlight migration speed, support responsiveness, open-source trust, and cost savings. | ||
| **Value themes:** | ||
|
|
||
| | Theme | Proof | | ||
| |-------|-------| | ||
| | Speed | Ship fixes in minutes instead of waiting for review | | ||
| | Safety | Channels, staged rollout, rollback, device logs | | ||
| | Trust | Open-source updater, transparent backend, status/history | | ||
| | Cost control | Free trial, usage-based plans, credit-based overages | | ||
|
coderabbitai[bot] marked this conversation as resolved.
|
||
|
|
||
| ## Goals | ||
| **Business goal:** Convert more product-page visitors into free trials and qualified enterprise conversations. | ||
| **Conversion action:** Start free trial, view live update product details, or contact enterprise/support. | ||
| **Current metrics:** Not captured in repo context. | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.