diff --git a/apps/web/src/pages/observe.astro b/apps/web/src/pages/observe.astro index b0e6ad6e4..cd020ded5 100644 --- a/apps/web/src/pages/observe.astro +++ b/apps/web/src/pages/observe.astro @@ -49,20 +49,18 @@ const screenSignals = [

Capgo Observe, beta

-

Find the version that needs attention.

-

- Compare native health, launch and WebView timing, and version-level signals with release markers for version, channel, and deployment date. -

+

Know when a release needs attention.

+

See what changed after your rollout, compare health by reported version, and move from a bad signal to the devices and logs behind it.

    -
  1. 01
    DeployA bundle is deployed to a channel.
  2. -
  3. 02
    ObserveCompare reported version health.
  4. -
  5. 03
    InvestigateUse Logs Insights to investigate a trend.
  6. +
  7. 01
    DeployMark the version, channel, and deployment date.
  8. +
  9. 02
    ObserveCompare reported health before support tickets arrive.
  10. +
  11. 03
    InvestigateFollow the trend into errors, versions, and devices.
@@ -85,9 +83,9 @@ const screenSignals = [
-

Your rollout context is already here

-

Know when a reported version needs attention.

-

Compare native health and timing across the selected period and each reported app version.

+

Stop treating production as a black box

+

Your rollout is only done when you know what happened next.

+

Observe gives every release a health view, then gives you the evidence to decide what deserves action.

@@ -107,9 +105,9 @@ const screenSignals = [
-

Compare reported versions

-

Find the version that needs attention.

-

Start with all-version health, then compare each reported native app version within the selected period.

+

See the release, not just the metric

+

Start broad. Narrow fast. Know where to look next.

+

Read all-version health, compare the versions that diverge, and use the release marker to connect the change to the impact.

Explore Live Updates
@@ -135,14 +133,14 @@ const screenSignals = [

From signal to evidence

-

Find the errors, versions, and devices behind a trend.

+

Do not hand your team a chart. Hand them the trail.

Observe

-

Compare the reported version that needs attention.

-

Compare a reported version's health and timing to decide what to investigate.

+

See which reported version changed the release picture.

+

Compare health and timing with the context of what you deployed, where, and when.

Logs Insights

@@ -173,8 +171,8 @@ const screenSignals = [

Observe every rollout

-

Start observing
your next rollout.

-

Keep deployment history, release health, and Logs Insights in one place.

+

Ship with proof,
not just hope.

+

Put deployment history, release health, and Logs Insights in one release workflow.

{m.cta_start_free({}, { locale })}
+ Deployment history @@ -185,7 +183,7 @@ const screenSignals = [
-

Go from rollout to evidence

+

One workflow from rollout to evidence

Pair Capgo Live Updates with Logs Insights to move from reported version health to errors, devices, and filtered raw action logs. diff --git a/docs/pr-screenshots/observe-marketing-story-desktop.webp b/docs/pr-screenshots/observe-marketing-story-desktop.webp new file mode 100644 index 000000000..c983ccca1 Binary files /dev/null and b/docs/pr-screenshots/observe-marketing-story-desktop.webp differ