What the pipeline did before this report shipped.
A public sample. What your verdict would look like.
What the pipeline ran before this verdict shipped. Every stage passed.
The 8× speed claim holds. Three named risks to watch.
A public sample. What your verdict would look like.
What the pipeline ran before this verdict shipped. Every stage passed.
Pulse is your $19/month AI pair-programmer built specifically for indie iOS developers1. You've hit $5.3K MRR with 280 paying users in 8 months on the side2. The pitch claims Pulse ships iOS features 8.4× faster than developers using GitHub Copilot. After checking 42 sources and putting two AI models in an argument about it, that claim holds at a 5× floor3.
Our recommendation: go full-time. The traction is real, the niche is right-sized for a single founder4, and your moat is the iOS-specific knowledge you've indexed (Copilot only knows generic code). Three named ways this fails: (1) Cursor or Copilot ships first-class Swift specialization inside 12 months15; (2) Apple ships a good-enough Xcode AI at WWDC16; (3) the indie iOS developer pool drops below 800K worldwide17.
One root claim. Four child claims. Eight leaves. Each tagged with evidence, status, and source.
Pulse is a real, quittable business: an AI coding tool that wins because it knows iOS deeply, where Copilot only knows code generally.
73% of indie iOS devs in our survey use Copilot today and report frustration with iOS-specific output.
Verdikt indie iOS dev survey · n=47 · Stack Overflow 2025
$19/month sits inside the $10–$25 indie SaaS sweet spot for solo and small studio buyers.
IndieHackers product database · $5K–$25K MRR cohort pricing
The total spend on indie developer tools sits around $300M a year and grows about 18% annually as more solo developers add AI coding tools to their stack5. The slice you actually serve, indie and small-studio iOS developers, is roughly $120M and growing faster (~22%) as iOS-specific tooling becomes a real category6. At $19/month with median 2 seats per studio, $5M in annual revenue clears at about 22K reachable customers, which is within range over two years7.
Total indie developer tools market
All indie dev tool spend, all platforms. Per IDC dev tools 2026 outlook.
Two primary sources disagree on the number of active indie iOS developers worldwide. We show both, say which we used, and tell you when we'll re-check.
Apple developer.apple.com/programs · active iOS devs worldwide
Statista 2026 mobile dev population · iOS exclusive subset
When two strong sources disagree by more than 5%, we show both and explain the gap. We do not silently average them. If the gap is wider than 40%, the claim gets downgraded to NEEDS MORE EVIDENCEand the report cannot ship until it's resolved. Otherwise the report ships with the gap noted.
Minutes to ship a typical iOS feature, end to end.
Median across 22 iOS dev tasks. Pulse customers vs published Copilot benchmarks on the same task list.
One AI model attacks the 8× claim with its best counter-argument. A second model defends. The report only ships if the claim survives above a stated floor.
The 8.4× median speedup is cherry-picked. Pulse only benchmarked tasks where iOS specialization matters most (SwiftUI lifecycle, App Store patterns). Run Pulse on a broader set of programming tasks and the gap disappears.
Granted that the benchmark is iOS-specific. That is the point: Pulse is positioned as an iOS-only tool. We re-ran on a broader iOS task set including general Swift logic, REST clients, and unit tests. Speedup compresses to 5.6× on the broader set, not 8.4×. The claim survives the 5×+ floor required.
Source: Verdikt benchmark · broader iOS suite n=22 · cross-checked against the sample dataset
Even at 5.6× the moat argument fails. GitHub or Cursor can fine-tune their existing models on iOS data and reach parity in six months. They have the engineers, the data access, and the distribution. Pulse will get crushed.
Catch-up risk acknowledged and recorded as kill criterion K01 at 35% probability over 12 months. Note: the iOS data curation Pulse did (3 years of WWDC content, 1.2K curated repos, App Store rejection categorization) is non-trivial. Reproducing it requires someone who understands iOS development well enough to make the right inclusions. That is the 6-12 month window where Pulse compounds further.
Source: Cursor and Copilot changelogs review · no iOS-specific releases in last 18 months
Stress test survives at 5×+ floor. The dominant risk is Cursor or Copilot adding Swift specialization, properly captured as K01 with named watch signal and quarterly review gate. Claim recorded as '8.4× on iOS-specific tasks, 5.6× on broader iOS suite'. Report updated.
Rule: A second model must attempt to break the 10× claim from its strongest counter-argument. The transcript is attached to the memo. If the claim survives only above a stated floor, the memo records the floor verbatim.
Pulse's real advantage is what it's been trained and fine-tuned on: Apple's developer docs, every WWDC session from the last three years, the Swift Package Index, App Store rejection patterns, and curated Swift code from top-rated indie repos9. The model itself is a thin wrapper. Cursor and Copilot use better base models but feed them generic code, so they hallucinate UIKit APIs, miss SwiftUI lifecycle quirks, and ship code that fails App Store review1011. To catch up they need 6–12 months of iOS-specific data work and someone who understands WWDC content well enough to curate it12. Hover any node below to see how a source flows through.
Hover a source or output to see how Pulse turns iOS-specific knowledge into working code. This is the moat.
$10/month. Owned by Microsoft, distributed inside VS Code. The threat is not feature parity today, it's that Microsoft can ship Swift-specific tuning in a single release cycle19. Watch their Build conference and any post-WWDC release notes.
$20/month. The best general AI IDE. Has the talent and capital to specialize per platform if iOS becomes a clear vertical20. Today they treat Swift as just another language. That's your window.
Apple's built-in Predictive Code Completion. Free. Limited to single-line completions and ships only with Xcode. Not a 10× tool today21, but the next WWDC could change that fast (this is K02).
41% of indie iOS devs in our illustrative survey just use Copilot and live with the friction22. Your real fight is not Cursor. It's the developer who already has a workflow that's good enough. You win by making the trial-week obviously better.
Named, watched, dated.
Probability against impact. Click a marker to expand. The diagonal is the ship-blocker line.
If Cursor or GitHub Copilot ships iOS/Swift-specific tuning in the next 12 months, your moat compresses fast. Probability is anchored on 3 Cursor changelog hints in Q1 2026 and Microsoft's pattern of fast vertical responses.
Each kill criterion ships with a named source, a threshold that triggers a rerun, and the next scheduled check.
| Kill | Trigger | Source | Threshold | Next check |
|---|---|---|---|---|
| K01 | Cursor or Copilot adds Swift specialization | Cursor changelog · GitHub Copilot release notes | Any product release mentioning 'Swift', 'SwiftUI' or 'iOS' specifically | 10 Jun 2026Monthly |
| K02 | Apple ships a serious Xcode AI at WWDC | WWDC keynote + Platform State of the Union | Apple announces a general-purpose iOS AI coding assistant | 10 Jun 2026 (WWDC)Annual |
| K03 | Indie iOS dev pool drops below 800K | Apple Developer Program enrollment + Statista mobile | Both estimates fall below 800K active iOS devs | 15 Jul 2026Quarterly |
When any threshold fires, we re-run the affected sections and ship a human-readable diff. Refund or re-run if it's not defensible.
Sample preview14 buyer-language quotes from indie iOS forums. Mapped against four comparables. The ceiling above which churn risk gets real, named.
Buyer language, comparable tools, and the price the market will actually pay.
Twelve weeks. One founder, full-time.
Stack to use. Tools to install. What to ship each week. The exact number to hit at week 12.
Ship Core Data + CloudKit + StoreKit 2 coverage in the iOS knowledge graph. These are the three places indie iOS devs hit walls in months 3-6 of building. Catching this layer makes you stickier on day 30.
One motion gets the year-1 nod. The other two are notes for year 2.
Three ways to reach indie iOS devs. We modeled reach, cost, and ceiling for each. One recommended for year 1.
You ship, you post, you talk to buyers directly.
Primary motion for the next 12 months. Your voice resonates with indie iOS devs because you are one. Costs almost nothing to start.
Free tier + in-product invites. Users find each other.
Layer in month 6+. Needs Pro tier and team plan to make the free tier pay for itself. Premature today.
Apple Developer events, JetBrains, dev-tool integrations.
Skip for year one. Partnership BD eats founder time you do not have. Revisit at $30K MRR when you can hire one.
Where the 22K reachable customers actually live, ranked by expected contribution. Total cost under $3K through week 12.
Tier distribution shown. Click a tier to filter the list. Every claim in the memo links back here.
Apple Developer Program · enrollment stats 2026
developer.apple.com/programs/stats-2026
Stack Overflow Developer Survey 2025
survey.stackoverflow.co/2025
Microsoft 10-K · developer tools segment
sec.gov/Archives/edgar/data/msft-10k-2025.pdf
GitHub Copilot · pricing + usage disclosure
github.blog/copilot-2026-usage-update
IDC · Developer tools market 2026 outlook
idc.com/dev-tools-2026
Cursor · product changelog (last 18 months)
cursor.sh/changelog
Pulse customer interviews · n=14
Verdikt sample dataset · interview transcripts
Latka founder interview · Alex Kim (Pulse)
getlatka.com/companies/pulse-app
The Information · Cursor funding + roadmap signals
theinformation.com/articles/cursor-2026
Hacker News · 'Indie iOS devs are paying for AI tools'
news.ycombinator.com/item?id=40231788
r/iOSProgramming · Pulse vs Copilot threads (sampled)
reddit.com/r/iOSProgramming/search?q=pulse
How this report was made.
A transparent log of the work that produced this report. Not a legal attestation.
This report is generated by AI research pipelines. Citations reflect publicly available information at the time of generation and may change. Verdikt provides the analysis as a decision-support artifact only and does not warrant outcomes or accept liability for actions taken based on its conclusions. Read the sources, apply your own judgment, and consult qualified professionals where appropriate.
Zero data retention · No training on your brief, trace, or memo · Refund or re-run if it's not defensible
Same homework. Different math.
The exact research above, the way you would've done it over a weekend with a dozen tabs open. And the way Verdikt did it this morning.
$49.99 per verdict. Target under 1 hour. Refund or re-run if it's not defensible.