Run a quarterly parking-app trend and competitor evidence review

[lightcloud00]

Outcome

Turn changing parking-app and iOS patterns into explicit experiments without copying competitors or bloating the privacy-first MVP.

Baseline snapshot

On 2026-08-18, a reproducible U.S. iTunes Search API sample across find my car, parking reminder, and parking meter timer returned 66 unique apps. Description mentions were directional only: timer/meter 37, photo/note 24, history 24, automatic/Bluetooth 18, sharing 12, Watch/widget 10, offline 7, and AR 3. Forty-seven had a 2026 update date. Search results are relevance-ranked samples, not market share.

Quarterly plan

• Repeat the same queries, country, entity, limit, timestamp, and deduplication method.
• Record exact App Store IDs, update dates, business models, privacy labels, ratings volume, and claimed features for relevant direct competitors.
• Review Apple platform changes and current Human Interface/App Review guidance.
• Compare support feedback and ParkNudge scorecard evidence.
• Route a hypothesis to an existing issue or open one with metric, cost, privacy impact, stop rule, and evidence gate.
• Explicitly close ideas that add background tracking, weak demand, or poor unit economics.

Candidate lanes

• Live Activity: Evaluate Live Activity for meter status as a Pro v1.1 feature #12
• Opt-in automatic suggestions, widgets, Watch: Evaluate opt-in automatic parking suggestions and companion surfaces #13
• Custom product pages: Create intent-specific App Store custom product pages #17
• Localization: Localize ParkNudge from territory and search-intent evidence #19
• Offline navigation and sharing remain hypotheses, not commitments.

Guardrails

• No ranking, revenue, or popularity claim from search position alone.
• No copying names, assets, descriptions, UI, or proprietary behavior.
• Fresh trademark/collision review remains required before identity changes.

Acceptance

• Timestamped source snapshot and analysis are committed.
• Each recommendation is linked to customer evidence and a GitHub decision.
• The canonical roadmap and project-state note are refreshed.

---

Scope / non-scope

Only the work and evidence already described in this issue are in scope. Merge, deployment, provider or store mutation, spend, billing, customer contact, device acceptance, indexing, and release remain separate gates unless this issue explicitly includes them and fresh proof is recorded.

Dependencies

No unresolved dependency is explicitly stated in the current body. If implementation exposes one, record its stable roadmap ID here before dependent work starts.

Plan

1. Revalidate the current evidence above against exact current source or live state.
2. Complete the scoped work and unchecked items above in dependency order, preserving every non-goal and stop gate.
3. Run the focused tests and proof already named; add regression coverage for any corrected defect.
4. Record the exact revision, receipt, and applicable live readback before closure.

Evidence and closure

Close only from exact current-source evidence plus the applicable independent readback. Keep local, GitHub/CI, provider, deployment, device, store, commerce, indexing, traffic, and revenue evidence distinct; one does not imply another.

Owner / lane

The repository delivery lane owns ordinary implementation and verification. The operator owns only actions explicitly marked as operator-only or protected.

Resolution plan

• Verified: 2026-08-25T05:34:25Z against main@04a6cd5e808720983471ee9595fd40bc94e1f0fe (commit time 2026-08-25T00:53:29Z).
• Source basis: Original issue body, all 0 comment(s), current default-branch tree, disposition-appropriate source-path checks, and referenced pull-request states.
• Disposition: Research or diagnostic work - gather current evidence and produce the bounded decision artifact; no source implementation is implied.
• Outcome: Turn changing parking-app and iOS patterns into explicit experiments without copying competitors or bloating the privacy-first MVP.

Current evidence and corrected premise

The issue remains open and requires the resolution steps below.
All 0 issue comment(s) were read. There are no comments.

Resolution steps

1. Revalidate the newest evidence and every availability claim against the named authoritative sources, recording identity, timestamp, and query window.
2. Execute the still-open research, measurement, and specification items in dependency order; preserve decisions already recorded in newer comments.
3. Reproduce the requested artifact from its documented inputs and reconcile any contradiction with older issue text.
4. Map each acceptance item to its timestamped evidence, unavailable-state receipt, or explicit decision.
5. Stop before implementation, publication, account mutation, provider spend, deployment, or release.

