Netflaix

Goal

Build Netflaix, a small Mac app based on the open-source torrent-search-api project. It searches selected public sources, sorts results by seeders, and lets the person copy a magnet link or open it in their existing torrent app.

Before you start, ask the person

1. What should the app be called? (Default: Netflaix)
2. Which public sources should be selected when the app opens? (Default: ThePirateBay, Yts, 1337x, Torrent9, and Eztv when those providers are available)
3. Which search category should be selected initially? (Default: All)
4. Where should the finished app be saved? (Default: in the project’s release folder)

Features

• Search sources: Provide a search field, category menu, and searchable public-source list. Search only checked providers. Select only providers marked public by torrent-search-api; show private providers as unavailable without asking for credentials.
• Compare results: Show each result’s title, source, size and available date. Sort by seeders from highest to lowest; missing seed counts appear as a dash and sort below numeric counts. Show peers when the source provides them.
• Handle categories: Offer All, Movies, TV, Music, Games, Apps, Books, and Anime. If a source does not support the chosen category or fails, keep valid results from other selected sources and explain when every source fails.
• Copy or open: Provide Copy and Open actions on every result. If the result has no magnet yet, ask the provider for it when the person clicks. Copy places the magnet on the clipboard; Open passes it to macOS to launch the person’s default torrent app.
• No surprise downloads: Never download a torrent or content automatically. Do not register Netflaix as the default magnet handler. Only open a magnet after the person clicks Open.
• Explain network use: Tell the person before the first search that their search terms are sent to the selected public sources. Requests go directly from the Mac to those sources; do not add an intermediary server, analytics, or search-history storage.
• Clear feedback: Show loading, empty, and error states. Keep the app usable when an individual provider is unavailable or returns malformed data.
• Mac finish: Use a polished macOS window, a custom app icon, keyboard-friendly controls, and light and dark appearance. Name the app Netflaix unless the person chooses another name.

Constraints

• Use Electron and the npm package torrent-search-api version 2.1.4. The main process owns the API calls; the renderer has no Node integration and talks to it through a small preload bridge with context isolation and sandboxing enabled.
• Build the macOS .app bundle into release/. Do not install it into /Applications unless the person explicitly asks.
• Use the public providers included in the package. Do not collect or store private-provider passwords, tokens, cookies, or credentials. Do not add providers or scrape sites outside the package’s public-provider list.
• Search terms and network requests are sent to each selected provider. Show this plainly in the app. Do not log queries, keep search history, add analytics, or send data to any other service.
• No accounts, server, auto-downloads, or bundled torrent client. Opening a magnet requires the person’s explicit click and an existing torrent app.
• Escape source-provided text before displaying it. Validate magnet links before copying or opening them, and restrict external link handling to the app’s explicit Open action.
• Keep a visible reminder to use the app only for content the person is authorized to access. The app must not describe results as licensed, verified, or safe; it only displays what a source returns.

Build steps

1. Check for macOS 14 or newer, Node.js 22 or newer, and npm. Ask the questions above; if the person is unavailable, use the defaults.
2. Create the project layout, package.json, Electron main process, secure preload bridge, and a simple window. Install torrent-search-api 2.1.4 and confirm its public providers load.
3. Add the source list and search interface. Enable public providers in the main process, accept searches only from selected public provider names, and enforce a reasonable result limit.
4. Add result sorting, source details, magnet lookup, clipboard copy, and explicit open-in-torrent-app actions.
5. Add the network-use notice, error states, safe text rendering, dark appearance, and the custom Netflaix icon.
6. Build the macOS app bundle into release/, launch it, and complete the acceptance checks below.

Acceptance checks

• Launching the app shows Netflaix, its custom icon, a query field, category menu, and public providers. Private providers cannot be enabled and no credential fields exist.
• Submitting an empty search does not make a network request and gives a clear prompt. Searching with selected sources passes the query, category, and result limit to the API.
• Results from multiple working sources appear together and sort by numeric seed count descending. Results with missing seed counts stay visible below counted results.
• A provider failure does not erase results from working providers. If all selected providers fail, show a readable error and let the person try again.
• A result with a magnet copies the exact link when Copy is clicked. Open calls the system link handler only after Open is clicked. A result without a magnet requests one on click and shows a useful error if none is available.
• Search terms are not stored or logged. No content downloads begin from a search, result display, or app launch.
• Build and launch the finished macOS app from release/; verify the visible app name and icon.

Hand-off to the person

Tell them:

• Where the finished Netflaix.app is and how to open it.
• Each search term is sent to the public sources they selected. Search history is not saved.
• Copy keeps a magnet link on the clipboard; Open hands it to their existing torrent app. Netflaix does not download files by itself.
• Only search for or access content they are authorized to use.
• Which sources were selected by default and how to change them.