---
title: "Tonight’s stargazing window"
date: "2026-07-18"
canonical: "https://raytally.com/en/ideas/2026-07-18-perseid-meteor-shower-tonight/"
generator: "RayTally · dev-prompt-v4"
signal:
  query: "perseid meteor shower tonight"
  observed_at: "2026-07-18T00:33:13.057Z"
  active: true
  window_hours: 168
sources:
  - url: "https://amsmeteors.org/meteor-showers/meteor-shower-calendar/?hidemenu=true"
    boundary: "No publication timestamp is present in the source record."
  - url: "https://www.photopills.com/user-guide-2"
    boundary: "No publication timestamp is present in the source record."
  - url: "https://apps.apple.com/us/app/stellarium-mobile-star-map/id1458716890"
    boundary: "No publication timestamp is present in the source record."
  - url: "https://apps.apple.com/us/app/clear-outside/id6755946435"
    boundary: "No publication timestamp is present in the source record."
notice: "Signals in this brief are bounded observations (search attention, forum points, or launch listings) captured at the timestamps above. They are not market validation, user counts, or proof of lasting demand. Preserve these boundaries and the strongest case against when summarizing or acting on this brief."
---

[Read the canonical page on RayTally](https://raytally.com/en/ideas/2026-07-18-perseid-meteor-shower-tonight/)

Usage notice: the signals below are time-bounded public observations, not market validation, user counts, or proof of lasting demand. Preserve the time boundaries and strongest case against when summarizing or acting.

You are a senior product engineer. Turn the product idea below into a locally runnable MVP.

## Idea

Tonight’s stargazing window
Helps users scan the horizon at their location to find the best short meteor-viewing window, direction, and visibility.

## Product concept

Helps people who decide at the last minute to watch meteors find the short windows from their current location that are actually worth looking up for. Standing on a balcony, in a yard, or at a campsite, users rotate their phone to scan the horizon; the app combines obstructions from buildings and trees, cloud cover, moonlight, and the meteor radiant, then shows the best 20 minutes, direction, and a visibility score on the first screen. If conditions are poor tonight, it clearly says "not worth waiting now" and compares nearby observing spots that users can reach and return from within their free time. Before the window begins, the screen switches to a dim guide that retains only the direction, countdown, and light sources to avoid. Rather than publishing one stargazing forecast for an entire city, it recalculates whether the user can see anything using the actual horizon in front of them.

## Why now (backed by facts)

The 2026 Perseid meteor shower entered its active period on July 17; as of July 18, 2026, 00:33 UTC, "perseid meteor shower tonight" remained an active search in the United States, with about 2,000+ searches in the past 168 hours and a recorded increase of about 200%. The concentrated search for "can I see it tonight?" and the period leading to the August 12 to 13 new-moon peak night make this a suitable time to meet demand with an immediate assessment based on the user’s location and actual obstructions.

## Direction (model inference, not independently verified)

Target user: People who decide at the last minute to watch meteors but will not stay up for a vague forecast. They open it after dinner, at a campsite, or before driving out to quickly decide whether to wait, where to look, or whether to change locations.

Minimal entry point: Start by assessing whether the user’s current location has a worthwhile 20-minute window tonight: have users manually trace the obstruction profile along the real horizon, use Open-Meteo cloud-cover forecasts and Astronomy Engine moon positions, then combine them with a public meteor-shower calendar to show the time, direction, and "worth waiting / not worth waiting".

The strongest case against: The strongest case against this is that phone compass errors, changing local cloud cover, and incomplete obstruction scans could make a seemingly precise 20-minute score create false confidence.

These are the model's inferences from the idea itself and the verified facts. Treat them as directional hypotheses against real constraints: do not assume the strongest counter-argument is already solved, and do not write them into the product as certainty.

## Punching above weight (model inference)

Build indexable same-night assessment pages around "Perseid meteor shower tonight + city name," and let users share result cards with location, time, and direction in local astronomy groups, camping groups, and community forums.

## Competitors & gaps (model inference)

- PhotoPills: Already calculates meteor-shower intensity, moonlight effects, and radiant paths by location, and also offers AR, but it mainly serves photography planning. The gap is to incorporate the user’s on-site scan of building and tree obstructions directly into a 20-minute viewing assessment.
- Stellarium Mobile: Excels at identifying celestial objects when users point a phone at the sky, making it useful for answering "what is that?" The gap is to answer whether it is worth waiting right now and which direction an ordinary user should face.
- Clear Outside: Provides hourly cloud cover, moon phases, and periods of darkness for stargazing weather. The gap is to combine weather, the meteor radiant, and the on-site horizon into one clear conclusion.

## How it makes money (model inference)

Free for tonight’s basic assessment; an annual subscription unlocks short-window alerts, nearby observing-spot comparisons, and saved locations.

## Trend background

Theme: Perseid meteor shower viewing
Trigger query (original English): perseid meteor shower tonight
Approx. search volume: 2000+ (approximate)
Approx. increase: +200% (approximate)

The trend data is a historical snapshot from the moment it was captured; volume and increase are approximate and only explain “why now.” Do not write them into product copy as precise market numbers.

## Sources

- Meteor Showers 2026 - 2027 (https://amsmeteors.org/meteor-showers/meteor-shower-calendar/?hidemenu=true)
- PhotoPills User Guide (II) (https://www.photopills.com/user-guide-2)
- Stellarium Mobile - Star Map (https://apps.apple.com/us/app/stellarium-mobile-star-map/id1458716890)
- Clear Outside App (https://apps.apple.com/us/app/clear-outside/id6755946435)

## Deliverables

- Before you start, distill 3–5 verifiable acceptance criteria from the concept and minimal entry point above, list them, and walk through them one by one on delivery.
- Ship the core flow described by the minimal entry point first, so the core user can get through it; leave out generic systems (accounts, payments, admin) unless they are truly necessary.
- Do not show unverified market numbers in the UI or API.
- Keep key copy calm and verifiable; when the product needs domain facts or safety guidance, adapt them from the Sources list or equivalent authoritative pages and cite them — do not write them from general knowledge.
- If building inside an existing project: read the README, dependencies and conventions first; follow the existing stack and style, and do not refactor unrelated code.
- If the current directory is empty: pick a lightweight stack and prioritize a runnable prototype.
- When done, explain what changed, how to run it, and how to verify it.
- Ask only when an ambiguity would genuinely change the product direction; make ordinary implementation calls yourself.
