Feature spec
Goal: Send a clear invoice after finishing a job.
- Add a client, line items, a due date, and payment instructions.
- Preview the total before exporting a PDF.
- Keep an editable draft if export fails.
PhosphorRTTY decodes Radio Teletype (RTTY) signals in real time using your iPhone's microphone
$0.99 · In-app purchases
Evidence scope: No current overall US chart position is available. Category-chart positions shown in discovery are a separate scope. Revenue is a directional model estimate, not verified earnings.
A product spec, screen plans, and build steps for your coding agent.
First kit free with a verified email
Combine features and design from your favorite apps.
Kit ready. Verify your email to download it.
Generating… usually about a minute.
What should your app do differently? Your note travels with the kit so your coding agent builds around your idea.
A product spec, phased build plan, differentiation notes, and screen references.
Illustrative example: an invoice app for independent contractors. Your kit is tailored to the app you choose; this is not its generated content.
Goal: Send a clear invoice after finishing a job.
Invoice editor: Client at the top, editable line items in the middle, total and preview action at the bottom.
States: Empty draft, validation errors beside each field, exporting, and a retry action that preserves the draft.
Hypothesis: Contractors need faster repeat invoices more than more templates.
First experiment: Test duplicating a previous job with five contractors. Watch where they hesitate before expanding the feature set.
The full kit adds a phased build plan, evidence notes, tool prompts, and implementation guidance. It is a plan for your coding agent, not a finished app.
Usage: Mechanics are fair game; never reuse the original name, branding, assets, or verbatim copy.
JavaScript is required to complete mailbox verification.
Good fit for mobile-first iOS and Android prototypes with managed app scaffolding.
Rork plan preview for PhosphorRTTY: map the core Utilities workflow, choose the smallest differentiated feature set, define the data and monetization boundaries, then prototype the riskiest user journey first.
Preview ready. Verify your email to reveal and copy the full prompt.
JavaScript is required to complete mailbox verification. Return to this prompt preview.
Affiliate link: CloneChart may earn a commission at no extra cost
Original App Store material. Ratings and screenshots describe the existing app, not proof of demand for your version.
PhosphorRTTY decodes Radio Teletype (RTTY) signals in real time using your iPhone's microphone. Hold your phone near a shortwave radio tuned to an RTTY signal and watch the text appear on screen, character by character, on an authentic phosphor CRT display. No internet connection required. No external hardware. No account. Just your iPhone and a radio. WHAT IT DECODES RTTY is the oldest digital mode in amateur radio — two audio tones representing mark and space, encoding text via the 5-bit ITA2 (Baudot) alphabet or 7-bit ASCII. PhosphorRTTY handles all standard configurations: Baud rates: 45.45, 50, 75, 100 Bd (auto-detected or manual) Shifts: 85, 170, 450, 850 Hz (auto-detected or manual) ITA2 (Baudot) and ASCII modes USB and LSB conventions AUTOMATIC SIGNAL DETECTION The app automatically finds and locks onto RTTY signals: AFC (Automatic Frequency Control) acquires and tracks drifting signals Auto-baud detection identifies the transmission speed Auto-shift detection determines the frequency separation Squelch suppresses noise when no signal is present Or disable any of these and tune manually for full control. FOUR TABS DECODE — The main teleprinter display. Decoded text appears character by character with an authentic mechanical delay. Status bar shows baud rate, shift, mark/space frequencies, and signal lock state. Clear, pause, and session controls. SIGNAL — Live signal analysis. FFT spectrum display (0–4 kHz), scrolling waterfall, mark/space tone indicators, bit period histogram with baud rate markers, and a paper punch tape visualisation of the decoded data stream. LOG — Session history. Every decode session is saved with timestamp, duration, character count, and the full decoded text. Copy, share, or delete individual sessions. CONFIG — All parameters. Audio input gain, decode mode (auto/manual for baud, frequency, and shift), display theme, font size, bell character handling, and RYRY sequence display options. THE DISPLAY Two authentic phosphor CRT themes: Amber (classic teleprinter terminal) Green (military/commercial terminal) Both feature horizontal scanlines, edge vignette, and phosphor glow effects. Monospaced font throughout. RYRY test sequences can be dimmed or hidden to keep the display clean. DSP ENGINE The signal processing is done entirely on-device using a per-sample I/Q quadrature demodulation pipeline: Biquad low-pass filtered I/Q channels for each tone W7AY Automatic Threshold Correction for bit decisions Digital Phase-Locked Loop (DPLL) with per-transition phase correction for timing recovery 512-point FFT for frequency analysis and AFC Asymmetric envelope detection for robust tone tracking through fading Tested against real over-the-air recordings from 20m and 40m amateur bands. Under 1% error rate on clean signals, 4–5% on moderate HF conditions with fixed tuning. WHERE TO FIND RTTY Amateur radio: 14.080–14.099 MHz (20m band), 7.080–7.100 MHz (40m band), 21.080–21.100 MHz (15m band). RTTY contests run throughout the year — during a contest, these frequencies are packed with signals. Maritime and commercial RTTY transmissions can be found across the HF spectrum. A shortwave receiver or SDR with audio output is all you need. REQUIREMENTS iPhone with microphone iOS 17 or later A radio receiver tuned to an RTTY signal (shortwave radio, SDR, or WebSDR audio played through a speaker) No in-app purchases. No subscriptions. No tracking. No network access.
Written user reviews are not shown here. Check current App Store reviews >
These are generated suggestions, not verified review quotations. Check current App Store reviews and speak with users before treating a possible gap as a requirement.
Hypothesis 1
Assumption to check: Expensive subscription
Validate with people who use this workflow before building.
Hypothesis 2
Assumption to check: Missing features
Validate with people who use this workflow before building.
Hypothesis 3
Assumption to check: Poor performance
Validate with people who use this workflow before building.
Plan a focused first version with your coding agent. These are planning assumptions, not a delivery guarantee.
Choose one audience and one core workflow. Use the kit to agree on its screens, data, and acceptance criteria before building.
Decide which secondary features, integrations, and platform support can wait. Your version does not need to reproduce everything in the original.
Validate external services, specialist technology, data access, and ongoing costs for your chosen scope.
From the Build Kit assessment.
A reliable timeline needs an agreed scope and a technical check. Ask your agent to estimate the phases in BUILD_PLAN.md after that review.