Grounded issue-authored detail

Scope / non-scope

Only the work and evidence already described in this issue are in scope. Merge, deployment, provider or store mutation, spend, billing, customer contact, device acceptance, indexing, and release remain separate gates unless this issue explicitly includes them and fresh proof is recorded.

Tests and acceptance

Acceptance

• Timestamped source snapshot and analysis are committed.
• Each recommendation is linked to customer evidence and a GitHub decision.
• The canonical roadmap and project-state note are refreshed.

---

Dependencies and stop gates

Dependencies

No unresolved dependency is explicitly stated in the current body. If implementation exposes one, record its stable roadmap ID here before dependent work starts.

• Do not close this issue until every acceptance item is mapped to exact merged-head evidence.

Next AI first action

Revalidate the newest evidence and every availability claim against the named authoritative sources, recording identity, timestamp, and query window.

[lightcloud00]

Verified issue disposition — diagnostic

This is the current managed disposition for lightcloud00/parknudge#21 at default-branch 5c3d185143a2.

Current evidence

• Current stable snapshot for Run a quarterly parking-app trend and competitor evidence review #21 at 5c3d185143a2 keeps the issue open with body hash fe80509481c6; the validated grounded planner classified it as diagnostic_ready.

Files or owner actions

• For Run a quarterly parking-app trend and competitor evidence review #21, bind the issue title 'Run a quarterly parking-app trend and competitor evidence review' to one existing source path or named owner action before implementation.

Bounded plan

• For Run a quarterly parking-app trend and competitor evidence review #21: Resolve the recorded targeted-source diagnostic or bind a canonical checkout before any implementation attempt.
• For Run a quarterly parking-app trend and competitor evidence review #21: Record the canonical checkout, default-branch SHA, worktree dirt, and issue body hash before probing.
• For Run a quarterly parking-app trend and competitor evidence review #21: Trace the issue-named behavior through these bounded source concepts or surfaces: quarterly, parking-app, trend, competitor, evidence, review.
• For Run a quarterly parking-app trend and competitor evidence review #21: Write a source-bound diagnostic receipt with reproduced/refuted state, root cause, implicated paths, and the smallest safe change boundary.
• For Run a quarterly parking-app trend and competitor evidence review #21: Only after that receipt exists, implement the bounded fix and run the focused check followed by the repository-wide gate.

Commands

• Run git grep -n -F quarterly main for Run a quarterly parking-app trend and competitor evidence review #21 and retain sanitized output.
• Run git grep -n -F parking-app main for Run a quarterly parking-app trend and competitor evidence review #21 and retain sanitized output.
• Run git grep -n -F trend main for Run a quarterly parking-app trend and competitor evidence review #21 and retain sanitized output.
• Run git grep -n -F competitor main for Run a quarterly parking-app trend and competitor evidence review #21 and retain sanitized output.
• Run git grep -n -F evidence main for Run a quarterly parking-app trend and competitor evidence review #21 and retain sanitized output.
• Run python3 -m pytest -q for Run a quarterly parking-app trend and competitor evidence review #21 and retain sanitized output.

Acceptance tests

• For Run a quarterly parking-app trend and competitor evidence review #21: [ ] Timestamped source snapshot and analysis are committed.
• For Run a quarterly parking-app trend and competitor evidence review #21: [ ] Each recommendation is linked to customer evidence and a GitHub decision.
• For Run a quarterly parking-app trend and competitor evidence review #21: [ ] The canonical roadmap and project-state note are refreshed.
• For Run a quarterly parking-app trend and competitor evidence review #21: [ ] Timestamped source snapshot and analysis are committed.
• For Run a quarterly parking-app trend and competitor evidence review #21: [ ] Each recommendation is linked to customer evidence and a GitHub decision.
• For Run a quarterly parking-app trend and competitor evidence review #21: [ ] The canonical roadmap and project-state note are refreshed.

Risks

• For Run a quarterly parking-app trend and competitor evidence review #21, a false source binding could widen the change or invalidate this plan; Revert only the exact task-branch change after capturing source and runtime identity; never reset or restore an owner worktree.

