Paid Spotlight replacement for power users
Package a polished, paid macOS utility built on the fsearch approach: instant fuzzy, typo-tolerant, content-indexed file search with a native UI, Spotlight-replacement positioning, and power-user features like regex, saved searches, and Alfred/Raycast integration. Target developers, designers, and power users frustrated with Spotlight's slow or inaccurate indexing.
What to build
A native macOS menu-bar app that packages fsearch's Rust indexing engine into a polished, paid Spotlight-replacement for developers and power users: instant fuzzy/typo-tolerant filename search plus indexed full-text content grep, with regex search, saved searches, and Alfred/Raycast extensions.
fsearch proves ~1 ms query latency over an 8M-file index is achievable on macOS with fuzzy matching and content grep; wrapping that engine in a native UI with power-user features turns a raw open-source benchmark into a sellable Spotlight alternative.
Demand
Developers, designers, and power users who already pay for Alfred, Raycast, or HoudahSpot to work around Spotlight's slow and inaccurate indexing are the natural buyers, and fsearch's rapid GitHub traction signals fresh interest in this exact problem.
- GitHub trending — noahdunnagan/fsearchMarket
1211 stars, written in Rust; high engagement at the source for a whole-disk macOS file search tool claiming ~1 ms query latency over 8M files.
- Opportunity briefMarket
Analyst-identified opportunity to productize fsearch's indexing approach into a paid native macOS app with Spotlight-replacement positioning and power-user integrations (regex, saved searches, Alfred/Raycast).
- Adjacent paid productivity toolsMarket
Alfred's Powerpack and Raycast Pro both monetize macOS search/launcher workflows, showing an established base of users willing to pay for faster local search and productivity tooling.
Stack
- fsearch (Rust indexing core)
- Swift / SwiftUI
- FSEvents API
- Full Disk Access / macOS sandboxing entitlements
- Sparkle (auto-update)
- Alfred Workflow & Raycast Extension APIs
Solo + AI difficulty
The hard part — a fast fuzzy/content-indexed search core — already exists as open source, so a solo builder mainly needs to wrap it in a native SwiftUI menu-bar UI, handle Full Disk Access permission prompts gracefully, and package/notarize the app; a basic sellable MVP (core search UI plus saved searches) is realistic in roughly 3-5 weeks with AI-assisted coding, with Alfred/Raycast integrations as a fast follow.
- Entry threshold
- Low barrier: the hard indexing/search engine already exists as open source, so a solo builder mainly needs to wrap it in a native macOS app with UI polish, licensing, and distribution; buildable in 2-4 weeks with AI assistance.
- Window
- 3-6 months
Where to find first users
- Product Hunt launch
- Show HN on Hacker News
- r/macapps and r/MacOS
- Alfred workflow gallery and Raycast extension store
Competitors
Counter-signals & risks
Apple's Spotlight and Finder could improve indexing speed and fuzzy/typo tolerance in future macOS releases, eroding the differentiation a third-party tool offers.
Existing established tools (Alfred, Raycast, HoudahSpot, EasyFind, mdfind-based utilities) already serve power-user file search needs, raising competitive and user-acquisition risk.
Full-disk content indexing on macOS requires broad filesystem access permissions, which may face user trust friction or App Store sandboxing restrictions if distributed commercially.
No historical market match was found for this opportunity, indicating limited validated demand signal beyond the technical repository itself.
Original title: noahdunnagan/fsearch: Whole-disk file search for macOS: fuzzy names, typo tolerance, indexed content grep. ~1 ms over 8M files.
Related signals
- Developer tools#1
Spend-capping proxy for AI API usage
Build a lightweight proxy/middleware that sits between apps and AI providers (OpenAI, Anthropic, Gemini, fal, Replicate) to enforce daily and hourly spend caps per key, agent or customer, auto-detect runaway loops of repeated calls, and fire instant alerts via Telegram, email or Slack. Target indie AI builders and small teams running agents or video/image generation pipelines who currently have no way to cap spend below the provider's monthly limit.
Demand6/10est.Buildability8/10est.Competition6/10est.via Reddit33 competitors - Developer tools#5
Local memory layer for AI coding agents
Build and sell a lightweight, local-first memory layer for coding agents (Claude Code, opencode, Cursor, Aider users) that persists project context across sessions without a daemon, cloud account, or LLM call. Ship it as a paid CLI/plugin with team-sync, encrypted cloud backup, or hosted search tiers for solo devs and small teams who want Claude Code-style memory without vendor lock-in.
Demand1/10measuredBuildability9/10est.Competition6/10est.via Hacker News33 competitors - Developer tools#7
PR screening bot for AI-generated contributions
Build a GitHub App or CI bot for open-source maintainers that scans incoming pull requests for signs of AI-generated code (boilerplate patterns, hallucinated APIs, inconsistent style, missing tests, template-like PR descriptions) and auto-labels or flags them for review, helping projects enforce new no-AI or disclose-AI-usage contribution policies. Secondary market: companies with internal contribution guidelines wanting the same triage on pull requests.
Demand4/10measuredBuildability7/10est.Competition10/10est.via Hacker News0No named competitors