Android · Web · Cloudflare Worker

Park Contact

Park Contact is a multi-surface contact platform built by Crovyx for parking-presence scenarios. A native Android app, a public web surface and a Cloudflare Worker backend with D1 storage sit behind shareable /s/:token links — so a driver can reach a vehicle owner without ever seeing a phone number, while abuse controls and FCM push keep the channel under control.

Discuss a similar build All projects
Park Contact — Android app, web surface and Cloudflare Worker backend with D1 and FCM
Android app → public web → Cloudflare Worker + D1 → FCM push → shareable /s/:token link. One product, three surfaces, one backend.
Problem

Reaching someone without exposing them.

Real-world parking-presence contact is a small problem with a hostile surface: the person reaching out is anonymous, the person being reached should stay private, and the channel sits exposed to spam and abuse the moment it goes live.

  • Private phone numbers must never be shared with the requester.
  • The owner needs to be notified instantly, on the actual device.
  • Links must be usable from a stranger’s phone with no install required.
  • The system has to survive spam, scraping and repeat abuse on day one.
What it does

One token. Three surfaces. One backend.

  • Native Android app for owners to register, manage tokens and receive contact requests.
  • Public web surface served from the Cloudflare Worker that resolves /s/:token links without an install.
  • Cloudflare Worker backend with a D1 schema for tokens, owners, requests and abuse events.
  • Firebase Cloud Messaging push so the owner’s phone reacts in seconds, not minutes.
  • Rate limiting, token rotation and abuse controls baked into the request path, not bolted on.
Capabilities demonstrated

What this project proves.

Multi-surface product

Native Android, public web and an edge backend designed together as one product — not three apps that happen to share a database.

Cloudflare edge stack

Workers + D1 used in anger: real schema, real handlers, real push integration, deployed at the edge with the latency profile to match.

Abuse-aware design

Token shape, rate limits and abuse signals designed into the request path from day one, because a public contact channel that ignores abuse dies in a week.

Build something similar Need a public-facing contact surface without exposing your users?

Whenever the brief is “let strangers reach our user safely, from any device, instantly” — the architecture pattern is the same. Crovyx ships these systems end-to-end across Android, web and the Cloudflare edge.

Start a conversation
AccountOS Platinum AI Notes Songift