Skip to content

Commit 3ce1d5f

Browse files
authored
Merge pull request #884 from Cap-go/codex/observe-product-page-refined
fix(web): sharpen Observe product story
2 parents bfe3e59 + 1356a0d commit 3ce1d5f

3 files changed

Lines changed: 38 additions & 41 deletions

File tree

813 KB
Loading

apps/web/src/pages/observe.astro

Lines changed: 38 additions & 41 deletions
Original file line numberDiff line numberDiff line change
@@ -7,9 +7,9 @@ import { getRelativeLocaleUrl } from '@/services/links'
77
88
const locale = Astro.locals.locale
99
const brand = Astro.locals.runtimeConfig.public.brand
10-
const title = brand + ' Observe | Release health for Capacitor apps'
10+
const title = brand + ' Observe | Version health after a rollout'
1111
const description =
12-
'See native app health, launch and WebView timing, version-by-version signals, and release markers in the Capgo console. Use Logs to investigate device update history.'
12+
'Compare reported native app health, launch and WebView timing, and version-level signals with release markers for version, channel, and deployment date. Use Logs Insights to investigate errors, versions, and devices.'
1313
const registerUrl = getRelativeLocaleUrl(locale, 'register')
1414
const logsDocsUrl = getRelativeLocaleUrl(locale, 'docs/webapp/logs')
1515
const liveUpdateUrl = getRelativeLocaleUrl(locale, 'live-update')
@@ -25,20 +25,20 @@ const serviceLdJson = createServiceLdJson(Astro.locals.runtimeConfig.public, {
2525
const content = {
2626
title,
2727
description,
28-
image: Astro.locals.runtimeConfig.public.baseUrl + '/social/capgo-live-update.png',
28+
image: Astro.locals.runtimeConfig.public.baseUrl + '/social/capgo-observe.png',
2929
ldJSON: createLdJsonGraph(Astro.locals.runtimeConfig.public, serviceLdJson, { includeOrganization: true }),
3030
}
3131
3232
const proofPoints = [
33-
['Native health by version', 'Read the visible version breakdown alongside issue-free device counts, launches, and runtime timing.'],
34-
['Release context built in', 'Keep rollout markers near the signals so your team can read app health and timing alongside recent deployment decisions.'],
35-
['A direct path to Logs', 'Move from a dashboard signal to Logs, update actions, and device diagnostic history.'],
33+
['Read release health', 'See issue-free devices, native issues, launch P90, and WebView P90 for the reported versions in one view.'],
34+
['Keep rollout context', 'Use release markers for version, channel, and deployment date as you read the signals.'],
35+
['Follow the evidence in Logs', 'Use grouped failures, affected versions, devices, and action logs to investigate a trend.'],
3636
]
3737
3838
const screenSignals = [
39-
['01', 'Version breakdown', 'Compare device health and timing across the visible native app versions in the selected period.'],
40-
['02', 'Release markers', 'Read performance and issue signals alongside the bundle and channel events shown as context.'],
41-
['03', 'Action breakdown', 'Separate launches, WebView loads, native issues, and update activity before opening a device trail.'],
39+
['01', 'All versions summary', 'Read issue-free devices, native issues, launch P90, and WebView P90 before narrowing your investigation.'],
40+
['02', 'Version breakdown', 'Compare reported app versions when health or timing differs from the overall picture.'],
41+
['03', 'Action breakdown', 'Separate launches, WebView loads, native issues, and update activity while you investigate a trend in Logs Insights.'],
4242
]
4343
---
4444

@@ -49,23 +49,20 @@ const screenSignals = [
4949
<div class="observe-hero-grid">
5050
<div>
5151
<p class="observe-kicker"><span aria-hidden="true"></span> Capgo Observe, beta</p>
52-
<h1>Every rollout leaves a signal.</h1>
52+
<h1>Find the version that needs attention.</h1>
5353
<p class="observe-statement">
54-
See native app health and timing alongside recent rollout markers, so your team can decide what deserves a closer look before support tickets tell you.
55-
</p>
56-
<p class="lead observe-lead">
57-
Observe puts native app health, launch and WebView timing, version distribution, and release markers on the same operational surface as your Capgo deployments.
54+
Compare native health, launch and WebView timing, and version-level signals with release markers for version, channel, and deployment date.
5855
</p>
5956
<div class="observe-actions">
6057
<a class="btn btn-lg btn-primary" href={registerUrl}>{m.cta_start_free({}, { locale })}</a>
61-
<a class="observe-link" href="#signals">See what Observe tracks <span aria-hidden="true">↓</span></a>
58+
<a class="observe-link" href="#signals">See the evidence flow <span aria-hidden="true">↓</span></a>
6259
</div>
6360
</div>
6461

6562
<ol class="observe-rail" aria-label="Release health workflow">
66-
<li><span>01</span><div><strong>Publish</strong><small>A bundle reaches a channel.</small></div></li>
67-
<li><span>02</span><div><strong>Observe</strong><small>Health and timing across the period.</small></div></li>
68-
<li><span>03</span><div><strong>Investigate</strong><small>Logs reveal the device-level path.</small></div></li>
63+
<li><span>01</span><div><strong>Deploy</strong><small>A bundle is deployed to a channel.</small></div></li>
64+
<li><span>02</span><div><strong>Observe</strong><small>Compare reported version health.</small></div></li>
65+
<li><span>03</span><div><strong>Investigate</strong><small>Use Logs Insights to investigate a trend.</small></div></li>
6966
</ol>
7067
</div>
7168

@@ -88,9 +85,9 @@ const screenSignals = [
8885
<section class="section observe-proof" id="signals">
8986
<div class="shell">
9087
<div class="observe-intro">
91-
<p class="eyebrow eyebrow--blue">Release health, in context</p>
92-
<h2 class="h2-section">Make rollout decisions with evidence, not a hunch.</h2>
93-
<p class="lead">Observe is focused on the question that follows every deployment: what changed for the app your users are running?</p>
88+
<p class="eyebrow eyebrow--blue">Your rollout context is already here</p>
89+
<h2 class="h2-section">Know when a reported version needs attention.</h2>
90+
<p class="lead">Compare native health and timing across the selected period and each reported app version.</p>
9491
</div>
9592

9693
<div class="observe-proof-grid">
@@ -110,12 +107,9 @@ const screenSignals = [
110107
<section class="section observe-reading bg-grid grain" id="screen">
111108
<div class="shell observe-reading-grid">
112109
<div class="observe-intro observe-intro--left">
113-
<p class="eyebrow eyebrow--blue">Read the signals</p>
114-
<h2 class="h2-section">The dashboard puts release context beside app telemetry.</h2>
115-
<p class="lead">
116-
Start with the all-version summary, then narrow the selected period and read the visible version breakdown. Every layer stays grounded in native telemetry and the
117-
release history your team already manages in Capgo.
118-
</p>
110+
<p class="eyebrow eyebrow--blue">Compare reported versions</p>
111+
<h2 class="h2-section">Find the version that needs attention.</h2>
112+
<p class="lead">Start with all-version health, then compare each reported native app version within the selected period.</p>
119113
<a class="observe-link" href={liveUpdateUrl}>Explore Live Updates <span aria-hidden="true">→</span></a>
120114
</div>
121115

@@ -140,20 +134,22 @@ const screenSignals = [
140134
<section class="section observe-diagnose" id="logs">
141135
<div class="shell">
142136
<div class="observe-diagnose-head">
143-
<p class="eyebrow eyebrow--blue">Observe plus Logs</p>
144-
<h2 class="h2-section">A chart tells you where to look. Logs tell you what happened.</h2>
137+
<p class="eyebrow eyebrow--blue">From signal to evidence</p>
138+
<h2 class="h2-section">Find the errors, versions, and devices behind a trend.</h2>
145139
</div>
146140

147141
<div class="observe-diagnose-grid">
148142
<article>
149143
<p class="observe-label">Observe</p>
150-
<h3>Read which visible versions differ in health and timing.</h3>
151-
<p>Use the health, timing, issue, and version views alongside release markers to decide what deserves investigation.</p>
144+
<h3>Compare the reported version that needs attention.</h3>
145+
<p>Compare a reported version's health and timing to decide what to investigate.</p>
152146
</article>
153147
<article class="observe-logs">
154148
<p class="observe-label">Logs Insights</p>
155-
<h3>Inspect a device’s update journey.</h3>
156-
<p>Filter update events by time and action, then open a device history to inspect the checks, downloads, installs, policy blocks, or rollbacks behind the signal.</p>
149+
<h3>Identify the errors, versions, and devices behind the trend.</h3>
150+
<p>
151+
Use Logs Insights to group errors by category, follow the daily trend, and identify affected versions and devices. Then open filtered raw action logs for the details.
152+
</p>
157153
<a class="observe-link" href={logsDocsUrl}>Read the Logs guide <span aria-hidden="true">→</span></a>
158154
</article>
159155
</div>
@@ -176,22 +172,23 @@ const screenSignals = [
176172

177173
<section class="section final bg-grid grain" id="cta">
178174
<div class="shell">
179-
<p class="eyebrow eyebrow--blue">Keep the release loop closed</p>
180-
<h2><span class="name">Observe the rollout.</span><br />Move with confidence.</h2>
181-
<p class="tagline">Keep Capgo deployments in view beside native app health and device evidence.</p>
175+
<p class="eyebrow eyebrow--blue">Observe every rollout</p>
176+
<h2><span class="name">Start observing</span><br />your next rollout.</h2>
177+
<p class="tagline">Keep deployment history, release health, and Logs Insights in one place.</p>
182178
<a class="btn btn-lg btn-primary btn-cta" href={registerUrl}>{m.cta_start_free({}, { locale })}</a>
183179
<div class="hero-meta hero-meta--cta">
184-
<span><span class="check">+</span> Native app health</span>
185-
<span><span class="check">+</span> Release context</span>
186-
<span><span class="check">+</span> Device diagnostics</span>
180+
<span><span class="check">+</span> Deployment history</span>
181+
<span><span class="check">+</span> Native health</span>
182+
<span><span class="check">+</span> Error and device evidence</span>
187183
</div>
188184
</div>
189185
</section>
190186

191187
<div class="shell seo-bridge">
192-
<h2 class="h2-section">Keep going from Observe</h2>
188+
<h2 class="h2-section">Go from rollout to evidence</h2>
193189
<p>
194-
Pair <a href={liveUpdateUrl}>Capgo Live Updates</a> with <a href={logsDocsUrl}>Logs</a> to understand the update journey from a rollout signal down to a device's history.
190+
Pair <a href={liveUpdateUrl}>Capgo Live Updates</a> with <a href={logsDocsUrl}>Logs Insights</a> to move from reported version health to errors, devices, and filtered raw action
191+
logs.
195192
</p>
196193
</div>
197194
</div>
-21.4 KB
Loading

0 commit comments

Comments
 (0)