Stop gates

• For Run a quarterly parking-app trend and competitor evidence review #21: no issue close, reopen, body edit, pull-request, branch, or merge mutation while implementing this plan
• For Run a quarterly parking-app trend and competitor evidence review #21: the managed plan comment and disposition-specific readiness labels are the only authorized issue mutations in the planning lane
• For Run a quarterly parking-app trend and competitor evidence review #21: no push, protected-branch update, force-push, or merge
• For Run a quarterly parking-app trend and competitor evidence review #21: no deploy, upload, App Store Connect, TestFlight, or public release
• For Run a quarterly parking-app trend and competitor evidence review #21: no credential value disclosure, rotation, billing, or provider change
• For Run a quarterly parking-app trend and competitor evidence review #21: no owner-worktree restore, reset, checkout, process signal, or queue reorder

---

Ledger schema: aos.github-issue-plan-coverage.v1 · issue body: fe80509481c6

[lightcloud00]

Competitor, review, and pricing research receipt

The dated dossier for ParkNudge is complete: 10 ranked competitors, official offer evidence, capped positive and negative review samples (or sourced low-evidence declarations), pricing distribution, contradictions, limitations, and a proposed offer.

• Obsidian dossier: AOS-Memory/02_projects/ParkNudge/research/2026-08-27-competitor-pricing-reviews.md
• Evidence package: /Users/gus/Desktop/research/portfolio-competitor-pricing-reviews-20260827/parknudge/run
• Strict package fingerprint: 4c2f349dd63eb16791bac48dcd7292a3b8547d4e81261aa55637767f769e53de
• Portfolio hub: AOS-Memory/02_projects/Portfolio/competitor-pricing-reviews/INDEX.md
• Proposed direction: Keep the current parking reminder free and test USD 4.99 lifetime Pro for history, saved places, and customization; do not charge for the first reminder.

The proposal is not a live price change. No storefront, RevenueCat, Stripe, Shopify, Chrome Web Store, public API, schema, website pricing, deployment, or release state changed.

Decision follow-up

• Research 10 competitors and current public offer evidence
• Capture positive/negative review themes or low-evidence declarations
• Run strict contradiction and unsupported-claim validation
• Product owner accepts, rejects, or revises the proposed paid boundary
• If accepted, open a separately scoped implementation issue for any public pricing change

[lightcloud00]

2026-08-28 evidence receipt

• Product: ParkNudge (lightcloud00/parknudge)
• Frozen source: 69d70d208727a190a0cfafcf30045f141321715f with status current_default_head. Current GitHub default head still matches the frozen research head.
• Final collector: competitor-collection:e1e094ee3471c3d86b5927c6; 10 screened rows for this app; portfolio total 170; manifest b2020b79c68959fc4d24d2051e45640cfb75767cb90ec3a217848ebe883f98d9.
• Strict package: c287d5173aa7324f0f2ecc3ccf0acc60553b7e8977cf0d938da29b41390c41ca with 5 verified sources, 5 evidence records, 3 claims, and contradiction review passed.
• Opportunity rank/score: Reserve ParkNudge identity and complete trademark review #6 / 78.75 — delivery_recommendation.
• Top-three classification: direct workflow, direct workflow, direct workflow.
• Competitors do better: Direct competitors foreground one-tap or automatic save, Bluetooth triggers, Apple Watch entry points, and immediate return navigation.
• Defensible portfolio edge: ParkNudge has a complete free parking loop, pin correction, garage details, meter alerts, directions, and no backend or background location.
• Uncertainty: The listing evidence cannot prove competitor auto-detection reliability or battery cost.
• Protected hold: None for the scoped source or issue action.

Ratings and search position are public proxies, never installs or revenue. No account, purchase, identity, physical device, provider spend, pricing change, deployment, submission, or public release was used or authorized by this research batch.

Ranked opportunity

• Child: Evaluate opt-in automatic parking suggestions and companion surfaces #13
• Action: Expose save-current-location and navigate-to-car through an App Shortcut or widget while keeping detailed corrections in the app.
• Boundary: User-invoked App Shortcut/widget only; no background tracking or commerce change.