ApplyCandid started as a Chrome extension for a plain reason: Chrome's Manifest V3 sidebar API (chrome.sidePanel) shipped first, and most job seekers were already there. Firefox users who wanted the same autofill for LinkedIn Easy Apply, Naukri, and Indeed had no option but to switch browsers, which isn't a reasonable ask just to fill out an application. That gap is closed now. ApplyCandid is live on Firefox Add-ons, and it's the same extension, not a stripped-down port.
What's identical to the Chrome version
Everything that decides what gets typed into a form is browser-agnostic, because none of it lives in a browser API. On Firefox, exactly as on Chrome:
- Deterministic fields (name, email, phone, work authorization, notice period) are matched against your saved profile and filled locally in your browser, with no network call.
- Open-ended fields that need drafted text go to ApplyCandid's AI server, along with your resume and the job description, so the draft is grounded in your actual background.
- Nothing submits itself. Auto-Submit is off by default, and when you turn it on, the daily cap still applies.
- No portal password is ever asked for or stored. The extension acts inside the LinkedIn, Naukri, or Indeed tab you're already logged into, the same way on both browsers.
That last point matters more on Firefox than it sounds, given how much of Firefox's own audience chose the browser specifically to avoid handing credentials to things that don't need them.
What actually changed to make this work
Chrome's sidebar API and Firefox's equivalent, sidebar_action, aren't the same interface, so the sidepanel UI runs behind a small compatibility layer that talks to whichever one is present. The background script is a Manifest V3 module in both builds, which only became possible on Firefox once Firefox 128 added full MV3 support; the Firefox build targets Firefox 140 and newer specifically because that's also when Firefox started supporting the data collection permissions section covered below. Content scripts, the pieces that read a LinkedIn or Naukri page's form fields, are identical files on both browsers; the sites don't know or care which browser injected them.
Practically, this means the sidebar opens from a slightly different spot. Firefox keeps extension sidebars in the sidebar area you toggle from the toolbar rather than Chrome's dedicated side panel icon, so the first time you open ApplyCandid on Firefox, look for it there instead of next to the address bar.
Why Firefox shows you a permissions screen Chrome doesn't
Install ApplyCandid on Firefox and you'll see something Chrome's install flow never shows: a breakdown of which categories of data the extension collects, not just which pages it can read. That's Firefox's data collection permissions system, and it's worth explaining plainly rather than letting it read as a red flag:
- Website content (required): the job posting text and form fields on the page you're applying from. This is the entire mechanism the autofill runs on; without reading the page, there's nothing to fill.
- Personally identifying information (required): your resume and profile data, the same information you'd type into any application yourself. It's required because deterministic field-filling reads it directly.
- Technical and interaction data (optional): basic usage analytics. You can decline this at install and the extension works exactly the same either way.
Chrome asks a coarser version of the same question, phrased as "read and change data on this site." Firefox just breaks it into categories instead of one line, which is a better disclosure, not a bigger ask. Nothing in that list is new information; it's the same access the Chrome build has always needed to do the same job.
What's not there yet
Chrome-only extension surfaces don't have a Firefox counterpart, and the extension is written to no-op cleanly where that's the case rather than error. The most visible example: Chrome's chrome.sidePanel auto-open behavior on some flows falls back to the toolbar popup on Firefox, since sidebar_action has no equivalent API to trigger it automatically. Everything downstream of opening the sidebar, meaning the actual form-filling, behaves the same once it's open.
Getting it on Firefox
Open the Firefox Add-ons listing and click Add to Firefox. Firefox will show the permissions breakdown above before install completes; approving the required categories is what lets the extension read the page and your saved resume, same as accepting Chrome's single permission prompt does today. After that, the setup is identical to Chrome: connect an AI server in Settings, upload a resume, and start a run on a LinkedIn, Naukri, or Indeed job page.
Try it on Firefox.
Free to start. Same resume-grounded autofill, same no-stored-passwords design.